this has been discussed to death many times already :)
basically the consensus is, as i see it, is that it is silly to extract an
IFormComponent until we have an IComponent, otherwise you end up with a
crappy interface like IPageable. in wicket 3.0 we plan on refactoring the
core to be based on interfaces, so this will have to wait until then i
guess.
-igor
On 12/26/06, Jonathan Sharp <[EMAIL PROTECTED]> wrote:
It would be really nice to have an interface for FormComponents that would
allow us to develop compound inputs (which would still operate on a single
value). Any thoughts on this?
For now I've created a wrapper object that proxies calls between
FormComponent and MyFormComponent objects.
-js
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user