aboutsummaryrefslogtreecommitdiffstats
path: root/jsquery/README.txt
diff options
context:
space:
mode:
authorManolo Carrasco <manolo@apache.org>2011-09-05 18:42:14 +0000
committerManolo Carrasco <manolo@apache.org>2011-09-05 18:42:14 +0000
commit987ce7f17fab929ca21e38289b4b88dea6fd2ee3 (patch)
tree27e52323734f6abfbfded37e1361c9265914a965 /jsquery/README.txt
parent4d91ee517b619b6e0526c4464f698aa8eb0a0081 (diff)
downloadgwtquery-987ce7f17fab929ca21e38289b4b88dea6fd2ee3.tar.gz
gwtquery-987ce7f17fab929ca21e38289b4b88dea6fd2ee3.zip
New gwt module to export gwtquery to javascript
Diffstat (limited to 'jsquery/README.txt')
-rw-r--r--jsquery/README.txt26
1 files changed, 26 insertions, 0 deletions
diff --git a/jsquery/README.txt b/jsquery/README.txt
new file mode 100644
index 00000000..32d45e37
--- /dev/null
+++ b/jsquery/README.txt
@@ -0,0 +1,26 @@
+
+This gwt module (JsQuery) allows to export gquery to javascript so as the exported
+javascript can be used as a substitute of jquery.
+
+* Compile:
+ - mvn package
+
+* Usage
+ - Copy the content of the folder target/_version_/jsquery to your webserver
+ - Include the script jsquery.nocache.js in your html files instead of jquery.js
+
+
+This is an experimental feature and not all of the methods in jquery are available,
+performance could be worst than jquery since gwtexporter needs to compute many runtime
+operations in order to figure out which method execute and to wrap gwt objects to js
+objects and viceversa.
+
+There are many advantages in exporting gquery to js, but the main goal is to use jsni
+code from jquery plugins in gwt without porting this code to java.
+
+Right now most methods in GQuery class are exporte via JQ class, but plugin developers
+could select just the methods they need for their plugins.
+
+
+
+- Manolo