Re: [gwt-contrib] now.. afetr GWT 2.0?
On Dec 17, 2009, at 3:03 PM, Arthur Kalmenson wrote: >> Working on a draft one. >> What do folks here think is important? > > - data binding and validation frameworks, which would remove a _lot_ > of boiler plate code and greatly increase productivity. > - incubator clean up and perhaps splitting it into multiple projects? Also, take a look at http://code.google.com/p/gwt-pectin/ that is a data binding and validation framework that uses HasValue as basis. It would also be neat with a "Enablable" interface to slap on everything that has setEnabled. > GWT 2.0 release is awesome, thanks for all the great work! > > -- > Arthur Kalmenson > > > > On Wed, Dec 16, 2009 at 12:01 PM, Bruce Johnson wrote: >> Working on a draft one. >> What do folks here think is important? >> >> On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: >>> >>> What about roadmap? >>> >>> -- >>> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
On Dec 17, 2009, at 3:03 PM, Arthur Kalmenson wrote: >> Working on a draft one. >> What do folks here think is important? > > - data binding and validation frameworks, which would remove a _lot_ > of boiler plate code and greatly increase productivity. Absolutely! > - incubator clean up and perhaps splitting it into multiple projects? Yes, It would be nice to clean up the scrolltable and put it in a separate project. > GWT 2.0 release is awesome, thanks for all the great work! I agree. Thank you! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
Here are the enhancements I would like to have in GWT : * incremental compilation to have the same ease of use than with php or jsp ; we have for instance an internal application where we have merged php and gwt, and (from the ease of modification point of view) it is always simpler to make a change or a patch on the php code than the gwt one. Incemental compilation should render these task simpler * compilation starting from .class and not from .java ; we could use gwt with code written in scala, groovy or better javafx * include the javafx syntax in gwt for describing UI instead of UIBinder (I hate xml for doing UI) ; we could even use the "bind" javafx feature in gwt, which could improve greatly the way of writing applications * refactoring theme management ; it fits not well with css way of doing things ; it is to complicated and not flexible enough * include html5 websockets * "desktop mode gwt" like AIR ou Silverlight * notion of timeline and states like in javafx or flash * eclipse/netbeans ui composer plugin * mobile and desktop profiles * launch the browser and set the url in it when running an application in development mode * OSGI-like mode to perfomr modularity and enabling to load only some features for a specific user * ... regards Xavier -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
1) Databinding a la Adobe Flex (they have *by far* the best solution[1] I've seen in all these toolkits). The GWT1.6 'HasValue' interface is a good starting point for this, hopefully it mixes well with UiBinder. 2) Scala compiler! 3) Make Compiler commandline options available to the Linker/Generator components. In my linker I'd like to know where the source webapp folder is, for instance. Having said that, GWT2.0 is an excellent piece of software with which I'm able to create excellent (mobile) web solutions. Thanks team! Cheers, Bart Guijt E: bgu...@gmail.com T: +31 6 30408987 On Wed, Dec 16, 2009 at 12:01 PM, Bruce Johnson wrote: > Working on a draft one. > What do folks here think is important? > > On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: >> >> What about roadmap? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
> Working on a draft one. > What do folks here think is important? - data binding and validation frameworks, which would remove a _lot_ of boiler plate code and greatly increase productivity. - incubator clean up and perhaps splitting it into multiple projects? GWT 2.0 release is awesome, thanks for all the great work! -- Arthur Kalmenson On Wed, Dec 16, 2009 at 12:01 PM, Bruce Johnson wrote: > Working on a draft one. > What do folks here think is important? > > On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: >> >> What about roadmap? >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
I'd like to see SuggestBox get a little love. For example: http://code.google.com/p/google-web-toolkit/issues/detail?id=2311 http://code.google.com/p/google-web-toolkit/issues/detail?id=2739 http://code.google.com/p/google-web-toolkit/issues/detail?id=3409 And one of those issues links to this thread where I had some other thoughts on SuggestBox improvements: http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/83db777f0e0602d0 And if I could include a wish for future GPE development it would be wizards, automated refactorings, and reusable code templates. Things like: http://code.google.com/p/google-web-toolkit/issues/detail?id=3914 I already have at least one SuggestBox patch floating around out there. I'd be happy to update that and work on other SuggestBox features, too, in my "spare" time. If somebody with commit privs cares to buddy up for design and review, please feel free to contact me on or off list. :) Oh, and woohoo GWT 2.0! Go team! - Isaac On Wed, Dec 16, 2009 at 12:01 PM, Bruce Johnson wrote: > Working on a draft one. > What do folks here think is important? > > On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: >> >> What about roadmap? >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
> 3) DataBinding & Validation (btw see this post from Ray announcing something > for Q1 2009 ;-) For me, it's the main feature GWT should have. Next would be "pretty" widgets, Drag'n Drop (in the framework, GWT DnD is very good, but DnD deserve to be in the framework by itself). And on top of it, yes, the WYSIWYG Eclipse plugin (with databing and validation, it could make people more easily start with GWT!) Thank you for the usefull features of 2.0 (just devMode in Firefox is worth it)! -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
GWT 2.0 was so awesome, it'll be hard to top any of the new stuff with my feature wishlist. A few things I'd like: - moving as many compiler properties as possible into configuration properties so we can build an instrumented release (with type cast checking, assertions, emulated stack traces) at the same time as release that can be turned on via - A DOM object to represent the window - Less of a hit on first load in development mode - New linker that uses iframes with dynamic scripts and a more generic, more easily reusable hosted mode script Matt. On 2009-12-16, at 10:01 AM, Bruce Johnson wrote: > Working on a draft one. > > What do folks here think is important? > > On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: > What about roadmap? > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
Hey Bruce, GWT 2 has provided great features focusing on the hidden parts of the iceberg (devmode, codesplitting, clientbundle, ...). It would be great to focus 2.1 on the user experience and the visible part of the user framework. Here's my wish list : 0) More widgets/containers compliant with the new CSS Layout API to get rid of the RootPanel.get() 1) Enrich the existing widgets and provide a good user experience (not the 3 predefined awful themes ;-)). Copy/Paste Wave/adWords apps themes is a good starting point :-D. With a multiple windows management framework (docking, maximize, etc ...) 2) A real DataGrid (sorting, paging, filtering, async...). Maybe by Improving the design (and the look) of the current incubator ScrollTable 3) DataBinding & Validation (btw see this post from Ray announcing something for Q1 2009 ;-) -> http://groups.google.com/group/Google-Web-Toolkit-Contributors/browse_thread/thread/8c611ab8bb076ead?pli=1 4) Replace RemoteService and RemoteServiceServlet by deRPC "for real" 5) Provide a UiBinder WYSIWYG Eclipse plugin (this would be the killer app) 6) provide a framework for UiBinder custom parsers long term - 7) Rewrite entirely the compiler ;-) instant dev mode (to benefit from incremental compilation) and generate the permutations from .class, not source code (to facilitate other language integration) I didn't congratulate all the GWT team for this fantastic 2.0 release. Let me thank you once more (some of you deserve a vacation ;-)). Sami On Wed, Dec 16, 2009 at 6:01 PM, Bruce Johnson wrote: > Working on a draft one. > > What do folks here think is important? > > > On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: > >> What about roadmap? >> >> -- >> http://groups.google.com/group/Google-Web-Toolkit-Contributors >> > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
Re: [gwt-contrib] now.. afetr GWT 2.0?
Working on a draft one. What do folks here think is important? On Wed, Dec 16, 2009 at 7:42 AM, tfreitas wrote: > What about roadmap? > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
[gwt-contrib] now.. afetr GWT 2.0?
What about roadmap? -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
