For the gwt-gdata project I routinely scan the HTML docs to determine
what has changed in each version, so that the GWT bindings can stay up
to date. I also use the scanned information to auto generate most of
the code and unit tests for the bindings, as well as for validating
the finished library.
The HTML that JSDoc generates is not at all easy to parse and is
likely to change overtime. I think in the GWT world this has the
potential to become almost a standard, since JS libraries using JSDoc
are one step away from having GWT bindings.
A JS library that exposes documentation in XML format is a GWT-
friendly library. :)
Thanks,
Monsur
- calendar.AllowGSync2Property - referenced from
calendar.CalendarEventFeed
- calendar.AllowGSyncProperty - referenced from
calendar.CalendarEventFeed
- contacts.ProfileEntry - referenced from contacts.ContactsService
- contacts.ProfileFeed - referenced from contacts.ContactsService
- contacts.PersonEntry - this class existed in 1.10, was it merged
with ProfileEntry? (i thought ProfileEntry extended PersonEntry)
Bobby