I would like more control over which classes/packages were actually sucked into a module for compilation. I appreciate there are workarounds like sticking diff java files under diff src dirs but that's ugly.
I don't like how including a particular package also sucks in sub packages. I think it wouldbe better if it only did the specific pkg. Further ctrl over individually classes within an included pkg would be great. I have noticed rhat google collections marks a few classes with various annonations like gwt-compatible and gwt-not-compatible. It would be great if the compiler honoured these. Even finer grained ctrl over individual methods would be great.i f it worked like suppress warnings but instructed the compiler to ignore invompatible code that would be great. - Use cases include stuff like a class with lots of static helpers some intended just for the server others that also are useful under gwt. - sometimes it's usegful to overload a method to take types that are irrelevant or wrong in gwt - eg inputstream. Again one could take that helper and stick it somewhere else buts it's ugly to have the disconnect when they really belong together. Hyh On 19/12/2009, at 3:29 AM, Mauro <[email protected]> wrote: > Definitely, the most important thing for me is fix the bugs and above > all publish an excellent documentation and ... > > +1 for Databinding & Validation > +1 for a nice DataGrid > +1 for nicer widgets > > Great job on GWT 2.0 > > On 16 dez, 10:42, tfreitas <[email protected]> wrote: >> What about roadmap? > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
