|Google Web Toolkit (GWT) tooling for WTP [message #170469]
||Sat, 03 June 2006 08:55
| Elias Balasis
Registered: July 2009
I have started building an eclipse project wizard for GWT.|
Quite soon I realized that this is the beginning of something far broader.
The idea of a tooling framework for WTP similar in concept to JSF tooling
platform, suddenly crossed my mind.
I will keep working on the subject on the purpose of learning eclipse
technologies but I could also actively contribute to a related eclipse
Please consider the idea of opening a related Eclipse project for GWT
|Re: Google Web Toolkit (GWT) tooling for WTP [message #170666 is a reply to message #170651]
||Mon, 05 June 2006 20:29
Originally posted by: thisisnot.mymail.com|
>> Please consider the idea of opening a related Eclipse project for GWT
> I like your enthusiasm but new projects can't simply be created at will.
> There is a process. Projects require proposals  and acceptance by
> Eclipse. Part of the acceptance process is to ensure that a project has
> adequate development resources and that the project addresses a need by
> the community.
>  http://www.eclipse.org/proposals/
If GWT was a tag library or a jsf component this would be a non-issue.
Although I like their thinking out of the box choosing a non standard
platform to develop a solution just makes it harder and more difficult
to invest in developing tools for it. As ajax is the cool buzzword of
the moment some investment in tooling will be made by the giants but I'd
be more inclined that things like DWR, dojo, prototype, moo.fx and
scriptaculus are to be more widely accepted. Perhaps the google guys
would like to donate some code to the WTP ajax project? What I would
like to see is better integration with the existing web frameworks (or a
more clearly documented point of integration), both controller or
Don't get down guys, if you believe in yourselves you can do it! A
project like this is ideal to excel in extending eclipse and I bet
Google might even add it to it's Summer of Code grants. Just open a
sourceforge project and start coding.
PS. I like the "There is a process" comment. It's a glimpse of how an
organization like IBM (or should I say the eclipse foundation?) must
think in order to keep large scale projects like these predictable. That
said, you can think out of the box :)
Anyhow, was the wtp/eclipse push in embedding ajax tooling something
hinted by the marketing/executive department or was it user feedback?
Powered by FUDForum
. Page generated in 0.01971 seconds