Eelco, I will take a look at it, but I'm not big on Groovy or Grails. I decided to write the Wails framework as an exercise in learning Wicket and if it turned out to be something folks might like, then they could feel free to do so. I was somewhat active in the Tapestry (4.x versions) community for a while and Wicket has interested me for quite some time.
James On 1/21/08, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > On Jan 21, 2008 2:34 PM, James Carman <[EMAIL PROTECTED]> wrote: > > Well, custom editor components based on object type sounds in scope for > what > > I have in mind. And, yes, I'm planning on implementing something > similar to > > Trails using Wicket (and I was planning on calling it "wails"). > > I'm not sure how well it works, but before anyone jumps into a code > rage, it might be a good idea to check out Grail's Wicket support: > http://grails.codehaus.org/Wicket+Plugin. Even if it is not perfect > yet (it might be, I don't know), it might be a more efficient use of > your time to improve the plugin rather than starting from scratch. > Unless you don't like Grails of course. > > Cheers, > > Eelco > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
