it was non-existent than it was to
say that it's poor.
I looked at the recent additions to the Wiki that you pointed me to,
and I still maintain the accuracy of my characterization but...
1) We ARE using Ext-GWT and we are glad we are using it.
Documentation is a serious complaint but we're happy
On 31 jan, 05:42, DaBlick dabl...@gmail.com wrote:
We used GWT-Ext and tossed it in favor of Ext-GWT (often referred to
as GXT).
I've said this before in this forum so I'll just be brief here as you
can search the forum for more details.
- It's been said MANY times so you know it's true
-existent.
The wiki is in work in progress
:http://extjs.com/learn/Learn_About_the_Ext_GWT_Library
and there is also a small help centerhttp://extjs.com/helpcenter/index.jsp
On 31 jan, 05:42, DaBlick dabl...@gmail.com wrote:
We used GWT-Ext and tossed it in favor of Ext-GWT (often referred
and in the very first phase we know that
we need a sortable grid that could be very large, so what must we do?
Must we implement a data model and a paging table or a big grid with
caching or must we use one of Ext-GWT, IT Mill, or SmartGWT? Should I
reinvent the wheel when there are three different
with
caching or must we use one of Ext-GWT, IT Mill, or SmartGWT? Should I
reinvent the wheel when there are three different toolkits with the
widgets that I need?
On Feb 4, 9:57 am, Miles T. dupont.nico...@gmail.com wrote:
Just a word about documentation. It is true that the documentation is
far
first phase we know that
we need a sortable grid that could be very large, so what must we do?
Must we implement a data model and a paging table or a big grid with
caching or must we use one of Ext-GWT, IT Mill, or SmartGWT? Should I
reinvent the wheel when there are three different
and in the very first phase we know that
we need a sortable grid that could be very large, so what must we do?
Must we implement a data model and a paging table or a big grid with
caching or must we use one of Ext-GWT, IT Mill, or SmartGWT? Should I
reinvent the wheel when there are three different
must we do?
Must we implement a data model and a paging table or a big grid with
caching or must we use one of Ext-GWT, IT Mill, or SmartGWT? Should I
reinvent the wheel when there are three different toolkits with the
widgets that I need?
On Feb 4, 9:57 am, Miles T. dupont.nico
We used GWT-Ext and tossed it in favor of Ext-GWT (often referred to
as GXT).
I've said this before in this forum so I'll just be brief here as you
can search the forum for more details.
- It's been said MANY times so you know it's true: It wouldn't be
accurate to say the documentation is poor
Not to resurrect the thread, but I feel I need to add some input to
this, as I've been using Gwt-Ext for over a year now.
I've been using it in a big and complex application, and the results
have been great.
Now, about some points people have raised:
-Slowness: if you design your application
I understand, my company also didn't want to work with GPL (although I
wanted to) :-p
So they purchased the ~300$ commercial license for me.
On 1 déc, 20:57, TedM [EMAIL PROTECTED] wrote:
Yeah but EXT-GWT is a no go for my company because of the license
On Dec 1, 11:10 am, Miles T. [EMAIL
That's fine, but you also need to consider future maintenance of your
application. If your application is going to have any substantial life
time and going to have to be extended and maintained, you're going to
have a pretty hard time with gwt ext or ext gwt. However, I know the
mentality
On 1 déc, 14:41, Arthur Kalmenson [EMAIL PROTECTED] wrote:
quick, get it out the door, I don't care that there
aren't any test cases
Actually, if you look into their SVN repository, you'll see that there
are (only) a few test cases in GWT-Ext. In fact, GWT-Ext is wrapping
ExtJS and only
Yeah but EXT-GWT is a no go for my company because of the license
On Dec 1, 11:10 am, Miles T. [EMAIL PROTECTED] wrote:
On 1 déc, 14:41, Arthur Kalmenson [EMAIL PROTECTED] wrote:
quick, get it out the door, I don't care that there
aren't any test cases
Actually, if you look
robust and structured code with Ext GWT.
Actually it's the complete lack of flexibility. You have to work with
Ext GWT's constraints, and work around it's buggy code and crappy
event model.
Well, actually I don't think price is a problem. Both products (GWT
Designer and Ext GWT) are cheaper than
as
a snail but a nice shiny turd of a web application, you use Ext GWT.
So let me see if I understod you correctly; you don't like Ext GWT?
Seriously,
not liking stuff is fine. It's more than fine as far as I am concerned. I
wish you
all the best in your future endeavours and sometime down the line when
to develop a sortable table.
Also I've studied the incubator widgets and found them also do be
lacking to GWT-EXT and EXT-GWT.
I've recently requested a sponsor in the incubator project to see if I
can help GWT move toward a richer widget set goal. I hope I'll be
able to help.
On Nov 27
On 22 nov, 16:29, Arthur Kalmenson [EMAIL PROTECTED] wrote:
I disagree with Nicolas. We experimented with gwt-ext on one of our
projects and had to backtrack because it was so slow, had far too many
bugs, and was just a pain to work with. It even prevented you from
using hosted mode because
I disagree with Nicolas. We experimented with gwt-ext on one of our
projects and had to backtrack because it was so slow, had far too many
bugs, and was just a pain to work with. It even prevented you from
using hosted mode because it was so slow!!
If you watch this mailing list at all, you'll
want a fully customized design, maybe vanilla GWT
is better.
I have tested both libraries and choose to use Ext GWT. I use it since
April and it makes me saving a lot of time. Here is the result of my
comparison :
Ext GWT (the ExtJS GWT library) :
++ this is a fully native GWT library
This is a common theme, and as I said above, I highly recommend
keeping far away from ext gwt or gwt ext. You can get the same
shininess with some nice CSS.
--
Arthur Kalmenson
On Wed, Nov 5, 2008 at 3:08 AM, zebulon303 [EMAIL PROTECTED] wrote:
I am trying to use ext-gwt for a few days
I am trying to use ext-gwt for a few days, and I get crazy because of
the really poor documentation available, you only have the code to
understand what you are doing, and not enough general guidelines. I
don't know how it is for GWT ext, but I will definitely have a look.
I am really new
I've used gwt-ext for about one month and used that for a quite complex real
world project. I've also tried to use ext-gwt.(It seems that ext-gwt support
ext2.2 but gwt-ext suport 2.0.2 and lower version).
From my current understanding, gwt-ext is very stable and has much more
features that ext
On 29 Okt., 03:46, rlaferla [EMAIL PROTECTED] wrote:
On Oct 28, 3:25 am, alex.d [EMAIL PROTECTED] wrote:
Ext GWT definitely. It's nativa Java-GWT code vs. Javascript wrapper.
Even though you have to pay for it it's worth it.
Sounds good but what are some of the problems that one may
This is a good advice when you have much time and the expertise to
develop nice looking widgets.
But in reality this is not the case.
From my point of view a small team is not able to develop something
which is as good as ExtGwt (aka GXT).
(E.g. a powerful grid component)
We took GXT to
I would agree with Arthur Kalmenson .
And that is the reason why we used vanilla gwt over ext.
you will miss that blazing performance in ext libs. Do not get fooled
with attractive showcase.
With that said, from look and feel + user experience perspective, ext
is probably the best and complete
Folks, correction to my first post. The original contributor of gwt-
ext is probably still part of the project, though not as active.
http://gwt-ext.com/forum/viewtopic.php?f=12p=10318sid=c4b4b0a204e3891ad392622656a65684#p10318
Rakesh Wagh
On Oct 27, 2:17 pm, rakesh wagh [EMAIL PROTECTED] wrote
Ext GWT definitely. It's nativa Java-GWT code vs. Javascript wrapper.
Even though you have to pay for it it's worth it.
On 28 Okt., 03:10, hezjing [EMAIL PROTECTED] wrote:
Hi
Yes, I agree with omsrobert that the license is one of the deciding factors.
However, the GWT-Ext LGPL license (http
I would say go with neither. If you look at the group, you'll find
that there are endless problems with these libraries. They're shoddy,
poorly put together, slow and nowhere near the level of quality that
you come to expect from GWT. The library is made by Javascript
developers who have little
On Oct 28, 3:25 am, alex.d [EMAIL PROTECTED] wrote:
Ext GWT definitely. It's nativa Java-GWT code vs. Javascript wrapper.
Even though you have to pay for it it's worth it.
Sounds good but what are some of the problems that one may encounter
with GWT-Ext? Also, GWT-Ext has GWT-Plus to connect
Not sure if there is a thread ever discussed on this. If so, I'd
appreciate help in locating it. Tried a search and it decided to
exclude the gwt part and search only for ext which isn't much help.
Anyway, for all the people using either of these, I figure it might be
good to get some feedback on
I have used GWT-ext but not ext-GWT.
GWT-ext was a hot favorite before ext-js went commercial and before
the ext team themselves launched ext-GWT. Now that gwt support is
provided by the ext team themselves, I think it will make more sense
to use ext-gwt. Moreover Sanjeev Jeevan the original
I think licensing is one of the deciding factors:
GWT-Ext (http://gwt-ext.com/) is free, open source. There is a
companion, commercial product called GWT Plus (same author) that
facilitates binding data objects to the widget record store.
Ext GWT (http://extjs.com/products/gxt/) is now
Hi
Yes, I agree with omsrobert that the license is one of the deciding factors.
However, the GWT-Ext LGPL license (http://gwt-ext.com/license/) applies only
to use of GWT-Ext with Ext versions 2.0.2 or lower.
I'm not sure, but will Ext 2.0.2 ends of support?
How does Ext 2.0.2 affects us? Should
34 matches
Mail list logo
