Funny thing, someone just responded to one of my threads on the Ext
GWT forum and reminded me why I gave up on it: the crappy attitude of
the authors (summarized: it's not a bug, it's supposed to act
broken), even after I gave them code to fix their product.
To finish, my response is : no
I use GWT only and it's work very well.
On 28 déc 2009, 03:16, Chris Ramsdale cramsd...@google.com wrote:
While the information on this thread has become a bit passionate, it is all
good and relevant information. When building large scale GWT-based apps,
Incorrect, SmartGWT allows both. Purchasing a license does not imply
that you *must* use the closed-source server-side portion. If you use
just the capabilities of SmartGWT LGPL, you can offer the LGPL
licensing terms to customers that prefer it, and you can purchase a
license from Isomorphic to
Hmm, but if you want to use the server side code, the primary reason for
buying a license I'd guess because you have to be pretty crazy to be
concerned about LGPL for a widget library since that's a good thing, then
you'd likely include that code in your code base, so then you couldn't also
offer
I will be taking a look at QxWT. I still think there is a need for a
good widget library. I've been looking for alternatives. I used mygwt
but stop using it when they did the bait and switch lat year. I lost
several months of work and I'm still pissed. Also, I don't like that
they try to redo the
The list of widget libraries is exhausting mostly because it seems so retro.
If the desktop windowing world were this fragmented for GUIs, life would
have been harder.
And if developers had to worry about licensing issues to write GUIs, life
would have been harder. Widget libraries needs to be
On Dec 26 2009, 3:51 am, gaill...@audemat.com gaill...@audemat.com
wrote:
You can't stat about 'uninformed choice', quick doesn't mean dirty
Even creating new widgets could be made easily with GWT, with SmartGWT
we must have good javascript skill to achieve the same task
This statement is
I must also give a big thumbs-down to GXT. The licensing is annoying
and misleading, yes - you must buy support to get a usable version,
making it rather bait-and-switch - but I'm willing to pay for good
tools so that's not what I'm complaining about. If it did what it was
supposed to, it would
@Jeff,
If you went with straight-up GWT what did you do for all the various
widgets that otherwise seem powerful and useful?
For example, what are your replacements for:
1) Paging grid/tables for showing lists of objects/data that users can then
click on to view/edit in detail for typical CRUD
The problems with GXT are basically summed up by:
Not to dismiss your experience in anyway, but actually GXT to me seems
easier than Google's appengine. At least with GXT I can see the
source (well not of the current master branch but ...) to clarify what
something does. App-Engine is much
I find the type of complexity of BigTable to be far easier to
handle. BigTable operates in a consistent manner and once you
understand the basic principles (watch *all* of the Google I/O video)
everything pretty much makes sense. The type of complexity of GXT
is endless little unrelated errata
Yozons,
I apologize for the tone in my previous mail. I've been following the Ext /
GXT shenanigans for a long time now and have raised numerous issues with
them in the past as well on their licensing terms and numerous license
violations. The issues were either ignored or deleted from their
No problem It's all good!
Our architect is trying to contact them directly now because he said it
sounds so goofy he can't believe it's the case since the license itself has
no such references and claims to be the authoritative document (so anything
else on other pages would not supersede
@Yozons Support
GXT is not a wrapper of ExtJs. So you can not compare the current GXT
version with any of the existing extJS versions.
They try to produce an almost identically looking end product (extjs
vs. GXT). But the way how this is achived is technically different
(and also from a
Thanks. I just read about that, which means it should be even easier to
debug and work with for us Java folks. I like what I see in GXT so far, but
admittedly very little. I'm most interested in the DTO issue and if there
are good ways to send HashMaps and the like to avoid creating so many of
There are a few strategies for DTO and GXT. Here are two
http://www.extjs.com/helpcenter/index.jsp?topic=/com.extjs.gxt.help/html/tutorials/beanmodel.html
I also did some using Commons::BeanUtils to autopopulate a DTO since I
use Cayenne on the backend and it was not serializing very cleanly.
Just to mention that there are other Widget-Projects besides SmartGWT
and GXT. I'm working
on a library called QxWT [1] which works similar to SmartGWT by
wrapping an JavaScript-Library.
We are (yet) not at the point where GXT and SmartGWT are but we are
working hard on to get there. For me
and
Great - Yozons is already a confused person incapable of making any decision
by himself for *his* project and now you throw in another variable. I
suspect this might throw him in a further endless loop. Oh, btw there's also
gwt-mosaic and Vaadin. Make sure you evaluate those too and good luck
While the information on this thread has become a bit passionate, it is all
good and relevant information. When building large scale GWT-based apps,
developers typically sketch out the foundation and then immediately start
looking for a good widget add-on. Threads like this can be extremely useful
@Martin - Why would you want to attack me just because I'm evaluating
toolkits? I understand our application domain just fine, and we've built
multiple applications in JSP technologies that are in our area of expertise
and have been running a profitable software business for 10 years now.
@Martin
Regarding the below, can you point to the section that you read this
from @ http://www.extjs.com/store/extjs/license.php ?
Our reading of the license is that its a standard, straightforward,
developer seat + support model + 'no royalty/source release
requirement' which meshes with how
You can't stat about 'uninformed choice', quick doesn't mean dirty
Enough of us to quickly test and evaluate a new framework and SmartGWT
does'nt meat our requirement.
We are moving from java to GWT with our own framework and it was
really more easy to do it with GXT.
We have no needs to have
We'll investigate GXT as well. I have to say that the licensing is more
straightforward with GXT because the free/commercial tiers are not related
to functionality in GXT versus SGWT. But if you go want OSS in a commercial
product (cheap?), you'd need to stick with LGPL of SGWT over the GPL of
If the choice was made quickly it was probably an uninformed
choice. We don't have anyone complaining that there is less
customization so perhaps you could clarify that.
With SmartGWT Pro and EE, you can literally open up a visual tool and
create a fully functional CRUD interface to Hibernate by
With SmartGWT Pro and EE, you can literally open up a visual tool and
create a fully functional CRUD interface to Hibernate by just picking
an existing Hibernate entity from a list. That's not offered in any
other GWT product, and it would be hard to argue that anything could
be simpler or
On Dec 4th keyboard_samurai wrote :
Hi, I am a newbie to GWT.
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/2d66440f4c6a59f/449f9401e2d4ddd4
To the original poster : Make sure you do your own research too. There are a
lot of newbies on this board that love to give
developers in this group. I am starting
a project and am in a dilemma where to use smartgwt or not. There are
many advantages of using it (like filters/sorting in list grids etc).
However I think there will be many problems later on (for example
changing the design). Want to hear experienced
I use GXT (Ext GWT from extJS) for several months with JBOSS 5.1, the
choice was made quickly between SmartGWT and GXT, GXT offers greater
customization and management of bindings are perfect with annontations
provided by GXTForms 0.2. There is no need to use Gilead or
Hibernate4gwt.
--
You
I would agree on ext gwt .. Its faster and much better than smart gwt.
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
EXT is GPL while Smart is LGPL, and of course both offer commercial
licenses. LGPL can be used commercially, while GPL cannot, so that could be
a consideration. And of course commercial licenses are fine, unless your
code itself is going to be open source.
--
You received this message because
2009/12/17 azure rockan...@gmail.com:
Hi all,
There are many gwt experienced developers in this group. I am starting
a project and am in a dilemma where to use smartgwt or not. There are
many advantages of using it (like filters/sorting in list grids etc).
However I think there will be many
and am in a dilemma where to use smartgwt or not. There are
many advantages of using it (like filters/sorting in list grids etc).
However I think there will be many problems later on (for example
changing the design). Want to hear experienced people's voice.
--
You received this message because
We're just now evaluating this ourselves, but we do like the look of their
large variety of widgets, but it is big and takes time to really evaluate it
all and there are myriad options from LGPL through proprietary EE. No
doubt, much depends on your app's needs. Ours is more business-focused, so
Hi
I think these javascript wrappers will have a hard time, with all new
features coming from GWT.
Code split, UiBinder etc.. I am excited to see how they will integrate it.
I used ext-gwt, which had a pretty big startup-download-size. Unfotunally it
was javascript coming from EXT, and not
In the end, it's all JS to the client, so not sure what wrapper would
really mean. The downside may be they can't get the same optimizations that
come with the Java-to-JS compiler as it increases in capability and can gen
browser-specific versions.
But if you need to move now, GWT just doesn't
Hi all,
There are many gwt experienced developers in this group. I am starting
a project and am in a dilemma where to use smartgwt or not. There are
many advantages of using it (like filters/sorting in list grids etc).
However I think there will be many problems later on (for example
changing
Hi,
i have used smart gwt for some projects, and i was not impressed from smart
gwt, but it you decide smart gwt ee its good to use, but it is paid. So only
smart gwt is painful to integrate with your server side (at least it was
before 3 months). Also the widgets are a little slower than the
37 matches
Mail list logo
