I like the idea. I have been working on a bean panel where I had some - unimplemented - idea's for detail editing as well. Haven't found the time yet to finish it though.
Code generation is the other way around though. That can be very powerful too, and is usually easier to customize later on. I think the ideal toolkit would be a combination of both: something that generates code for you (in such a way that you can customize extension code, but that you can regenerate whenever you want), but that produces code that is smarter than just static binding everything too. You don't like Ruby? It's on my list to learn. From what I've read, I like it, though when I played around with it a bit, I immediately missed code completion and documentation hoovers etc. I'm an IDE guy that's loves all the little productivity boosters and analyses tools (like java inheritance hierarchy views, call hierarchy views, etc) modern Java IDE can give you. But Ruby is supposed to be very good with text processing, so you/ we might even consider using Ruby for code generation. Otoh, Velocity is easy and good in this too. Eelco On 10/2/05, David Liebeherr <[EMAIL PROTECTED]> wrote: > Hi! > > Today i read a pretty much interesting article about Ruby on Rails (RoR). > First things first. I don't like ruby. > But: The Aproach of Ruby on Rails is very impressing and provides a > effective way to write standard Web-Apps. > So i like the way how wicket works much. And now i am thinking about to > adopt some ideas of Ruby on Rails to wicket. > The most interesting and time saving aspect of RoR is that it has mayn > scripts to automaticly generate Formulars and Lists so that you can deal > with Datas which mostly comes from a Database. > I think a similary tool could be made for Wicket. > The features i think of are somehting likt this: > -Gernation of Formulars and Lists from the Strucure of a certain > Database-Table (Or JavaBean Class). > Which includes the generation of: Wicket-Class, Wicket-HTML-File and > that all already ready with all necessary connections and handling to > the database or the JavaBean object. > > This generated "Prototype" can then be customized to the needs of the > specific project. > But mostly this is not even neccessary if the generator generates stuff > that fits on most common use casses (Of course with pretty basic User > Interface :-)). > > So i think all this can be pretty easy implemented (It's a lot of work, > but the principle is pretty clear and easy i think). > > My question now to you guys is: > 1. Is already someone writing such a Generator? > 2. What do you guys think about this idea? (Please stay on the way of > what the tool should be able to do. Please no discussion about how to > implement it bc that comes later!) > > Thanks, > Dave > > -- > Rent-a-Developer > David Liebeherr > Tel.: 0721 3504990 > mail: [EMAIL PROTECTED] > > SUN Certified Java Associate (SCJA) > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
