Man, that would be nice.

First, to do this it needs to parse and understand any <super-source>
module entries in the module hieracharchy (including GWT's own emul
module) and build an index including only those classes and methods
defined. This is necessary because you can add your own emulated JDK
classes so use them in GWT (For example, I've added NavigableMap
support).

Using that, and all of the <source> paths defined in Modules within
your project, it could then flag any usage of undefined classes/
methods.

I'm guessing GPE doesn't do the required indexing in real time right
now, but it seems plausible that it could. Being able to see "GWT:
String.getBytes() has no translatable source" in the Problems view
would be just awesome. And there's probably a whole other class of
enhancements this sort of indexing capability could enable. How about
GWT-aware code completion when writing client side code, giving you
only the available methods and classes, preventing the problem in the
first place?

On May 24, 2:32 am, hezjing <[email protected]> wrote:
> Hi
>
> GWT emulates a subset of Java as described in GWT JRE
> documentation<http://code.google.com/intl/sv-SE/webtoolkit/doc/1.6/RefJreEmulation....>
> .
>
> Is Google plugin able to detect classes and methods in the client code which
> is not implemented by the GWT JRE?
> and marks these errors on the editor?
>
> For example, Google plugin should display an error when the developer enter
> String.getBytes() in the client code.
> Better still, if the code auto complete can filter the unsupported classes
> and methods.
>
> I'm not sure if this is doable though!
>
> --
>
> Hez
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to