One thing you can do is turn of the render check. Would that suffice? Eelco
On 3/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > I'm in need of 'optional' components, i.e. they exist in Java code but the > web designer is allowed to omit them in the HTML template. > > Currently I'm using a base class (named OptionalPanel) that cooperates with > the page: In Page#renderAll() all appropriate children are marked as being > rendered, if not already rendered by Wicket. > I'm not happy with the implementation though, as it seems to me more like a > hack :(. > > What do you think - could Wicket include a solution for this? A tag > interface? Or an #isOptional() on Component? > > Thanks > > Sven > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
