From a1b265c318dbda4a213cec930785b81e4c0f7d2b Mon Sep 17 00:00:00 2001
From: elmot <elmot@vaadin.com>
Date: Fri, 25 Sep 2015 16:40:44 +0300
Subject: Framework documentation IN

Change-Id: I767477c1fc3745f9e1f58075fe30c9ac8da63581
---
 .../clientsideapp/clientsideapp-compiling.asciidoc | 27 ++++++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 documentation/clientsideapp/clientsideapp-compiling.asciidoc

(limited to 'documentation/clientsideapp/clientsideapp-compiling.asciidoc')

diff --git a/documentation/clientsideapp/clientsideapp-compiling.asciidoc b/documentation/clientsideapp/clientsideapp-compiling.asciidoc
new file mode 100644
index 0000000000..fe790fa45e
--- /dev/null
+++ b/documentation/clientsideapp/clientsideapp-compiling.asciidoc
@@ -0,0 +1,27 @@
+---
+title: Compiling and Running a Client-Side Application
+order: 3
+layout: page
+---
+
+[[clientsideapp.compiling]]
+= Compiling and Running a Client-Side Application
+
+__Compilation of client-side modules other than widget sets with the Vaadin
+Plugin for Eclipse has recent changes and limitations at the time of writing of
+this edition and the information given here may not be accurate.__
+
+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
+<<dummy/../../../framework/clientside/clientside-compiling#clientside.compiling,"Compiling
+a Client-Side Module">>.
+
+During development, it is easiest to use the SuperDevMode, which also quickly
+launching the client-side code and also allows debugging. See
+<<dummy/../../../framework/clientside/clientside-debugging#clientside.debugging,"Debugging
+Client-Side Code">> for more details.
+
+
+
-- 
cgit v1.2.3

