I don't know if my use-case is enough of a reason to clutter up the
interface of WebPage. I also don't know if there is a reason to widen
this facility beyond adding AttributeModifiers. But for what it's
worth, here is my simple suggestion.
Honestly, I'm not in favour of cluttering the interface. What about an
Interface with one method which if your Page implements it, the method
is called. That method could be addBodyAttributeModifier. Thus, we do
not clutter the interface, but it is far less obvious for wicket user
what to do to achieve it => good javadoc/wiki
You're right. Much cleaner. Where should that interface live?
wicket.markup.html?
-- Scott
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
