I just gave up on gwt-ext and switched to gxt. I was tweaking gwt- ext's showcase example, the one with form-grid binding, and I want to add an update button to update the changes made in the form back into the grid. I followed the api doc and searched through their forum, but it just didn't work; to make it worse, there is no way for me to debug this, because in gwt-ext, almost everything is just a Java class wrapping a JavaScript object! It's probably the most painful thing for the Java programmers that they can't debug a program. As for actually using the APIs, gwt-ext and gxt are pretty much the same, both follow ExtJS's API, so it doesn't take much time to switch from one to the other.
License: although gwt-ext is open source, you still need to pay for the gwt-plus package, which is necessary if your client communicates with the server through GWT RPC and costs $199, not much a difference from a gxt single developer license. On Sep 2, 8:06 am, MN <[EMAIL PROTECTED]> wrote: > GXTand GWT-EXT looks very similar.gxtis in native gwt and gwt-ext > is a js wrapper for extjs. > > but what is better? > > can you please write your experiences and some main differences with > this 2 libraries? (more on the programming focus than on licence > issues) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
