From 0b7457325200162961cae52e7d871db928dc3cd9 Mon Sep 17 00:00:00 2001 From: Zhe Sun <31067185+ZheSun88@users.noreply.github.com> Date: Thu, 23 May 2019 09:43:31 +0300 Subject: Update broken docs syntax in github (#11596) * Add delay to the unstable test * Add delay for unstable tests * Update broken docs syntax in github * Merge branch 'master' into ZheSun88-patch-1 * Update doc reference syntax * Merge branch 'ZheSun88-patch-1' of github.com:vaadin/framework into ZheSun88-patch-1 # Conflicts: # documentation/components/components-overview.asciidoc * Merge branch 'master' into ZheSun88-patch-1 * use .asciidoc * Merge remote-tracking branch 'origin/ZheSun88-patch-1' into ZheSun88-patch-1 * use .asciidoc * Merge branch 'master' into ZheSun88-patch-1 --- documentation/clientsideapp/clientsideapp-compiling.asciidoc | 4 ++-- .../clientsideapp/clientsideapp-entrypoint.asciidoc | 2 +- documentation/clientsideapp/clientsideapp-overview.asciidoc | 12 ++++++------ 3 files changed, 9 insertions(+), 9 deletions(-) (limited to 'documentation/clientsideapp') diff --git a/documentation/clientsideapp/clientsideapp-compiling.asciidoc b/documentation/clientsideapp/clientsideapp-compiling.asciidoc index fe790fa45e..59caf37ba2 100644 --- a/documentation/clientsideapp/clientsideapp-compiling.asciidoc +++ b/documentation/clientsideapp/clientsideapp-compiling.asciidoc @@ -15,12 +15,12 @@ The application needs to be compiled into JavaScript to run it in a browser. For deployment, and also initially for the first time when running the Development Mode, you need to do the compilation with the Vaadin Client Compiler, as described in -<>. During development, it is easiest to use the SuperDevMode, which also quickly launching the client-side code and also allows debugging. See -<> for more details. diff --git a/documentation/clientsideapp/clientsideapp-entrypoint.asciidoc b/documentation/clientsideapp/clientsideapp-entrypoint.asciidoc index 954922310b..00811cef38 100644 --- a/documentation/clientsideapp/clientsideapp-entrypoint.asciidoc +++ b/documentation/clientsideapp/clientsideapp-entrypoint.asciidoc @@ -47,7 +47,7 @@ described in the next section. The entry-point of a client-side application is defined, along with any other configuration, in a client-side module descriptor, described in -<>. The descriptor is an XML file with suffix [filename]#.gwt.xml#. diff --git a/documentation/clientsideapp/clientsideapp-overview.asciidoc b/documentation/clientsideapp/clientsideapp-overview.asciidoc index 95f32b105e..c24ffb0474 100644 --- a/documentation/clientsideapp/clientsideapp-overview.asciidoc +++ b/documentation/clientsideapp/clientsideapp-overview.asciidoc @@ -43,25 +43,25 @@ public class HelloWorld implements EntryPoint { The user interface of a client-side application is built under a HTML __root element__, which can be accessed by [methodname]#RootPanel.get()#. The purpose and use of the entry-point is documented in more detail in -<>. The user interface is built from __widgets__ hierarchically, just like with server-side Vaadin UIs. The built-in widgets and their relationships are catalogued in -<>. You can also use many of the widgets in Vaadin add-ons that have them, or make your own. A client-side module is defined in a __module descriptor__, as described in -<>. A module is compiled from Java to JavaScript using the Vaadin Compiler, of which use was described in -<>. The -<> in this chapter gives further information about compiling client-side applications. The resulting JavaScript can be loaded to any web page, as described in -<>. // TODO What is this? What's an "UI Binder"? -- cgit v1.2.3