On 6/12/07, Patrick Angeles <[EMAIL PROTECTED]> wrote:
> I'm not that deep into Wicket yet, but my idea was that there would be Java
> classes that represent various page templates and panels. The component tree
> could be dynamically built using metadata from a DB. So the URL would
> basically invoke a Page class which looks up an entry in the database
> corresponding to that URL. This entry will have associated CMS metadata that
> instructs the page on how to build its component tree.
Yep, that should work. Encapsulate everything that can only be known
at runtime in panels, and you can build your component tree completely
dynamically.
if (foo) { add(new TextFieldPanel(id); } else { add(new
GridEditorPanel(id); } etc
Eelco
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
