Hi irc1258
I think that post is one of the most balanced, genuine and informative
I've come across on this subject.
Would you mind expanding on your experience on some of these issues?
1) You say "Very rich widgets compared with base GWT". What do you
mean by "rich" in this context? Is it look and feel, responsiveness,
functionality?
2) You say "Even given the learning curve, I still think it would have
taken longer to get the same functionality using just GWT." Which Ext
widgets, or what aspect of the framework, would you say gave you that
advantage?
regards
gregor
On Aug 28, 6:55 pm, dummymael <[EMAIL PROTECTED]> wrote:
> About the documentation, you might get what you want by looking at the
> ExtJS docs instead. And also note that GWT-Ext will only support up to
> the last LGPL release so I suggest you only look there and not on the
> later ones. The wrapper is true to the ExtJS API and its more or less
> the same, maybe some methods missing like setting text on the Grid's
> column label and the sort asc/desc labels. Also I've found that you
> don't get true oo especially if you want to extend a class from ExtJS
> (e.g. TreeNode). But all-in-all it has the most complete set of
> widgets from my GWT experience.
>
> As for alternatives, you might want to try out the SmartGWT wrapper
> for SmartClient. The author is also the founder of GWT-Ext (Sanjiv).
>
> On Aug 28, 10:59 pm, irc1258 <[EMAIL PROTECTED]> wrote:
>
> > I'm completely new to GWT and GWT-Ext and here is my experience using
> > GWT-Ext
>
> > 1. Very rich widgets compared with base GWT.
> > 2. The learning curve is very steep because:
> > * Because of the rich functionality, the toolkit is fairly complex.
> > * Virtually no documentation.
> > * Many requests for help go unanswered.
> > 3. I have encountered not any bugs that I know of.
>
> > If I had it to do over again, I would probably still use GWT-Ext over
> > straight GWT. Even given the learning curve, I still think it would
> > have taken longer to get the same functionality using just GWT.
>
> > If you use GWT-Ext, be prepared to:
> > - Spend lots of time looking at the showcase and the accompanying
> > source code.
> > - Search the forum for answers.
> > - Ask for help on the forum.
> > - Have your patience strained on occasion.
>
> > On Aug 28, 8:16 am, masterGaurav <[EMAIL PROTECTED]> wrote:
>
> > > Hi,
>
> > > I had a word with the Tatami team. And I think our approaches are
> > > different... at least they seem to at the moment.
>
> > > Tatami is a wrapper on Dojo Widgets... and as such, I personally feel
> > > that extending it going to be a real challenge. For example, to create
> > > a "DateTimePicker", it calls the native
> > > "$wnd.dijit.form.DateTimePicker" object for instantiation and
> > > initialization.
>
> > > On the other hand, DWT is porting Dojo for GWT - as you say,
> > > "rewriting the widgets with GWT". It does not mean 100% rewrite in
> > > GWT. Base Dojo (Dojo-core) may be used as is. My initial focus is to
> > > port Widgeting System (Dijit) with GWT. Subsequently, any calls to the
> > > dojo-core would be gradually ported.
>
> > > I am targeting my first "Button" to "alert('Hello, World!')" to be
> > > ready sometime in the 2nd week of September. Right now, my all energy
> > > is going into implementing the "Template Engine".
>
> > > Catch up soon with updates...
>
> > > --
> > > Happy Hacking,
> > > Gauravhttp://sf.net/projects/dwthttp://eduzine.edujini-labs.comhttp://blogs...
> > > ------------------------------
>
> > > On Aug 28, 1:30 pm, "David Clément" <[EMAIL PROTECTED]> wrote:
>
> > > > Hi!
>
> > > > Are your developping a wrapper or are you rewriting the widgets with
> > > > GWT?
>
> > > > There is another project working with DOJO
> > > > :http://code.google.com/p/tatami/.
>
> > > > Are you going to implement widgets that are not implemented by this
> > > > project?
>
> > > > Let us know when you have your first demo ready!
>
> > > > --
> > > > David
>
> > > > On Thu, Aug 28, 2008 at 8:18 AM, masterGaurav <[EMAIL PROTECTED]> wrote:
>
> > > > > Hi All,
>
> > > > > For the pure-JavaScript side, I personally love Dojo Toolkit for
> > > > > various reasons:
>
> > > > > 1) Maturity of the toolkit over last few years
> > > > > 2) License (See:http://dojotoolkit.org/license)
> > > > > 3) Out-of-the-box Widgets
> > > > > 4) Features: Support for template-based widget, Django-templates,
> > > > > Offline support using Google Gears etc. Just fantastic.
> > > > > 5) Support (See:http://dojotoolkit.org/foundation)
>
> > > > > If you're looking for something on GWT -- you may have to wait.
> > > > > DWT - Dojo on GWT - is something that I am currently working on. But
> > > > > it's only a few weeks old, may take at least 3-4 months to have only
> > > > > the "Widgets" ready.
>
> > > > > --
> > > > > Happy Hacking,
> > > > > Gaurav
> > > > >http://sf.net/projects/dwt
> > > > >http://eduzine.edujini-labs.com
> > > > >http://blogs.mastergaurav.com
> > > > > ------------------------------
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
