and the application starts with a [[JavaFX]] WebView and displays your page in it. More info at [[DukeScript]] [https://dukescript.com/update/2015/02/05/New-Version-of-Dukescript.html getting started] page.

and the application starts with a [[JavaFX]] WebView and displays your page in it. More info at [[DukeScript]] [https://dukescript.com/update/2015/02/05/New-Version-of-Dukescript.html getting started] page.

<source lang="java">

<source lang="java">

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.html \

$ mvn archetype:generate \

-DarchetypeArtifactId=knockout4j-archetype \

-DarchetypeGroupId=com.dukescript.archetype \

-DarchetypeVersion=1.1.2 \

-DarchetypeArtifactId=knockout4j-archetype \

-Dbck2brwsr=true

-DarchetypeVersion=0.16

-Dwebpath=client-web

</source>

</source>

Possibly replace the ''1.1.2'' version with newer version if/when available.

Possibly replace the ''0.16'' version with newer version if/when available.

[[Maven]] will download its libraries. Then it asks few questions (for example name of the project you want to create) and generates the skeleton project for you. When the project is successfully created, switch to the created subfolder and execute following command in it

[[Maven]] will download its libraries. Then it asks few questions (for example name of the project you want to create) and generates the skeleton project for you. When the project is successfully created, switch to the created subfolder and execute following command in it

<source lang="bash">

<source lang="bash">

$ mvn -Pfxbrwsr clean package exec:java

$ mvn package

$ mvn -f client process-classes exec:exec

</source>

</source>

<source lang="bash">

<source lang="bash">

$ mvn -Pbck2brwsr clean package bck2brwsr:show

$ mvn -f client-web clean package -DskipTests bck2brwsr:show

</source>

</source>

<source lang="bash">

<source lang="bash">

$ mvn clean install -Pbck2brwsr

$ mvn clean install

$ unzip target/*.zip

$ unzip client-web/target/*-bck2brwsr.zip

# to test it try firefox

# to test it try firefox

$ firefox public_html/index.html

$ firefox public_html/index.html

When unzipped on the server, it is also wise idea to configure it to serve the ''bck2brwsr.js'' as a [[GZip]]ed file. That will get its size to ~200KB.

When unzipped on the server, it is also wise idea to configure it to serve the ''bck2brwsr.js'' as a [[GZip]]ed file. That will get its size to ~200KB.

==== [[Eclipse]] Support ====

==== [[Eclipse]] Support ====

<source lang="bash">

<source lang="bash">

$ mvn clean install -Pfxbrwsr

$ mvn -Pdesktop -f client clean install

$ unzip target/*zip

$ unzip client/target/*-javafx.zip

$ java -jar *-fxbrwsr/*jar

$ java -jar *-app/*jar

</source>

</source>

and the application starts with a [[JavaFX]] WebView and displays your page in it.

and the application starts with a [[JavaFX]] WebView and displays your page in it. More info at [[DukeScript]] [https://dukescript.com/update/2015/02/05/New-Version-of-Dukescript.html getting started] page.

=== Old Archetype with Query API ===

=== Old Archetype with Query API ===

The latest archetype now focuses on integration with [[Knockout4Java]] and its execution in [[Bck2Brwsr]] (for deployment) and [[FXBrwsr]] (for debugging) modes:

The latest archetype now focuses on integration with [[Knockout4Java]] and its execution in [[Bck2Brwsr]] (for deployment) and [[FXBrwsr]] (for debugging) modes:

<source lang="java">\

<source lang="java">

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.html \

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.html \

-DarchetypeArtifactId=knockout4j-archetype \

-DarchetypeArtifactId=knockout4j-archetype \

The latest archetype now focuses on integration with [[Knockout4Java]] and its execution in [[Bck2Brwsr]] (for deployment) and [[FXBrwsr]] (for debugging) modes:

The latest archetype now focuses on integration with [[Knockout4Java]] and its execution in [[Bck2Brwsr]] (for deployment) and [[FXBrwsr]] (for debugging) modes:

<source lang="java">

<source lang="java">\

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.bck2brwsr \

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.html \

-DarchetypeArtifactId=knockout4j-archetype -DarchetypeVersion=0.8.1

-DarchetypeArtifactId=knockout4j-archetype \

-DarchetypeVersion=1.1.2 \

</source>

</source>

Possibly replace the ''0.8.1'' version with ''0.9-SNAPSHOT'' or newer versions when available.

Possibly replace the ''1.1.2'' version with newer version if/when available.

[[Maven]] will download its libraries. Then it asks few questions (for example name of the project you want to create) and generates the skeleton project for you. When the project is successfully created, switch to the created subfolder and execute following command in it

[[Maven]] will download its libraries. Then it asks few questions (for example name of the project you want to create) and generates the skeleton project for you. When the project is successfully created, switch to the created subfolder and execute following command in it

<source lang="bash">

<source lang="bash">

$ mvn process-classes bck2brwsr:brwsr -Pfxbrwsr

$ mvn -Pfxbrwsr clean package exec:java

</source>

</source>

<source lang="bash">

<source lang="bash">

$ mvn process-classes bck2brwsr:brwsr -Pbck2brwsr

$ mvn -Pbck2brwsr clean package bck2brwsr:show

</source>

</source>

==== [[Eclipse]] Support ====

==== [[Eclipse]] Support ====

Yesterday we (Jonathan Fuerth watched be me) managed to open the generated (and compiled) project in [[Eclipse]]. Showed up without errors after adding ''target/generated-sources/annotations/'' as additional source path root. The support for [[AnnotationProcessor]]s was limited, when we added new ''@Property(...)'', we needed to recompile for the IDE to realize what is going on. However the behavior seems acceptable and certainly better than I expected given the fact nobody tested it and designed for it yet.

Yesterday we (Jonathan Fuerth watched by me) managed to open the generated (and compiled) project in [[Eclipse]]. Showed up without errors after adding ''target/generated-sources/annotations/'' as additional source path root. The support for [[AnnotationProcessor]]s was limited, when we added new ''@Property(...)'', we needed to recompile for the IDE to realize what is going on. However the behavior seems acceptable and certainly better than I expected given the fact nobody tested it and designed for it yet.

==== Deploy as a Desktop Application ====

==== Deploy as a Desktop Application ====

<source lang="java">

<source lang="java">

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.bck2brwsr \

$ mvn archetype:generate -DarchetypeGroupId=org.apidesign.bck2brwsr \

-DarchetypeArtifactId=knockout4j-archetype -DarchetypeVersion=0.8

-DarchetypeArtifactId=knockout4j-archetype -DarchetypeVersion=0.8.1

</source>

</source>

Possibly replace the ''0.8'' version with ''0.9-SNAPSHOT'' or newer versions when available.

Possibly replace the ''0.8.1'' version with ''0.9-SNAPSHOT'' or newer versions when available.

[[Maven]] will download its libraries. Then it asks few questions (for example name of the project you want to create) and generates the skeleton project for you. When the project is successfully created, switch to the created subfolder and execute following command in it

[[Maven]] will download its libraries. Then it asks few questions (for example name of the project you want to create) and generates the skeleton project for you. When the project is successfully created, switch to the created subfolder and execute following command in it

</source>

</source>

and the application start with a [[JavaFX]] WebView and displays your page in it.

and the application starts with a [[JavaFX]] WebView and displays your page in it.

=== Old Archetype with Query API ===

=== Old Archetype with Query API ===

==== [[Eclipse]] Support ====

==== [[Eclipse]] Support ====

Yesterday we (me and Jonathan Fuerth) managed to open the generated (and compiled) project in [[Eclipse]]. Showed up without errors after adding ''target/generated-sources/annotations/'' as additional source path root. The support for [[AnnotationProcessor]]s was limited, when we added new ''@Property(...)'', we needed to recompile for the IDE to realize what is going on. However the behavior seems acceptable and certainly better than I expected given the fact nobody tested it and designed for it yet.

Yesterday we (Jonathan Fuerth watched be me) managed to open the generated (and compiled) project in [[Eclipse]]. Showed up without errors after adding ''target/generated-sources/annotations/'' as additional source path root. The support for [[AnnotationProcessor]]s was limited, when we added new ''@Property(...)'', we needed to recompile for the IDE to realize what is going on. However the behavior seems acceptable and certainly better than I expected given the fact nobody tested it and designed for it yet.

==== Deploy as a Desktop Application ====

==== Deploy as a Desktop Application ====

One can also build classical [[Java]] desktop application and deploy it to users as a [[ZIP]] file:

One can also build classical [[Java]] desktop application and deploy it to users as a [[ZIP]] file:

<source lang="java">

<source lang="bash">

$ mvn clean install -Pfxbrwsr

$ mvn clean install -Pfxbrwsr

$ unzip target/*zip

$ unzip target/*zip

Yesterday we (me and Jonathan Fuerth) managed to open the generated (and compiled) project in [[Eclipse]]. Showed up without errors after adding ''target/generated-sources/annotations/'' as additional source path root. The support for [[AnnotationProcessor]]s was limited, when we added new ''@Property(...)'', we needed to recompile for the IDE to realize what is going on. However the behavior seems acceptable and certainly better than I expected given the fact nobody tested it and designed for it yet.

Yesterday we (me and Jonathan Fuerth) managed to open the generated (and compiled) project in [[Eclipse]]. Showed up without errors after adding ''target/generated-sources/annotations/'' as additional source path root. The support for [[AnnotationProcessor]]s was limited, when we added new ''@Property(...)'', we needed to recompile for the IDE to realize what is going on. However the behavior seems acceptable and certainly better than I expected given the fact nobody tested it and designed for it yet.

=== Old Archetype with Query API ===

=== Old Archetype with Query API ===