
Some parts of this message have been removed.
Learn more about Nabble's
security policy.
This looks very cool. With GWT 1.5 JavascriptObject, it will not be too hard to make a simple wrapper for dojo, and expressly for dijit in GWT. However, to preserve the architectural underpinings of dojo, I think it may be quite a bit of work. For example, you will need to support things like dojo.connect, since that is everywhere, and that may be trickier. I think some open conversations about how the dojo api ports to Java should be undertaken before too much coding is done. And I would really like to hear the thoughts of Alex and the other Dojo folks on what they see as the biggest issues are.
The other major issue in integration is seeing if you can bring the performance improvements offered by the GWT compiler and the Dojo build tools together somehow. A solution that could use GWT compiler and treat Dojo as a library of tools that could be selectively included in the build, inlined where necessary, etc. would be great. Because otherwise you will, by necessity have to have all of Dojo (built with appropriate layers) and all of GWT together on the page. That being said, a quick look at GWT-Ext show that that is exactly what they do on that project. In other words they do not worry about optimization of build, but only about creating a shim between the Ext api and a Java Api. An example: you could provide an API to dojo.query, but have it pass through to GQuery to save some code (maybe...)
I think this could be a really cool project, but I do think the API would need to be really well thought through for it to succeed... I would be interested in helping out in whatever way I could...
just my $0.02
-maulin
--
-maulin
_______________________________________________
FAQ:
http://dojotoolkit.org/support/faqBook:
http://dojotoolkit.org/docs/bookForums:
http://dojotoolkit.org/forumDojo-interest@...
http://turtle.dojotoolkit.org/mailman/listinfo/dojo-interest