yes, any markup container can implement the interface. but be warned :)
-igor
On 3/27/07, Chris Colman <[EMAIL PROTECTED]> wrote:
I think it would be awesome if we could implement our own
IComponentResolvers. I could make a truly markup driven page class that
loaded components specified in the markup 'on demand' as they were
parsed in the markup.
I realize that I could probably use
<wicket:component class="myApp.MyTable" key=value>
For this purpose but I think it's much easier if the graphics designer
only has to use:
<span wicket:id="myTable"/>
I know the lifecycle document at
http://www.wicket-wiki.org.uk/wiki/index.php/Lifecycle
warns against such rebellious undertakings but would it still be
possible to implement my own IComponentResolver and add components to a
page 'on demand'?
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
