You could take a look at what is in cvs HEAD now if you are interested.
In the extensions project, there is some stuff in the
wicket.extensions.markup.html.beanedit package.
It is probably a good idea to keep that package in extensions and build
a more sophisticated project on top of that.
Btw, it's not done (though basically usefull), so if any of you play
with it and find stuff, it's probably not build yet or a plain bug.
Please let me know then. I'm just doing too many things at once right
now to really finish it right away :)
Eelco
Stefan Matthias Aust wrote:
Hi Eelco,
So, what do you guys think? What direction should the bean panel
experiment head? Who is interested in cooperating, and where should we
put it (in wicket-stuff, so that it can be a seperate full-fledged
project with more people working on it, or in extensions in case we keep
it really simple)?
I can only give you a very high level answer. The idea of having some
automatic dynamic UI generator for beans was one thing that got me
interested in Wicket. I'd love to see this evolving into something
similar to the scaffolding stuff Rails on Ruby got somewhat famous for
- just enough to setup simple editors to enter and maintain master
data. So you might want to have a look at want Rails provides (not
talking about Rails semi-automatic ORM here).
Regards,
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
