GWT VS GWT-EXT
90 views
Skip to first unread message
Jason Essington
Jun 1, 2009, 10:50:14 AM6/1/09
to Google-We...@googlegroups.com
UHM ... that question is a bit confused.
GWT is the Toolkit in which GWT-EXT exists. without GWT there is not
GWT-EXT.
the EXT variants (GWT libraries based on EXT) seem to be rather
popular, but also seem to have more than their fair share of detractors.
You can search the list for information on the Pros and Cons of using
various external Libraries with GWT.
That said, I tend to try to stick to straight GWT (and occasionally
GWT-Incubator) for my projects. It reduces number of externally
induced headaches.
But, your situation may be different. Best to create a sample app
using the proposed libraries to determine if it is fit for your project.
-jason
> <firdaus_linux.vcf>
GWT is the Toolkit in which GWT-EXT exists. without GWT there is not
GWT-EXT.
the EXT variants (GWT libraries based on EXT) seem to be rather
popular, but also seem to have more than their fair share of detractors.
You can search the list for information on the Pros and Cons of using
various external Libraries with GWT.
That said, I tend to try to stick to straight GWT (and occasionally
GWT-Incubator) for my projects. It reduces number of externally
induced headaches.
But, your situation may be different. Best to create a sample app
using the proposed libraries to determine if it is fit for your project.
-jason
Amzad Basha
Jun 1, 2009, 7:18:39 AM6/1/09
to Google Web Toolkit
Please refer: http://gwt-ext.com/
Cheers!
Amzad Basha.
On May 31, 10:11 pm, Fitrah Elly Firdaus <firdaus.li...@gmail.com>
wrote:
> firdaus_linux.vcf
> < 1KViewDownload
Cheers!
Amzad Basha.
On May 31, 10:11 pm, Fitrah Elly Firdaus <firdaus.li...@gmail.com>
wrote:
> < 1KViewDownload
Adligo
Jun 1, 2009, 11:31:05 PM6/1/09
to Google Web Toolkit
Hi,
As I see the world, GWT is newer than EXT (javascript library) and
a lot more robust. GWT-EXT is a port of EXT so that it works with in
the GWT (java souce code) framework. In general they do the same
thing, GWT-EXT looks nicer, but GWT is more generally developer
friendly.
EXT was written by web developers and comes from a web developer
mind set (usually modifies the DOM directly), where GWT was written by
people who are web developers but have more of a traditional GUI
(Swing, SWT, AWT, VB exc) mindset (seems to have the concept of double
buffering, or in other words writing to a off screen DOM for things
that aren't visible).
However on the oppisite argument GWT-EXT has some featurs that are
built in to it, that GWT does not yet have. Most notibly Drag and
Droping Object between Grids (Tables) and Trees. Sorting in Grids and
dragging (reordering) columns in the Ext Grid. Another way of saying
this is that the GWT-EXT grid behaves like a swing Table, and the GWT
FlexTable behaves more like a swing Grid Bag Layout (for a panel).
Answering which one is 'Best' really depends on what your trying to
do...
Hope this helps,
Scott
As I see the world, GWT is newer than EXT (javascript library) and
a lot more robust. GWT-EXT is a port of EXT so that it works with in
the GWT (java souce code) framework. In general they do the same
thing, GWT-EXT looks nicer, but GWT is more generally developer
friendly.
EXT was written by web developers and comes from a web developer
mind set (usually modifies the DOM directly), where GWT was written by
people who are web developers but have more of a traditional GUI
(Swing, SWT, AWT, VB exc) mindset (seems to have the concept of double
buffering, or in other words writing to a off screen DOM for things
that aren't visible).
However on the oppisite argument GWT-EXT has some featurs that are
built in to it, that GWT does not yet have. Most notibly Drag and
Droping Object between Grids (Tables) and Trees. Sorting in Grids and
dragging (reordering) columns in the Ext Grid. Another way of saying
this is that the GWT-EXT grid behaves like a swing Table, and the GWT
FlexTable behaves more like a swing Grid Bag Layout (for a panel).
Answering which one is 'Best' really depends on what your trying to
do...
Hope this helps,
Scott
Sylvain
Jun 2, 2009, 6:39:33 AM6/2/09
to Google Web Toolkit
I started a GWT project and quickly had the need for more widgets than
what is provided in the standard SDK. GWT-EXT comes up consistently as
a popular library that provides widgets on top of GWT but when digging
into the implementation it is clear that it actually is a binding of a
Javascript UI library on top of the GWT framework.
The situation is tough for developers, it's a bit like the good old
days of Java 1.1 / 1.2 when the Netscape IFCs looked so much better
than the standard widgets and Swing was in it's infancy. At this point
and mostly influenced by the specific project I'm working on I've
decided to stick to GWT alone and not use a not-fully-native library
on top of it. It was a tough call to make, like every time one has to
choose between integrating a 3rd party library that may have long term
caveats or building from scratch and taking the hit upfront.
- Sylvain
On May 31, 8:11 pm, Fitrah Elly Firdaus <firdaus.li...@gmail.com>
wrote:
> firdaus_linux.vcf
> < 1KViewDownload
what is provided in the standard SDK. GWT-EXT comes up consistently as
a popular library that provides widgets on top of GWT but when digging
into the implementation it is clear that it actually is a binding of a
Javascript UI library on top of the GWT framework.
The situation is tough for developers, it's a bit like the good old
days of Java 1.1 / 1.2 when the Netscape IFCs looked so much better
than the standard widgets and Swing was in it's infancy. At this point
and mostly influenced by the specific project I'm working on I've
decided to stick to GWT alone and not use a not-fully-native library
on top of it. It was a tough call to make, like every time one has to
choose between integrating a 3rd party library that may have long term
caveats or building from scratch and taking the hit upfront.
- Sylvain
On May 31, 8:11 pm, Fitrah Elly Firdaus <firdaus.li...@gmail.com>
wrote:
> < 1KViewDownload
DaBlick
Jun 2, 2009, 1:29:03 PM6/2/09
to Google Web Toolkit
My understanding is that GWT-Ext development is halted.
Your mileage may be different, but if you are setting up your
technology stack, why pick something with no apparent future?
It's popular now but when something is not moving at all, other things
are bound to catch up and surpass it.
We're using Ext-GWT (also known as GXT) and are quite happy with
it. We've managed to build a HIGHLY stylized RIA with it such that
you'd barely know it was GWT or even GXT for that matter.
Your mileage may be different, but if you are setting up your
technology stack, why pick something with no apparent future?
It's popular now but when something is not moving at all, other things
are bound to catch up and surpass it.
We're using Ext-GWT (also known as GXT) and are quite happy with
it. We've managed to build a HIGHLY stylized RIA with it such that
you'd barely know it was GWT or even GXT for that matter.
Message has been deleted
Carl Pritchett
Jun 4, 2009, 9:00:19 PM6/4/09
to Google Web Toolkit
> My understanding is that GWT-Ext development is halted.
An active replacement is SmartGWT (has a "free" LGPL version).
Note that Ext-GWT is not free for commercial use - it uses GPL
licensing. I'm currently using it.
- Carl.
Adligo
Jun 5, 2009, 7:50:53 PM6/5/09
to Google Web Toolkit
This last statement seems to contradict it self so to ovoid any
confusion (as I and several others I have talked to are confused about
this);
GXT (Ext-GWT) does NOT use the GPL (License) it uses its own license
http://extjs.com/store/gxt/
And it Costs money
GWT-EXT does use GPL
http://code.google.com/p/gwt-ext/
And its free for commercial use like (svn, linux, gwt exc)
but if you modify it you must post your changes otherwise you will
get
in trouble with the free software foundation (like cisco did)
And now for a quesiton.
I know from using Gwt-Ext for a few months that a lot of the code is
acutally written in javascript (EXT, and some Flash for its Charts)
and GWT-EXT is a GWT adapter to make it work from GWT.
What is GXT, is it also this javascript wrapped by a adaptor for GWT?
and
What is SmartGWT is it also javascript wrapped by a adaptor for GWT?
Personally I think that wrapping a bunch of hand written javascript
code in the GWT api doesn't make a lot of sense, mostly due to the way
it behaves when you work with it.
For instance when debugging in Eclipse javascript will throw
exceptions that don't get caught by the GWT adaptors, and your
exceptions will bounce directly into the Browser stack, causing you
hours of frustration.
Cheers,
Scott
confusion (as I and several others I have talked to are confused about
this);
GXT (Ext-GWT) does NOT use the GPL (License) it uses its own license
http://extjs.com/store/gxt/
And it Costs money
GWT-EXT does use GPL
http://code.google.com/p/gwt-ext/
And its free for commercial use like (svn, linux, gwt exc)
but if you modify it you must post your changes otherwise you will
get
in trouble with the free software foundation (like cisco did)
And now for a quesiton.
I know from using Gwt-Ext for a few months that a lot of the code is
acutally written in javascript (EXT, and some Flash for its Charts)
and GWT-EXT is a GWT adapter to make it work from GWT.
What is GXT, is it also this javascript wrapped by a adaptor for GWT?
and
What is SmartGWT is it also javascript wrapped by a adaptor for GWT?
Personally I think that wrapping a bunch of hand written javascript
code in the GWT api doesn't make a lot of sense, mostly due to the way
it behaves when you work with it.
For instance when debugging in Eclipse javascript will throw
exceptions that don't get caught by the GWT adaptors, and your
exceptions will bounce directly into the Browser stack, causing you
hours of frustration.
Cheers,
Scott
Dean S. Jones
Jun 6, 2009, 12:18:34 AM6/6/09
to Google Web Toolkit
Many of these issues are WHY we just got done ripping out all EXT-GWT
code out of a large financial app.
1) License issues
2) GWT compatibility ( Widget intermixing, events, exceptions )
3) Look&Feel didn't ( and couldn't be made to ) conform to corporate
branding
4) generated javascript size
5) reduce external dependencies
6) rendering speed, especially tables.
Financial apps are mostly "Table Driven", so I wrote my own friggin
Table Widget, an optimized it for our use cases. I can now say
the app totally SCREAMS. I have done a few GWT apps for banks, etc,
and I can truly say this is one of the fastest I have ever seen.
ALL the fancy widget packages were orders of magnitude slower on
rendering our data. My table does sorting, paging, selection, and
export to Excel is built in. Cells can have custom properties
( alignment, class ) and even override the renderer so a cell can
contain
a widget. I wrote it, so I understand every line, we own the source,
and can extend it... filtering is next on my list. Screens that used
to
take 7-8 seconds to render now take < 1 second, and I still have a few
tricks up my sleeve....
for instance, ( tho this is not working in IE ), this can render a
300x20 grid, with styling and alignment, in 10ms:
http://deansjones.appspot.com/
and it is a proper sub-class of Grid. Try that on any of these
toolkits ;-)
code out of a large financial app.
1) License issues
2) GWT compatibility ( Widget intermixing, events, exceptions )
3) Look&Feel didn't ( and couldn't be made to ) conform to corporate
branding
4) generated javascript size
5) reduce external dependencies
6) rendering speed, especially tables.
Financial apps are mostly "Table Driven", so I wrote my own friggin
Table Widget, an optimized it for our use cases. I can now say
the app totally SCREAMS. I have done a few GWT apps for banks, etc,
and I can truly say this is one of the fastest I have ever seen.
ALL the fancy widget packages were orders of magnitude slower on
rendering our data. My table does sorting, paging, selection, and
export to Excel is built in. Cells can have custom properties
( alignment, class ) and even override the renderer so a cell can
contain
a widget. I wrote it, so I understand every line, we own the source,
and can extend it... filtering is next on my list. Screens that used
to
take 7-8 seconds to render now take < 1 second, and I still have a few
tricks up my sleeve....
for instance, ( tho this is not working in IE ), this can render a
300x20 grid, with styling and alignment, in 10ms:
http://deansjones.appspot.com/
and it is a proper sub-class of Grid. Try that on any of these
toolkits ;-)
Reply all
Reply to author
Forward
0 new messages