diff options
Diffstat (limited to 'documentation/architecture')
4 files changed, 15 insertions, 17 deletions
diff --git a/documentation/architecture/architecture-client-side.asciidoc b/documentation/architecture/architecture-client-side.asciidoc index e16b003687..77e60a8940 100644 --- a/documentation/architecture/architecture-client-side.asciidoc +++ b/documentation/architecture/architecture-client-side.asciidoc @@ -17,7 +17,7 @@ The client-side engine is illustrated in <<figure.architecture.client-side>>. [[figure.architecture.client-side]] .Vaadin Client-Side Engine -image::img/clientside-arch-hi.png[] +image::img/clientside-arch-hi.png[width=60%, scaledwidth=90%] The client-side framework includes two kinds of built-in widgets: GWT widgets and Vaadin-specific widgets. The two widget collections have significant @@ -38,6 +38,3 @@ between the two sides. Integration of widgets with their server-side counterpart components is described in <<dummy/../../../framework/gwt/gwt-overview.asciidoc#gwt.overview,"Integrating with the Server-Side">>. - - - diff --git a/documentation/architecture/architecture-events.asciidoc b/documentation/architecture/architecture-events.asciidoc index e832c581fe..e273a28e97 100644 --- a/documentation/architecture/architecture-events.asciidoc +++ b/documentation/architecture/architecture-events.asciidoc @@ -37,7 +37,6 @@ corresponding listener class. For example, the [classname]#Button# has In the following, we handle button clicks with a listener implemented as an anonymous class: - [source, java] ---- final Button button = new Button("Push it!"); @@ -60,15 +59,21 @@ in this case the [classname]#Button#. [[figure.eventlistenerdiagram]] .Class Diagram of a Button Click Listener -image::img/events-classdiagram-hi.png[] +image::img/events-classdiagram-hi.png[width=50%, scaledwidth=75%] + +In Java 8, you can implement such functional interfaces with a lambda expression: + +[source, java] +---- +Button button = new Button("Push it!"); + +button.addClickListener(event -> + button.setCaption("You pushed it!")); +---- In the ancient times of C programming, __callback functions__ filled largely the same need as listeners do now. In object-oriented languages, we usually only have classes and methods, not functions, so the application has to give a class interface instead of a callback function pointer to the framework. -<<dummy/../../../framework/application/application-events#application.events,"Handling -Events with Listeners">> goes into details of handling events in practice. - - - +<<dummy/../../../framework/application/application-events#application.events,"Handling Events with Listeners">> goes into details of handling events in practice. diff --git a/documentation/architecture/architecture-overview.asciidoc b/documentation/architecture/architecture-overview.asciidoc index 9307b7b72c..dee3a13fcf 100644 --- a/documentation/architecture/architecture-overview.asciidoc +++ b/documentation/architecture/architecture-overview.asciidoc @@ -18,7 +18,7 @@ code and services, and can be mixed together easily. [[figure.architecture.detailed]] .Vaadin Runtime Architecture -image::img/architecture-detailed-hi.png[] +image::img/architecture-detailed-hi.png[width=70%, scaledwidth=100%] <<figure.architecture.detailed>> gives a basic illustration of the client-side and server-side communications, in a running situation where the page with the diff --git a/documentation/architecture/architecture-technology.asciidoc b/documentation/architecture/architecture-technology.asciidoc index 39df9c3651..834bcba292 100644 --- a/documentation/architecture/architecture-technology.asciidoc +++ b/documentation/architecture/architecture-technology.asciidoc @@ -165,7 +165,7 @@ dynamic content. This is illustrated in [[figure.architecture.technology.servlet]] .Java Web Applications and Servlets -image::img/java-servlet-hi.png[] +image::img/java-servlet-hi.png[width=40%, scaledwidth=70%] Web applications are usually packaged and deployed to a server as __WAR__ ( __Web application ARchive__) files, which are Java JAR packages, which in turn @@ -202,7 +202,3 @@ widget set in technical terms, needs to be located under the [filename]#VAADIN/widgetsets# path in the web application. The precompiled default widget set is served from the [filename]#vaadin-client-compiled# JAR by the Vaadin Servlet. - - - - |