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).
That's something you could do with panels. The advantage of using panels here is that you can have a form like:
<form ...>
<ul wicket:id="myFormFieldsListView"> <!-- list view for all fields -->
<li><span wicket:id="myFieldPanel" /></li> <!-- for each field insert a panel -->
</ul>
</form>
now, in one case your panel can be:
<wicket:panel> <input type="text" wicket:id="input" size="50" /> </wicket:panel>
while in another it can be:
<wicket:panel> <input type="checkbox" wicket:id="input" /> </wicket:panel>
or:
<wicket:panel> <select wicket:id="select"> <option>option 1</option> <option>option 2</option> </select> </wicket:panel>
So... with a panel you can defer what you actual contents/ component sub tree will look like. Our form won't mind, and you can nest as deep as you want.
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 ?
I meant adding a wicket (form)component with HTML attached. By using panels you have both the component, and the markup (e.g. with just the <input type="text"...)
Ari S.
Eelco
------------------------------------------------------- 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
