Thanks Sumit, that's what i wanted to hear. I've added a project for the GData-GWT library: http://code.google.com/p/gdata-gwt-client/
Also, i managed to scrape the information in the JS Docs for GData (http://code.google.com/apis/gdata/jsdoc/1.8/index.html) so i'm looking to dynamically generate the GWT libraries using the overlay technique that you described - this way, i can easily keep it in sync with the GData JS library. If anyone reading this thread is interested in contributing to this project just let me know. Bobby On Apr 13, 5:37 pm, Sumit Chandel <[email protected]> wrote: > Hi Bobby, > Please check out replies inlined below: > > 1. I couldn't find a GData Library for GWT, did i miss it (i already > > > checked with the GData group)? I know GData has the Java API, but that > > (probably) won't compile to JavaScript. However, GData also has a JS > > API (the JS docs are here > >http://code.google.com/apis/gdata/jsdoc/1.8/index.html), > > so at a minimum we could wrap the JS API in a very thin GWT library - > > i'm wondering if this already exists or if it's planned as an addition > > to the list of GWT Google API Libraries (http://code.google.com/ > > webtoolkit/googleapilibraries.html). > > There currently aren't any plans to provide GData bindings in the GALGWT > project, but as you may know, the project is open source and we would > welcome any contributions if you were planning on creating bindings for the > GData JS library. > > > 2. In the scenario where you have an existing JS library that you want > > to make use of in GWT, what's the best, thinnest, way to to create a > > Java wrapper to the JS library? For example, we could create a Java > > class per JS class. The Java class could keep a reference to the > > native JSObject, and define the same properties and methods that the > > JS class provides but which delegate to the JS implementation via > > JSNI. The problem with this is that after compiling to JS, we end up > > with a JS wrapper around a JS object. Is there a better implementation > > approach that will avoid this? > > I think the easiest way to wrap the objects in the GData JS library is to > not actually wrap them, but overlay them with JavaScript Overlay Types (link > below). This is the technique that is used for the existing Google APIs that > have bindings in the GALGWT project and would be the easiest and best way to > provide support for GData bindings as well. The greatest thing about the > overlay technique is that there is zero overhead to pay for overlaying the > JS object. The one-to-one nature of the binding also makes it somewhat > intuitive for developers to follow documentation on the proper API as they > use it in their GWT project through GALGWT, so there's yet another win by > choosing the overlay strategy. > > JavaScript Overlay > Types:http://code.google.com/webtoolkit/doc/1.6/DevGuideCodingBasics.html#D... > > Hope that helps, > -Sumit Chandel > > > > - Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
