>> I semi-evaluated Vaadin some while back. It is promising, and has a similar >> philosophy to weblocks -- everything is done at the backend using seamless >> ajax, so malicious manipulation at the front end is less effective. In terms >> of baked in widgets etc. Vaadin is quite complete, far more so than weblocks >> is. It wasn't really an option because we didn't want to work in java. >> Perhaps you could evaluate how easy it would be to extend with custom >> widgets (and hey, while I'm at it how about a tutorial? ;-) > > Tomek Lipski recently posted a simple integration tutorial here: > http://dev.vaadin.com/wiki/Articles/ClojureScripting > So based on that I put it together and you just call the Vaadin Java > classes from Clojure and that's basically it, I didn't do much more. > I don't know how to extend it with custom widgets, that's probably in > the Vaadin book.
Hi, >From what I've seen, custom widgets have to be developed in Google Web Toolkit, so basically in Java or even JavaScript. But I believe, that the term 'widget' is misunderstood here - contrary to Weblocks, in Vaadin it is more something like a color picker than customer data form. In most cases, basic/provided Vaadin widgets should suffice. Best regards, Tomek Lipski -- You received this message because you are subscribed to the Google Groups "weblocks" 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/weblocks?hl=en.
