On Thu, Feb 4, 2010 at 6:25 PM, mariyan nenchev <[email protected]> wrote: > Yes it has very fancy widgets but the integration with the server side is > killing unless you decide to purchase pro/ee, which is why it is done that > way, to show the devs how rich library it is and when they began to use it > they understand that they must buy pro/ee else they will code hundreds lines > of code to do something simple. No body told me how many steps are needed to > list some data in table if your backend is EJBs and you are using GWT-RPC?
Dude, but after all, SmartGWT so far is the best among others, despite its somewhat tragifunky API. Yes, for us, who are doing Swing as well, SmartGWT is quite painful, although it intended to be like Swing for Web. Yes, method names are wicked, composing widgets is weird etc. And there is also a number of reasons why they're done this way — hence let's don't regard them as fools — the guys, actually doing awesome job. Because what else on the market is available right now that could solve a huge number of a problems that we facing every day, making enterprise software for the Web? Personally I don't like concentrating on JavaScript horror and prefer Java Swing over JNLP in most cases. In Enterprise controlled internal network we never allow web stuff — there is only Swing and it works rock stable. But it requires very clean and highly controlled networks. Since outside the company, in the wild world, there are anything you might expect, so browsers + JavaScript + HTML is the only way. However, it is horrific way to make UIs, has no real standards, is very unpredictable, slippery and unreliable. So let's better think how we can help them instead, because everyone can bashing things: that's no brainer... -- bm -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. 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.
