I don't know Vaadin, but I would argue that this issue concerns the official GWT development stack - which does indeed rely on the development mode and thus, a browser plugin. I am curious though, how can you hook into components and do your own (the nice thing about GWT is that one can use OO for reusability and extensionability), without having to compile these?
> This is not the only way. Vaadin uses pre-compiled GWT widgets and that > sooo long compilation never occurs, or occurs only once in a while when > using third parties' widgets. For the rest the development is super-fast > in 100% Java, no plugins, and, if you want, pretty agile. I've been > developing with GWT through Vaadin for 1.5 years now :-) Seeing that > Vaadin is sitting at the table of the new GWT stewards makes me feel > pretty safe. > -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/6Jb5luzA_NkJ. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
