> 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 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 -~----------~----~----~----~------~----~------~--~---
