Hi, 1) I would choose a Panel
2) Sounds like Markup Inheritance would help you here. Create some Base Panel and then extend this class and the markup and include the different Components, if any. Hope this helps Regards, Timm Am Thursday 09 October 2008 19:08:25 schrieb miro: > I have a page with same pattern but different data in several td > tag. Like > > Header1 > link 1 > link2 > link3 > > > header2 > link1 > link2 > > and so..on > > I dont want to repeat the same html for header1 header2 instead I want to > make a custom component which takes header and RepeatingView for links > ,So in my html i just give the id of the component and the component html > is used . > to acheieve this I have few questions > 1st > For this should I use a webmarkupcontainer or a panel as super class for > my custom component ?and why should > 2nd > my custom component html is very little and i dont want to create a html > page instead > I want customize the lookup of html ie just tell wicket use this html to > render my custom component or give wickwet some html to render my > component --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
