diff options
Diffstat (limited to 'documentation/application/application-architecture.asciidoc')
| -rw-r--r-- | documentation/application/application-architecture.asciidoc | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/application/application-architecture.asciidoc b/documentation/application/application-architecture.asciidoc index 5e87ea8531..a26edc77ad 100644 --- a/documentation/application/application-architecture.asciidoc +++ b/documentation/application/application-architecture.asciidoc @@ -50,19 +50,19 @@ The actual UI is shown in <<figure.application.architecture.example>>. .Simple hierarchical UI image::img/ui-architecture-hierarchical.png[width=70%, scaledwidth=90%] -Instead of building the layout in Java, you can also use a declarative design, as described later in <<dummy/../../../framework/application/application-declarative#application.declarative,"Designing UIs Declaratively">>. +Instead of building the layout in Java, you can also use a declarative design, as described later in <<application-declarative#application.declarative,"Designing UIs Declaratively">>. The examples given for the declarative layouts give exactly the same UI layout as built from the components above. The easiest way to create declarative designs is to use Vaadin Designer. The built-in components are described in -<<dummy/../../../framework/components/components-overview.asciidoc#components.overview,"User +<<../components/components-overview.asciidoc#components.overview,"User Interface Components">> and the layout components in -<<dummy/../../../framework/layout/layout-overview.asciidoc#layout.overview,"Managing +<<../layout/layout-overview.asciidoc#layout.overview,"Managing Layout">>. The example application described above just is, it does not do anything. User interaction is handled with event listeners, as described a bit later in -<<dummy/../../../framework/application/application-events#application.events,"Handling +<<application-events#application.events,"Handling Events with Listeners">>. [[application.architecture.architecture]] @@ -79,7 +79,7 @@ architectural patterns in Vaadin applications. The subsequent sections describe some basic application patterns. For more information about common architectures, see -<<dummy/../../../framework/advanced/advanced-architecture#advanced.architecture,"Advanced +<<../advanced/advanced-architecture#advanced.architecture,"Advanced Application Architectures">>, which discusses layered architectures, the Model-View-Presenter (MVP) pattern, and so forth. @@ -145,7 +145,7 @@ MyView myview = new MyView(); ---- For a more detailed description of [classname]#Composite# and [classname]#CustomComponent#, see -<<dummy/../../../framework/components/components-customcomponent#components.customcomponent,"Composition +<<../components/components-customcomponent#components.customcomponent,"Composition with Composite and CustomComponent">>. @@ -163,11 +163,11 @@ sub-views. .Navigation Between Views image::img/view-navigation-hi.png[width=80%, scaledwidth=100%] -The [classname]#Navigator# described in <<dummy/../../../framework/advanced/advanced-navigator#advanced.navigator,"Navigating in an Application">> is a view manager that provides a flexible way to navigate between views and sub-views, while managing the URI fragment in the page URL to allow bookmarking, linking, and going back in the browser history. +The [classname]#Navigator# described in <<../advanced/advanced-navigator#advanced.navigator,"Navigating in an Application">> is a view manager that provides a flexible way to navigate between views and sub-views, while managing the URI fragment in the page URL to allow bookmarking, linking, and going back in the browser history. Often Vaadin application views are part of something bigger. In such cases, you may need to integrate the Vaadin applications with the other website. -You can use the embedding techniques described in <<dummy/../../../framework/advanced/advanced-embedding#advanced.embedding,"Embedding UIs in Web Pages">>. +You can use the embedding techniques described in <<../advanced/advanced-embedding#advanced.embedding,"Embedding UIs in Web Pages">>. [[application.architecture.accessing]] @@ -206,5 +206,5 @@ You can get the page and the session also from a [classname]#UI# with The static methods use the built-in ThreadLocal support in the classes. ifdef::web[] -The pattern is described in <<dummy/../../../framework/advanced/advanced-global#advanced.global.threadlocal,"ThreadLocal Pattern">>. +The pattern is described in <<../advanced/advanced-global#advanced.global.threadlocal,"ThreadLocal Pattern">>. endif::web[] |