HI, On Mar 31, 10:15 am, Blessed Geek <blessedg...@gmail.com> wrote: > [...] > Therefore, listing vaadin directory elements as generally useable GWT > widgets would be misleading because to use vaadin widgets, you would > have to use them in a vaadin application
As I stated previously, the client side of the component (which is the GWT part), is for many add-ons specifically made to be usable in "plain GWT" without Vaadin (and even if it's not, it's still GWT and can be usable, although it depends on the component how hard this is). No one is trying to 'list' all the stuff in directory as general GWT components, though. On the other hand, with only a few exceptions so far, the _core_ components of Vaadin are not of any use in a "plain GWT" project. Perhaps this is what you were thinking about? (especially considering the Directory was opened only yesterday) > [...] > It is difficult to use vaadin to > construct a mashed application set. It is difficult to use vaadin to > construct a site mashed from facebook, twitter, youtube, yahoo > elements as well as under GAE constraints. I don't actually find these particularly difficult, and the Directory will make this sort of thing even easier (ready-made components for specific tasks), but you should certainly make that call yourself - whether or not tool X or tool Y is better suited for you and your task at hand. I would use Vaadin for some project, for others plain GWT would be my choice, and for yet other tasks, I might choose jQuery. This recent "designbygravity" blog post presents some views on where Vaadin excels, it might shed some light on what Vaadin is all about: http://designbygravity.wordpress.com/2010/03/21/for-the-love-of-vaadin-rias-done-right/ I'll also point out something that is quite often misunderstood: Vaadin is not competing with GWT, and is not "built on top of" - instead Vaadin is using GWT, embracing it, and loving it. Vaadin has a different target, providing a server-driven programming model with a tight client/server integration. Those who have not done so already, might want to try both (actually, don't limit yourself to these two), so that you know which tool to apply to which problem. Best Regards, Marc -- 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-tool...@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.
