> This is one reason that ruby on rails has taken off--the combination of > Instant Rails and Active Record makes it the easiest framework to get a > fully database-enabled application up and running. > > Wicket has done a great job of making it easy to get up and running, but > there is always more to be done.
Definitively. The next steps in making the framework better imho is to focus more on stacks. It should be optional, and focussed on getting database apps up and running real quick. Databinder goes in this direction, and also projects like salve (Igor's baby) can mean a lot in this context. And what Matej has been working on, a cluster solution that is optimized for Wicket is another stack improvement (and the fact that Terracotta has specific Wicket support yet another). It wouldn't hurt of more people (other than the core team) would pick this up though. We are busy enough as it is with writing the book, supporting this list and fixing bugs etc. I'm definitively interested to play around with ideas myself once we get the book over with. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]