Re: GWT-ext or ext-GWT?
On Feb 4, 3:57 am, Miles T. dupont.nico...@gmail.com wrote: Just a word about documentation. It is true that the documentation is far from complete but it is not true that it is non-existent. Well, it's not true that I said it was non-existent either. :-) I said it was more accurate to say 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 otherwise. It's just our biggest beef and people considering using GXT need to be aware of it, which was my point. 2) ExtJS is VERY responsive to bugs and questions, and the forums are very helpful. Not a substitute for documentation, but they dull the pain considerably. 3) I'm ecstatically happy to see that a book is coming out. I'm going to preorder copies for all my colleagues. This could eliminate the entire complaint if the book is decent. 4) I'm quite happy that work is being done on the Wiki. But the fact remains, that not much is there yet. As far as I can tell, the GXT MVC architecture (which IMHO is pretty darn good) is largely undocumented. One sentence descriptions often in the Javadocs even. 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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
Just a word about documentation. It is true that the documentation is far from complete but it is not true that it is non-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 center http://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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
And there is also a book ((http://www.apress.com/book/view/ 9781430219408) which should be available soon. 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 from complete but it is not true that it is non-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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
Hi getaceres, If you're looking for a sortable grid, check out the ScrollTable in the gwt-incubator: http://code.google.com/p/google-web-toolkit-incubator/. If you're loading a lot of data into the ScrollTable, you might want to use the BulkTableRenderer: http://code.google.com/docreader/#p=google-web-toolkit-incubators=google-web-toolkit-incubatort=BulkTableRenderers -- Arthur Kalmenson On Wed, Feb 4, 2009 at 4:51 AM, getaceres getace...@gmail.com wrote: It's not only about the look, it's about the lack of a decent default widget set in GWT. We are starting a project now 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 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 from complete but it is not true that it is non-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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
It's not only about the look, it's about the lack of a decent default widget set in GWT. We are starting a project now 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 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 from complete but it is not true that it is non-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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
Thanks, I didn't know about the Incubator widgets. It seems very complete and interesting but I have a question about it: What's the state of stability and feature completeness of the widgets in Incubator? I mean, are they ready to be used in real applications? On Feb 4, 3:58 pm, Arthur Kalmenson arthur.k...@gmail.com wrote: Hi getaceres, If you're looking for a sortable grid, check out the ScrollTable in the gwt-incubator:http://code.google.com/p/google-web-toolkit-incubator/. If you're loading a lot of data into the ScrollTable, you might want to use the BulkTableRenderer:http://code.google.com/docreader/#p=google-web-toolkit-incubators=go... -- Arthur Kalmenson On Wed, Feb 4, 2009 at 4:51 AM, getaceres getace...@gmail.com wrote: It's not only about the look, it's about the lack of a decent default widget set in GWT. We are starting a project now 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 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 from complete but it is not true that it is non-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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
The incubator is much less stable than the main GWT widget library. Widgets in the incubator are still evolving and the API is subject to change. The incubator is not recommended for production use. Widgets that graduate to the main library are considered production ready (see DatePicker for an example of a graduate in the upcoming GWT 1.6). I've found significant time savings in using widgets from the incubator in my own work. I've also had to refactor when something in the incubator changes and I want to upgrade. Whenever possible I try to wrap an incubator widget in a widget of my own to reduce direct coupling of unstable incubator API to my application code. There is the intention to implement some means of informing developers of the relative stability of incubator widgets, but this is still a work in progress. On Wed, Feb 4, 2009 at 12:24 PM, getaceres getace...@gmail.com wrote: Thanks, I didn't know about the Incubator widgets. It seems very complete and interesting but I have a question about it: What's the state of stability and feature completeness of the widgets in Incubator? I mean, are they ready to be used in real applications? On Feb 4, 3:58 pm, Arthur Kalmenson arthur.k...@gmail.com wrote: Hi getaceres, If you're looking for a sortable grid, check out the ScrollTable in the gwt-incubator:http://code.google.com/p/google-web-toolkit-incubator/. If you're loading a lot of data into the ScrollTable, you might want to use the BulkTableRenderer:http://code.google.com/docreader/#p=google-web-toolkit-incubators=go... -- Arthur Kalmenson On Wed, Feb 4, 2009 at 4:51 AM, getaceres getace...@gmail.com wrote: It's not only about the look, it's about the lack of a decent default widget set in GWT. We are starting a project now 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 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 from complete but it is not true that it is non-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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
I think it's also important to point out that while the GWT team says the incubator should not be used in production, it's still far more stable, better test and put together then most of the third party libraries available for GWT. You also have the added benefit that some of them might make it to the core. We use ScrollTable in production and are looking into using CssResource in the future. -- Arthur Kalmenson On Wed, Feb 4, 2009 at 12:37 PM, Isaac Truett itru...@gmail.com wrote: The incubator is much less stable than the main GWT widget library. Widgets in the incubator are still evolving and the API is subject to change. The incubator is not recommended for production use. Widgets that graduate to the main library are considered production ready (see DatePicker for an example of a graduate in the upcoming GWT 1.6). I've found significant time savings in using widgets from the incubator in my own work. I've also had to refactor when something in the incubator changes and I want to upgrade. Whenever possible I try to wrap an incubator widget in a widget of my own to reduce direct coupling of unstable incubator API to my application code. There is the intention to implement some means of informing developers of the relative stability of incubator widgets, but this is still a work in progress. On Wed, Feb 4, 2009 at 12:24 PM, getaceres getace...@gmail.com wrote: Thanks, I didn't know about the Incubator widgets. It seems very complete and interesting but I have a question about it: What's the state of stability and feature completeness of the widgets in Incubator? I mean, are they ready to be used in real applications? On Feb 4, 3:58 pm, Arthur Kalmenson arthur.k...@gmail.com wrote: Hi getaceres, If you're looking for a sortable grid, check out the ScrollTable in the gwt-incubator:http://code.google.com/p/google-web-toolkit-incubator/. If you're loading a lot of data into the ScrollTable, you might want to use the BulkTableRenderer:http://code.google.com/docreader/#p=google-web-toolkit-incubators=go... -- Arthur Kalmenson On Wed, Feb 4, 2009 at 4:51 AM, getaceres getace...@gmail.com wrote: It's not only about the look, it's about the lack of a decent default widget set in GWT. We are starting a project now 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 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 from complete but it is not true that it is non-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 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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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. It'd be more accurate to say that the documentation is NON-EXISTENT and this is a SERIOUS SERIOUS issue you must consider before choosing it. You are, apparently, expected to learn the library by reverse-engineering the examples. This means your project will have a potentially steep ramp- up time. - It's easy to find bugs in Ext-GWT because it's basically been a one- man project for most of its life. However... - Reported bugs tend to get fixed VERY quickly and if you are licensed, you can pick up the fix from the SVN as soon as they are fixed. - Ext-GWT has what I consider to be a rather nice MVC architecture built into it. It really goes well beyond, say, Swing's MVC because it not only de-couples Ms, Vcs and Cs, but decouples data-models, data loaders, etc. The MVC architecture has some problems with its generic implementation, but it's pretty good overall. - We think the components look nice, but then... we pretty much have customized everything. Our app is highly stylized. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 properly and use the right widgets for each job, you'll have no problems. Our application runs like a charm, and it deals with BIG datasets. But yes, you do need to code thinking about performance, as is the case with ANY other application if you deal with a lot of data. -Bugs: I've come across a couple, but nothing serious, and you do have the source, so you can FIX them (I've done it when needed). The detractors please tell me of a piece of software that doesn't have a bug... Our app has always been completely stable, no problems there, so I don't know what some people here are talking about... -Maintainability/extensibility: you have the source, so you can adapt and extend whatever widget you want (done that too). If you think you can develop the same kind of functionality with just GWT / CSS to match one of these libraries in a decent amount of time, you are just insane, or just are so inexperienced you cannot understand how much work you have ahead of you. It saved us a huge (I mean HUGE) amount of time, and I recommend it. --~--~-~--~~~---~--~~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 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 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 contains a thin GWT layer, maybe it explains why there are a few test cases. However, I agree that a good code coverage is a sign of quality. On the other side, there are A LOT of test cases in Ext GWT. -- Arthur Kalmenson On Thu, Nov 27, 2008 at 9:57 AM, Niklas Derouche [EMAIL PROTECTED] wrote: On Thu, Nov 27, 2008 at 2:52 PM, Arthur Kalmenson [EMAIL PROTECTED] wrote: I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow 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 you have spent more than a year or two in the workplace post your degree you may find that you start making choices based on pragmatic weighing of pros and cons and where your design ideals may take the backseat to cost and time-to-market factors. Your mileage will vary. n. -- I've had a wonderful time but this wasn't it. Groucho Marx --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 of quick, get it out the door, I don't care that there aren't any test cases is still very prevalent. If that's the type of work environment one is in, they have little choice. -- Arthur Kalmenson On Thu, Nov 27, 2008 at 9:57 AM, Niklas Derouche [EMAIL PROTECTED] wrote: On Thu, Nov 27, 2008 at 2:52 PM, Arthur Kalmenson [EMAIL PROTECTED] wrote: I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow 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 you have spent more than a year or two in the workplace post your degree you may find that you start making choices based on pragmatic weighing of pros and cons and where your design ideals may take the backseat to cost and time-to-market factors. Your mileage will vary. n. -- I've had a wonderful time but this wasn't it. Groucho Marx --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 contains a thin GWT layer, maybe it explains why there are a few test cases. However, I agree that a good code coverage is a sign of quality. On the other side, there are A LOT of test cases in Ext GWT. -- Arthur Kalmenson On Thu, Nov 27, 2008 at 9:57 AM, Niklas Derouche [EMAIL PROTECTED] wrote: On Thu, Nov 27, 2008 at 2:52 PM, Arthur Kalmenson [EMAIL PROTECTED] wrote: I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow 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 you have spent more than a year or two in the workplace post your degree you may find that you start making choices based on pragmatic weighing of pros and cons and where your design ideals may take the backseat to cost and time-to-market factors. Your mileage will vary. n. -- I've had a wonderful time but this wasn't it. Groucho Marx --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 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 contains a thin GWT layer, maybe it explains why there are a few test cases. However, I agree that a good code coverage is a sign of quality. On the other side, there are A LOT of test cases in Ext GWT. -- Arthur Kalmenson On Thu, Nov 27, 2008 at 9:57 AM, Niklas Derouche [EMAIL PROTECTED] wrote: On Thu, Nov 27, 2008 at 2:52 PM, Arthur Kalmenson [EMAIL PROTECTED] wrote: I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow 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 you have spent more than a year or two in the workplace post your degree you may find that you start making choices based on pragmatic weighing of pros and cons and where your design ideals may take the backseat to cost and time-to-market factors. Your mileage will vary. n. -- I've had a wonderful time but this wasn't it. Groucho Marx --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
In my own experience, I see that these projects are good and not only shiny :-p I agree that they are more complex to use than vanilla GWT. But actually, I think this is the drawback of a high-level, Swing/ SWT-like API. I think you have more flexibility with GWT but it is easier to write 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 weekly wage for a developer (and even cheaper than a DAILY wage for some engineers). On the other hand, spending days to write CSS themes, integrating incubator or custom widgets are not really cheap. What about if you spend WEEKS trying to figure out why Ext GWT is formatting your widgets in this way, and not another. Or trying to figure out why it's so deathly slow that hosted mode barely works. I understand that in smaller shops the programmer ends up doing the CSS (I do it myself), but GWT already comes with themes in 1.5, what's wrong with those? Creating custom widgets isn't really very hard, and at least you can be sure that what you write will be tested (not sure about Ext GWT). Furthermore, a lot of the incubator stuff is pretty high quality and is written by the GWT staff, so you know it's tested well and of a much higher quality standard then Ext GWT will ever achieve. I think it depends on your needs. If you have exotic graphical needs or if you want a hardly customized design or if you don't want to hear about GPL or LGPL product, vanilla GWT is sufficient for you. If not, you should hardly think about the choice. I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow as a snail but a nice shiny turd of a web application, you use Ext GWT. -- Arthur Kalmenson On Tue, Nov 25, 2008 at 11:50 AM, Miles T. [EMAIL PROTECTED] wrote: 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 it was so slow!! Try last versions. Both libraries (Ext GWT and GWT-Ext) evolve very quickly. If you watch this mailing list at all, you'll find that most of the problems that people are having are related to some Ext product. You get forced into their retarded even model, they're overly complex widgets and sample code that doesn't work as shown in the showcase. Just because a turd is made shiny, does not mean it's good. In my own experience, I see that these projects are good and not only shiny :-p I agree that they are more complex to use than vanilla GWT. But actually, I think this is the drawback of a high-level, Swing/ SWT-like API. I think you have more flexibility with GWT but it is easier to write robust and structured code with Ext GWT. You can use the incubator and regular GWT to get anything you need done. GWT 1.5 already comes with default CSS themes, and that should be enough to get you off the ground. If you want better themes, get a graphics designer. They're very cheap and will probably run you less then buying a couple ExtGWT licenses. Well, actually I don't think price is a problem. Both products (GWT Designer and Ext GWT) are cheaper than weekly wage for a developer (and even cheaper than a DAILY wage for some engineers). On the other hand, spending days to write CSS themes, integrating incubator or custom widgets are not really cheap. I think it depends on your needs. If you have exotic graphical needs or if you want a hardly customized design or if you don't want to hear about GPL or LGPL product, vanilla GWT is sufficient for you. If not, you should hardly think about the choice. IMHO -- Arthur Kalmenson On Thu, Nov 20, 2008 at 8:30 AM, Nicolas [EMAIL PROTECTED] wrote: Hi all, I don't agree with Arthur. You save a lot of time using one of these libraries. In both cases you don't have to care about CSS and you have much more widgets than vanilla GWT. On the other side, both libraries are not as mature as GWT, so you will find isolated issues. Obviously, if you 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 (it is not wrapping JS code and therefore fully benefits from GWT compiler optimizations and debugging features) + the library is supported by ExtJS company, which is already a popular
Re: GWT-ext or ext-GWT?
On Thu, Nov 27, 2008 at 2:52 PM, Arthur Kalmenson [EMAIL PROTECTED]wrote: I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow 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 you have spent more than a year or two in the workplace post your degree you may find that you start making choices based on pragmatic weighing of pros and cons and where your design ideals may take the backseat to cost and time-to-market factors. Your mileage will vary. n. -- I've had a wonderful time but this wasn't it. Groucho Marx --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
I agree with you Arthur on the point that I wish we could use 100% GWT but the GWT Widget set is lacking in richness. I really wish this will be addresses. Examples Tab panel functionality Sortable Grid/Table Grouping Grid/Table Calendar data fields Popup dialogs with configurable top right buttons I agree all these widgets can be done with some work and using the core GWT code. But what makes me sad is no one has done it and published it. Plus, in my work and I believe most people's work place there is no time to reinvent the wheel. I'm not going to get my supervisor to approve time 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, 8:52 am, Arthur Kalmenson [EMAIL PROTECTED] wrote: In my own experience, I see that these projects are good and not only shiny :-p I agree that they are more complex to use than vanilla GWT. But actually, I think this is the drawback of a high-level, Swing/ SWT-like API. I think you have more flexibility with GWT but it is easier to write 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 weekly wage for a developer (and even cheaper than a DAILY wage for some engineers). On the other hand, spending days to write CSS themes, integrating incubator or custom widgets are not really cheap. What about if you spend WEEKS trying to figure out why Ext GWT is formatting your widgets in this way, and not another. Or trying to figure out why it's so deathly slow that hosted mode barely works. I understand that in smaller shops the programmer ends up doing the CSS (I do it myself), but GWT already comes with themes in 1.5, what's wrong with those? Creating custom widgets isn't really very hard, and at least you can be sure that what you write will be tested (not sure about Ext GWT). Furthermore, a lot of the incubator stuff is pretty high quality and is written by the GWT staff, so you know it's tested well and of a much higher quality standard then Ext GWT will ever achieve. I think it depends on your needs. If you have exotic graphical needs or if you want a hardly customized design or if you don't want to hear about GPL or LGPL product, vanilla GWT is sufficient for you. If not, you should hardly think about the choice. I disagree, you don't need any exotic graphic needs to use GWT. If you want a good, functional and quick web application, you use GWT. If you want a hard to maintain, buggy and poorly (if at all) tested, slow as a snail but a nice shiny turd of a web application, you use Ext GWT. -- Arthur Kalmenson On Tue, Nov 25, 2008 at 11:50 AM, Miles T. [EMAIL PROTECTED] wrote: 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 it was so slow!! Try last versions. Both libraries (Ext GWT and GWT-Ext) evolve very quickly. If you watch this mailing list at all, you'll find that most of the problems that people are having are related to some Ext product. You get forced into their retarded even model, they're overly complex widgets and sample code that doesn't work as shown in the showcase. Just because a turd is made shiny, does not mean it's good. In my own experience, I see that these projects are good and not only shiny :-p I agree that they are more complex to use than vanilla GWT. But actually, I think this is the drawback of a high-level, Swing/ SWT-like API. I think you have more flexibility with GWT but it is easier to write robust and structured code with Ext GWT. You can use the incubator and regular GWT to get anything you need done. GWT 1.5 already comes with default CSS themes, and that should be enough to get you off the ground. If you want better themes, get a graphics designer. They're very cheap and will probably run you less then buying a couple ExtGWT licenses. Well, actually I don't think price is a problem. Both products (GWT Designer and Ext GWT) are cheaper than weekly wage for a developer (and even cheaper than a DAILY wage for some engineers). On the other hand, spending days to write CSS themes, integrating incubator or custom widgets are not really cheap. I think it depends on your needs. If you have exotic graphical needs or if you want a hardly customized design or if you don't want to hear about GPL or LGPL
Re: GWT-ext or ext-GWT?
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 it was so slow!! Try last versions. Both libraries (Ext GWT and GWT-Ext) evolve very quickly. If you watch this mailing list at all, you'll find that most of the problems that people are having are related to some Ext product. You get forced into their retarded even model, they're overly complex widgets and sample code that doesn't work as shown in the showcase. Just because a turd is made shiny, does not mean it's good. In my own experience, I see that these projects are good and not only shiny :-p I agree that they are more complex to use than vanilla GWT. But actually, I think this is the drawback of a high-level, Swing/ SWT-like API. I think you have more flexibility with GWT but it is easier to write robust and structured code with Ext GWT. You can use the incubator and regular GWT to get anything you need done. GWT 1.5 already comes with default CSS themes, and that should be enough to get you off the ground. If you want better themes, get a graphics designer. They're very cheap and will probably run you less then buying a couple ExtGWT licenses. Well, actually I don't think price is a problem. Both products (GWT Designer and Ext GWT) are cheaper than weekly wage for a developer (and even cheaper than a DAILY wage for some engineers). On the other hand, spending days to write CSS themes, integrating incubator or custom widgets are not really cheap. I think it depends on your needs. If you have exotic graphical needs or if you want a hardly customized design or if you don't want to hear about GPL or LGPL product, vanilla GWT is sufficient for you. If not, you should hardly think about the choice. IMHO -- Arthur Kalmenson On Thu, Nov 20, 2008 at 8:30 AM, Nicolas [EMAIL PROTECTED] wrote: Hi all, I don't agree with Arthur. You save a lot of time using one of these libraries. In both cases you don't have to care about CSS and you have much more widgets than vanilla GWT. On the other side, both libraries are not as mature as GWT, so you will find isolated issues. Obviously, if you 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 (it is not wrapping JS code and therefore fully benefits from GWT compiler optimizations and debugging features) + the library is supported by ExtJS company, which is already a popular and recognized javascript framework + MVC layer - less features for now - if you want to distribute your product and don't want to do it under GPL license you will have to buy a commercial license (289$ for one developer) GWT-Ext : + more features (especially experimental Yahoo UI Charts integration) - This is a library wrapping ExtJS (Javascript code). Therefore debugging is limited - no support for ExtJS 2.0.2 - no GWT RPC integration (except if you buy the commercial extension GWT-Ext Plus) Regards Nicolas On 6 nov, 14:41, Arthur Kalmenson [EMAIL PROTECTED] wrote: 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, 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 with GWT in general, maybe that's why I need more documentation. I was trying to figure out how to add a delete button to the EditorGrid, or just access the current selected item of the grid. I find it really difficult to get to this simple information. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 find that most of the problems that people are having are related to some Ext product. You get forced into their retarded even model, they're overly complex widgets and sample code that doesn't work as shown in the showcase. Just because a turd is made shiny, does not mean it's good. You can use the incubator and regular GWT to get anything you need done. GWT 1.5 already comes with default CSS themes, and that should be enough to get you off the ground. If you want better themes, get a graphics designer. They're very cheap and will probably run you less then buying a couple ExtGWT licenses. -- Arthur Kalmenson On Thu, Nov 20, 2008 at 8:30 AM, Nicolas [EMAIL PROTECTED] wrote: Hi all, I don't agree with Arthur. You save a lot of time using one of these libraries. In both cases you don't have to care about CSS and you have much more widgets than vanilla GWT. On the other side, both libraries are not as mature as GWT, so you will find isolated issues. Obviously, if you 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 (it is not wrapping JS code and therefore fully benefits from GWT compiler optimizations and debugging features) + the library is supported by ExtJS company, which is already a popular and recognized javascript framework + MVC layer - less features for now - if you want to distribute your product and don't want to do it under GPL license you will have to buy a commercial license (289$ for one developer) GWT-Ext : + more features (especially experimental Yahoo UI Charts integration) - This is a library wrapping ExtJS (Javascript code). Therefore debugging is limited - no support for ExtJS 2.0.2 - no GWT RPC integration (except if you buy the commercial extension GWT-Ext Plus) Regards Nicolas On 6 nov, 14:41, Arthur Kalmenson [EMAIL PROTECTED] wrote: 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, 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 with GWT in general, maybe that's why I need more documentation. I was trying to figure out how to add a delete button to the EditorGrid, or just access the current selected item of the grid. I find it really difficult to get to this simple information. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
Hi all, I don't agree with Arthur. You save a lot of time using one of these libraries. In both cases you don't have to care about CSS and you have much more widgets than vanilla GWT. On the other side, both libraries are not as mature as GWT, so you will find isolated issues. Obviously, if you 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 (it is not wrapping JS code and therefore fully benefits from GWT compiler optimizations and debugging features) + the library is supported by ExtJS company, which is already a popular and recognized javascript framework + MVC layer - less features for now - if you want to distribute your product and don't want to do it under GPL license you will have to buy a commercial license (289$ for one developer) GWT-Ext : + more features (especially experimental Yahoo UI Charts integration) - This is a library wrapping ExtJS (Javascript code). Therefore debugging is limited - no support for ExtJS 2.0.2 - no GWT RPC integration (except if you buy the commercial extension GWT-Ext Plus) Regards Nicolas On 6 nov, 14:41, Arthur Kalmenson [EMAIL PROTECTED] wrote: 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, 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 with GWT in general, maybe that's why I need more documentation. I was trying to figure out how to add a delete button to the EditorGrid, or just access the current selected item of the grid. I find it really difficult to get to this simple information. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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, 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 with GWT in general, maybe that's why I need more documentation. I was trying to figure out how to add a delete button to the EditorGrid, or just access the current selected item of the grid. I find it really difficult to get to this simple information. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 with GWT in general, maybe that's why I need more documentation. I was trying to figure out how to add a delete button to the EditorGrid, or just access the current selected item of the grid. I find it really difficult to get to this simple information. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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-gwt. Sammi On Wed, Nov 5, 2008 at 12:08 AM, zebulon303 [EMAIL PROTECTED] wrote: 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 with GWT in general, maybe that's why I need more documentation. I was trying to figure out how to add a delete button to the EditorGrid, or just access the current selected item of the grid. I find it really difficult to get to this simple information. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 encounter with GWT-Ext? You never know until you start using it in your particular application. Also, GWT-Ext has GWT-Plus to connect your backend database objects to the GWT-Ext widget's store (e.g. GridPanel). What do you use for Ext GWT? Haven't heared of such binding in Ext-GWT yet. BTW - The names are really confusing. I expect a lawsuit will force a name change at some point. Actually - Ext-GWT was renamed to GXT, but nobody seemes to use it :( --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 develop our app. In general we had no huge problems to solve until now (at least in context with GXT) Regards, Martin On Oct 28, 1:55 pm, Arthur Kalmenson [EMAIL PROTECTED] wrote: 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 to no Java knowledge. If you want a well test, well designed toolkit, stick with vanilla GWT and make widgets yourself. Regards, -- Arthur Kalmenson On Mon, Oct 27, 2008 at 11:50 AM, Suri [EMAIL PROTECTED] wrote: 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 the drawbacks and strengths of each and have something helpful for everyone like me trying to decide which is a good fit. Any ideas? Sorry if I seem abstract, I just thought the more general the better. Thanks Suri --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 library out there. If you are a smart developer you will go with gwt. If you are a dumb manager, u will go with ext Rakesh Wagh On Oct 29, 5:45 pm, sankar.gorthi [EMAIL PROTECTED] wrote: http://gwt-ext.com/forum/viewtopic.php?f=12p=10318sid=c4b4b0a204e38... On Oct 29, 1:55 am, maku [EMAIL PROTECTED] wrote: 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 develop our app. In general we had no huge problems to solve until now (at least in context with GXT) Regards, Martin On Oct 28, 1:55 pm, Arthur Kalmenson [EMAIL PROTECTED] wrote: 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 to no Java knowledge. If you want a well test, well designed toolkit, stick with vanilla GWT and make widgets yourself. Regards, -- Arthur Kalmenson On Mon, Oct 27, 2008 at 11:50 AM, Suri [EMAIL PROTECTED] wrote: 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 the drawbacks and strengths of each and have something helpful for everyone like me trying to decide which is a good fit. Any ideas? Sorry if I seem abstract, I just thought the more general the better. Thanks Suri --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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: 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 creator of gwt- ext is no longer part of that project. I would go with ext-gwt with a little evaluation. Hope they dont have any major hiccups. Rakesh Wagh On Oct 27, 10:50 am, Suri [EMAIL PROTECTED] wrote: 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 the drawbacks and strengths of each and have something helpful for everyone like me trying to decide which is a good fit. Any ideas? Sorry if I seem abstract, I just thought the more general the better. Thanks Suri --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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://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 this be another deciding factor too? On Tue, Oct 28, 2008 at 9:10 AM, omsrobert [EMAIL PROTECTED] wrote: 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 a commercial product with an open source license option. -- Hez --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 to no Java knowledge. If you want a well test, well designed toolkit, stick with vanilla GWT and make widgets yourself. Regards, -- Arthur Kalmenson On Mon, Oct 27, 2008 at 11:50 AM, Suri [EMAIL PROTECTED] wrote: 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 the drawbacks and strengths of each and have something helpful for everyone like me trying to decide which is a good fit. Any ideas? Sorry if I seem abstract, I just thought the more general the better. Thanks Suri --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 your backend database objects to the GWT-Ext widget's store (e.g. GridPanel). What do you use for Ext GWT? BTW - The names are really confusing. I expect a lawsuit will force a name change at some point. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
GWT-ext or ext-GWT?
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 the drawbacks and strengths of each and have something helpful for everyone like me trying to decide which is a good fit. Any ideas? Sorry if I seem abstract, I just thought the more general the better. Thanks Suri --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 creator of gwt- ext is no longer part of that project. I would go with ext-gwt with a little evaluation. Hope they dont have any major hiccups. Rakesh Wagh On Oct 27, 10:50 am, Suri [EMAIL PROTECTED] wrote: 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 the drawbacks and strengths of each and have something helpful for everyone like me trying to decide which is a good fit. Any ideas? Sorry if I seem abstract, I just thought the more general the better. Thanks Suri --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 a commercial product with an open source license option. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: GWT-ext or ext-GWT?
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 this be another deciding factor too? On Tue, Oct 28, 2008 at 9:10 AM, omsrobert [EMAIL PROTECTED] wrote: 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 a commercial product with an open source license option. -- Hez --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
