<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to FAQ</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>Recent changes to FAQ</description><atom:link href="https://sourceforge.net/p/ondofaristo/wiki/FAQ/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 24 Dec 2013 20:55:47 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ondofaristo/wiki/FAQ/feed" rel="self" type="application/rss+xml"/><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v15
+++ v16
@@ -15,7 +15,7 @@
     * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo ([dojo.declare](https://dojotoolkit.org/reference-guide/1.6/dojo/declare.html)). This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.

     * Speed-issues caused by Angular's dirty-checking system
-The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
+The documentation of Angularjs [itself says](http://docs.angularjs.org/guide/introduction) that :
     *Games and GUI editors are examples of applications with intensive and tricky DOM     manipulation. These kinds of apps are different from CRUD apps, and as a result are probably not a good fit for Angular.*
     * Two-way databinding and the use of directives are features which are already available in Dojo for a long time.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Tue, 24 Dec 2013 20:55:47 -0000</pubDate><guid>https://sourceforge.net0397cd8a779d973b1662f10428ad77ce28192df8</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v14
+++ v15
@@ -6,7 +6,7 @@

     * Backwards compatibility
     * Conserve the collective knowledge which will become useless in time because the original Wavemaker code-base will be thrown away by Cloudjee.
-    * No trust that Cloudjee can deliver a stable release based on AngularJS within 2 years which will have at least the same functionality as WM6.6.
+    * No trust that Cloudjee can deliver a stable release based on AngularJS within 2 years (october 2013) which will have at least the same functionality as WM6.6.

 + **What are the objections against Cloudjee policy to use Angularjs as the foundation framework for future releases?**

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Mon, 09 Dec 2013 16:14:09 -0000</pubDate><guid>https://sourceforge.nete7a90ab3c281058851ec1d2b72413ec85b130298</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v13
+++ v14
@@ -12,7 +12,7 @@

     * Thirst it must be said that this is not a matter of which Java-script framework is the best.

-    * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo ([dojo.declare)[https://dojotoolkit.org/reference-guide/1.6/dojo/declare.html]. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
+    * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo ([dojo.declare](https://dojotoolkit.org/reference-guide/1.6/dojo/declare.html)). This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.

     * Speed-issues caused by Angular's dirty-checking system
 The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
@@ -21,7 +21,7 @@

     * angularjs is not a toolkit but a framework-library.

-    * Though within [Google Trends](http://www.google.com/trends/explore?q=dojo#q=dojo%2C%20Angularjs%2C%20jquery&amp;amp;cmpt=q) it seems that Dojo is not used very much compared to Jquery and Angularjs is running up, it has to be said that a lot of internal business applications(which are not reachable by google) are build with Dojotools. For example [IBM is a large sponsor and user](https://www.google.nl/#q=site:ibm.com+and+dojo&amp;amp;safe=off&amp;amp;tbs=qdr:m) of Dojotools. 
+    * Though within [Google Trends](http://www.google.com/trends/explore?q=dojo#q=dojo%2C%20Angularjs%2C%20jquery&amp;amp;cmpt=q) it seems that Dojo is not used very much compared to Jquery and Angularjs is running up, it has to be said that a lot of internal business applications(which are not reachable by Google) are build with Dojotools. For example [IBM is a large sponsor and user](https://www.google.nl/#q=site:ibm.com+and+dojo&amp;amp;safe=off&amp;amp;tbs=qdr:m) of Dojotools. 

 + **Are Ondofaristo's version and Cloudjee's new versions compatible?**
 It depends on if and how Cloudjee keeps the current Java-script page-template with widget definitions for the front-end. For sure the look of the generated applications will be different because Cloudjee's widgets will be based on Jquery while OndoFaristo's source-base  will stay on Dojo widgets (but Jquery widgets can be build as custom components)
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Wed, 13 Nov 2013 13:23:00 -0000</pubDate><guid>https://sourceforge.netab0f3b261fd91b26807b77bc8469346f955a537f</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v12
+++ v13
@@ -12,7 +12,7 @@

     * Thirst it must be said that this is not a matter of which Java-script framework is the best.

-    * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
+    * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo ([dojo.declare)[https://dojotoolkit.org/reference-guide/1.6/dojo/declare.html]. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.

     * Speed-issues caused by Angular's dirty-checking system
 The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Wed, 13 Nov 2013 13:21:57 -0000</pubDate><guid>https://sourceforge.net4b551102c292bebf856392ac4a454734cc4615ae</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v11
+++ v12
@@ -10,18 +10,18 @@

 + **What are the objections against Cloudjee policy to use Angularjs as the foundation framework for future releases?**

-Thirst it must be said that this is not a matter of which Java-script framework is the best.
+    * Thirst it must be said that this is not a matter of which Java-script framework is the best.

-* Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
+    * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.

-* Speed-issues caused by Angular's dirty-checking system
+    * Speed-issues caused by Angular's dirty-checking system
 The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
     *Games and GUI editors are examples of applications with intensive and tricky DOM     manipulation. These kinds of apps are different from CRUD apps, and as a result are probably not a good fit for Angular.*
-* Two-way databinding and the use of directives are features which are already available in Dojo for a long time.
-* angularjs is not a toolkit but a framework-library.
+    * Two-way databinding and the use of directives are features which are already available in Dojo for a long time.
+    
+    * angularjs is not a toolkit but a framework-library.

-
-* Though within [Google Trends](http://www.google.com/trends/explore?q=dojo#q=dojo%2C%20Angularjs%2C%20jquery&amp;amp;cmpt=q) it seems that Dojo is not used very much compared to Jquery and Angularjs is running up, it has to be said that a lot of internal business applications(which are not reachable by google) are build with Dojotools. For example [IBM is a large sponsor and user](https://www.google.nl/#q=site:ibm.com+and+dojo&amp;amp;safe=off&amp;amp;tbs=qdr:m) of Dojotools. 
+    * Though within [Google Trends](http://www.google.com/trends/explore?q=dojo#q=dojo%2C%20Angularjs%2C%20jquery&amp;amp;cmpt=q) it seems that Dojo is not used very much compared to Jquery and Angularjs is running up, it has to be said that a lot of internal business applications(which are not reachable by google) are build with Dojotools. For example [IBM is a large sponsor and user](https://www.google.nl/#q=site:ibm.com+and+dojo&amp;amp;safe=off&amp;amp;tbs=qdr:m) of Dojotools. 

 + **Are Ondofaristo's version and Cloudjee's new versions compatible?**
 It depends on if and how Cloudjee keeps the current Java-script page-template with widget definitions for the front-end. For sure the look of the generated applications will be different because Cloudjee's widgets will be based on Jquery while OndoFaristo's source-base  will stay on Dojo widgets (but Jquery widgets can be build as custom components)
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Wed, 13 Nov 2013 13:19:00 -0000</pubDate><guid>https://sourceforge.net72a71164917866ea74607c81f17e804842d5e829</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v10
+++ v11
@@ -5,7 +5,7 @@
 1. **What are the main considerations to fork Wavemaker ?**

     * Backwards compatibility
-    * Conserve the collective knowledge which will get useless in time because the original Wavemaker code-base will be thrown away by Cloudjee.
+    * Conserve the collective knowledge which will become useless in time because the original Wavemaker code-base will be thrown away by Cloudjee.
     * No trust that Cloudjee can deliver a stable release based on AngularJS within 2 years which will have at least the same functionality as WM6.6.

 + **What are the objections against Cloudjee policy to use Angularjs as the foundation framework for future releases?**
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Wed, 13 Nov 2013 13:16:57 -0000</pubDate><guid>https://sourceforge.netbc45cc12a377e8cf56a4ec1a7c18a87285f36697</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v9
+++ v10
@@ -2,7 +2,7 @@

 Frequently asked questions
 ==========================
-1. **What are the considerations to fork Wavemaker ?**
+1. **What are the main considerations to fork Wavemaker ?**

     * Backwards compatibility
     * Conserve the collective knowledge which will get useless in time because the original Wavemaker code-base will be thrown away by Cloudjee.
@@ -13,8 +13,13 @@
 Thirst it must be said that this is not a matter of which Java-script framework is the best.

 * Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
-* The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
+
+* Speed-issues caused by Angular's dirty-checking system
+The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
     *Games and GUI editors are examples of applications with intensive and tricky DOM     manipulation. These kinds of apps are different from CRUD apps, and as a result are probably not a good fit for Angular.*
+* Two-way databinding and the use of directives are features which are already available in Dojo for a long time.
+* angularjs is not a toolkit but a framework-library.
+

 * Though within [Google Trends](http://www.google.com/trends/explore?q=dojo#q=dojo%2C%20Angularjs%2C%20jquery&amp;amp;cmpt=q) it seems that Dojo is not used very much compared to Jquery and Angularjs is running up, it has to be said that a lot of internal business applications(which are not reachable by google) are build with Dojotools. For example [IBM is a large sponsor and user](https://www.google.nl/#q=site:ibm.com+and+dojo&amp;amp;safe=off&amp;amp;tbs=qdr:m) of Dojotools. 

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Wed, 13 Nov 2013 12:18:50 -0000</pubDate><guid>https://sourceforge.net1b327f36f3d33d7f800a402200bbacb94d53b7fb</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v8
+++ v9
@@ -2,7 +2,6 @@

 Frequently asked questions
 ==========================
-
 1. **What are the considerations to fork Wavemaker ?**

     * Backwards compatibility
@@ -10,10 +9,14 @@
     * No trust that Cloudjee can deliver a stable release based on AngularJS within 2 years which will have at least the same functionality as WM6.6.

 + **What are the objections against Cloudjee policy to use Angularjs as the foundation framework for future releases?**
+
 Thirst it must be said that this is not a matter of which Java-script framework is the best.
-    * Wavemaker is currently (version 6.6.M3) developped fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
-    * The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
+    
+* Wavemaker is currently (version 6.6.M3) developed fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
+* The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
     *Games and GUI editors are examples of applications with intensive and tricky DOM     manipulation. These kinds of apps are different from CRUD apps, and as a result are probably not a good fit for Angular.*
+
+* Though within [Google Trends](http://www.google.com/trends/explore?q=dojo#q=dojo%2C%20Angularjs%2C%20jquery&amp;amp;cmpt=q) it seems that Dojo is not used very much compared to Jquery and Angularjs is running up, it has to be said that a lot of internal business applications(which are not reachable by google) are build with Dojotools. For example [IBM is a large sponsor and user](https://www.google.nl/#q=site:ibm.com+and+dojo&amp;amp;safe=off&amp;amp;tbs=qdr:m) of Dojotools. 

 + **Are Ondofaristo's version and Cloudjee's new versions compatible?**
 It depends on if and how Cloudjee keeps the current Java-script page-template with widget definitions for the front-end. For sure the look of the generated applications will be different because Cloudjee's widgets will be based on Jquery while OndoFaristo's source-base  will stay on Dojo widgets (but Jquery widgets can be build as custom components)
@@ -28,5 +31,3 @@
 + **Why Dojotoolkit ? **
 The main reason is one-stop-shop. Implementing a best-of-breed means that new dependencies enter the project. 

-+ **Which license is used?**
-[Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0)
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Wed, 13 Nov 2013 12:03:41 -0000</pubDate><guid>https://sourceforge.net0e02b0fde14feb6d868bde3d29cbe56522760bfd</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v7
+++ v8
@@ -11,7 +11,9 @@

 + **What are the objections against Cloudjee policy to use Angularjs as the foundation framework for future releases?**
 Thirst it must be said that this is not a matter of which Java-script framework is the best.
-    * Wavemaker is currently (version 6.6.M3) developped fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze
+    * Wavemaker is currently (version 6.6.M3) developped fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze.
+    * The documentation of Angularjs [itself says](docs.angularjs.org/guide/overview) that :
+    *Games and GUI editors are examples of applications with intensive and tricky DOM     manipulation. These kinds of apps are different from CRUD apps, and as a result are probably not a good fit for Angular.*

 + **Are Ondofaristo's version and Cloudjee's new versions compatible?**
 It depends on if and how Cloudjee keeps the current Java-script page-template with widget definitions for the front-end. For sure the look of the generated applications will be different because Cloudjee's widgets will be based on Jquery while OndoFaristo's source-base  will stay on Dojo widgets (but Jquery widgets can be build as custom components)
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Fri, 18 Oct 2013 21:25:08 -0000</pubDate><guid>https://sourceforge.net99d86181451940c48fddad6652a6836ac6052d78</guid></item><item><title>FAQ modified by Ondofaristo</title><link>https://sourceforge.net/p/ondofaristo/wiki/FAQ/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v6
+++ v7
@@ -14,7 +14,7 @@
     * Wavemaker is currently (version 6.6.M3) developped fully in Object Oriented *Programming* (OOP) style which is supported  by Dojo. This means that maintaining the Wavemaker code-base and extending the functionality is a breeze

 + **Are Ondofaristo's version and Cloudjee's new versions compatible?**
-It depends on if and how Cloudjee keeps the current Java-script page-template with widget definitions for the front-end. For sure the look of the generated applications will be different because Cloudjee's widgets will be based on Jquery while OndoAristo;s source-base  will stay on Dojo widgets (but Jquery widgets can be build as custom components)
+It depends on if and how Cloudjee keeps the current Java-script page-template with widget definitions for the front-end. For sure the look of the generated applications will be different because Cloudjee's widgets will be based on Jquery while OndoFaristo's source-base  will stay on Dojo widgets (but Jquery widgets can be build as custom components)
 The Java back-end will be compatible as long as Cloudjee keeps the Java source-code fully open-source.

 + **Does OndoFaristo have enough resources to maintain the source-code**
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ondofaristo</dc:creator><pubDate>Fri, 18 Oct 2013 21:18:03 -0000</pubDate><guid>https://sourceforge.net1a81b08c82798943945714d398c42045c39096c0</guid></item></channel></rss>