[PJUG Javamail] GWT

[James Perkins]

I would hardly say DART is the new version of GWT. They're quite different.
You write GWT applications in Java. You write DART in DART.
--
James R. Perkins


On Tue, Apr 10, 2012 at 12:18, Umesh Gohil <gohilumesh at hotmail.com> wrote:

>
> DART is new version of GWT. So if you are building new website I think you
> should stick to HTML5 coz most of feature are now available in HTML5.
>
> For eg : Like Drag and Drop
>
> We used GWT in our project coz most of developer were not aware of OOP
> javascript, Debugging in javascript and so on.
>
> So it was easy for us to build anything in java ie GWT and that is reason
> why we have gone for it.
>
> @Umesh
>
>
> > Date: Tue, 10 Apr 2012 09:47:09 -0700
> > From: gandracu+pjug at gmail.com
> > To: michaelvk at gmail.com
> > CC: javamail at pjug.org
> > Subject: Re: [PJUG Javamail] GWT
>
> >
> > Like any other framework or technology, GWT can be misused to create
> > functionality that is hard to maintain and extend. GWT was very easy
> > to misuse before the introduction of the newer features -- the MVP
> > framework, UI Binder, [fill in your favorite feature here]. Some of
> > the widgets were pretty rudimentary in the 1.* versions. I rarely have
> > to worry about browser issues, and when I do I never, ever "clean up
> > generated Javascript", but rather rewrite some UI component to work
> > around box model issues. Of course, just because I don't have to do
> > something doesn't mean that nobody else does.
> >
> > If you're just building UI, perhaps GWT is overkill. If you're
> > building a full-fledged web app, GWT gives you a lot and all it asks
> > for is patterns and common sense.
> >
> > Vid
> >
> > On Tue, Apr 10, 2012 at 9:27 AM, Michael Van Kleeck <michaelvk at gmail.com>
> wrote:
> > > My current company has a GWT UI that we're maintaining and extending
> to add new features. I previously have worked on two other GWT UI's that we
> built from scratch at other clients. My experience is that GWT is great for
> building new UI's, but it's not particularly maintainable or extensible. I
> went through the ordeal of trying to add a single menu item to the existing
> UI yesterday, and it took about 3 hours of config file modifications, code
> generation, and working with the GWT compiler to figure out just what all
> was needed to get a new item in the existing UI. (resource files, UI
> binders, CSS with names that bind to names in Java files, etc...)
> > >
> > > And GWT doesn't solve the eternal IE 7/8 compatibility issues for
> UI's, despite the write-once, run anywhere promises (oh, Java...). Trying
> to clean up GWT-generated Javascript for IE- that's weekends of support fun!
> > >
> > > More recent versions of GWT might solve some of these issues- our UI
> is built on some version of GWT 1.
> > >
> > > If I were building a new UI today, from scratch, I'd probably go with
> jQuery or some other Javascript libraries calling into a service layer.
> Javascript is quick to write and easy to throw away when product teams
> decide they need new features or a new UI. GWT's complexity makes it fine
> for developing long-lived applications, but modern UI's are fairly
> disposable, and GWT is just too complex for rapid release cycles, IMHO.
> > >
> > > -Michael
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Web Site - http://www.pjug.org/
> > > Javamail mailing list
> > > Javamail at pjug.org
> > > http://www.pjug.org/mailman/listinfo/javamail
> > _______________________________________________
> > Web Site - http://www.pjug.org/
> > Javamail mailing list
> > Javamail at pjug.org
> > http://www.pjug.org/mailman/listinfo/javamail
>
> _______________________________________________
> Web Site - http://www.pjug.org/
> Javamail mailing list
> Javamail at pjug.org
> http://www.pjug.org/mailman/listinfo/javamail
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://javac.com/pipermail/javamail/attachments/20120410/d1d72ba5/attachment-0002.html>