Wicketopia does some of this kind of stuff, but it's based on
class/property metadata.  Basically, it auto-creates forms for you on
the fly based on annotations you put on the field values.

You *could* also use Velocity to dynamically generate your markup at
runtime, also.  That's an interesting approach that I thought about
trying but never really got around to it.  It should work, though.

On Tue, May 4, 2010 at 1:23 PM, Brian Mulholland <blmulholl...@gmail.com> wrote:
> I don't have this situation right now, it's mostly curiosity, but I've
> had these requirements at times in the past.  If I had a panel whose
> appearance was highly dynamic, say perhaps because it was driven by
> some personalization or data, can a Wicket panel add components that
> don't have a corresponding tag in HTML?
>
> So I would just have a tag for where the wicket panel renders, but the
> panel might consist of an unknown combination of other controls so
> that I could not have a static HTML template for it.  How might I
> handle that in wicket?
>
> Brian Mulholland
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Reply via email to