diff options
Diffstat (limited to 'documentation/architecture/architecture-client-side.asciidoc')
| -rw-r--r-- | documentation/architecture/architecture-client-side.asciidoc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/architecture/architecture-client-side.asciidoc b/documentation/architecture/architecture-client-side.asciidoc index 63f62bcd63..2d62f912e5 100644 --- a/documentation/architecture/architecture-client-side.asciidoc +++ b/documentation/architecture/architecture-client-side.asciidoc @@ -24,9 +24,9 @@ and Vaadin-specific widgets. The two widget collections have significant overlap, where the Vaadin widgets provide a bit different features than the GWT widgets. In addition, many add-on widgets and their server-side counterparts exist, and you can easily download and install them, as described in -<<dummy/../../../framework/addons/addons-overview.asciidoc#addons.overview,"Using +<<../addons/addons-overview.asciidoc#addons.overview,"Using Vaadin Add-ons">>. You can also develop your own widgets, as described in -<<dummy/../../../framework/clientside/clientside-overview.asciidoc#clientside.overview,"Client-Side +<<../clientside/clientside-overview.asciidoc#clientside.overview,"Client-Side Vaadin Development">>. The rendering with widgets, as well as the communication to the server-side, is @@ -36,5 +36,5 @@ each widget that has a server-side counterpart. The framework handles serialization of component state transparently, and includes an RPC mechanism 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 +<<../gwt/gwt-overview.asciidoc#gwt.overview,"Integrating with the Server-Side">>. |