One thing I can imagine is a form with a panel attached, that you feed a java bean. Based on the properties of that java bean (using introspection), you could add form fields to the form.
This is quite easy to accomplish for simple introspection, though if you really want to do a good job, it's more work because you should then do the whole java beans trick with property descriptors etc.
Is that more like what you need?
Our old jsp/servlet -based system has thing just like this, so I have existing code to do this (ie. generate user interface on-the-fly based on java model class). However, this isn't always enough, since user interface layout is always pretty simple, just rows containing label - field (or drop down list/radiobutton) pairs. Although this works functionally ok, it isn't very good-looking.
I'm going to prototype this kind of component also with wicket if I have time to do it.
The other case I was originally posting about (ie. having full
screen design in html) is pretty much standard wicket use, only
with small optimization related to coding work (ie. instantiate
suitable wicket components like TextField, DropDownChoice, RadioChoice based on bean's attribute type).
Maybe I misunderstood your suggestion ? When saying "you could add form fields to the form" did you mean html contents or just wicket field etc. instances ?
Ari S.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
