Can you provide a quickstart of your panel (the one you already developed and which works nice)?
Juergen On 10/27/06, Petr Sakar <[EMAIL PROTECTED]> wrote:
> Can you be more specific as to why you don't want to inherit from > Border, Panel or Fragment? The usage is mainly for dynamic forms. 1. you define your components and their markup (TextField, DropDownChoice, ...) and some panel 2. adds them to panel, which is doing their layout to some table You can then write forms without need to write html templates for forms. Basically you would not have to use panel as wrapper instead of that you would be able to use existing components, subclass them to implement such interface and define their html template. I've alredy done such panel for one our project, and it works nice. It saves a lot of work ... saki > > Martijn > > On 10/27/06, Petr Sakar <[EMAIL PROTECTED]> wrote: >> Hi, >> currently (wicket 1.2) if I want to make component with own markup, I >> must >> extend Panel, or override some method to provide markup. >> Can you use as well interfaces to give framework hint that the component >> has its own markup in html template ? >> >> For example if component would implement interface BodyMarkup, the html >> template would be looked up. If it would implement interface >> HeadContributor, you would know it is contributing to page head. >> >> saki >> > > > -- > <a href="http://www.thebeststuffintheworld.com/vote_for/wicket";>Vote</a> > for <a > href="http://www.thebeststuffintheworld.com/stuff/wicket";>Wicket</a> > at the <a href="http://www.thebeststuffintheworld.com/";>Best Stuff in > the World!</a> >
