Hello Eelco, thank you for your response. I've checked the FormComponentPanel, but if I want to use it in forms I would have to reimplement all the functionality of such components (eg. Button, CheckBox, TextField, ...), which would be definitely reinventing the wheel. I'm looking for how to do the following:
1. create subclass of existing component (eg. TextField) and corresponding html file. 2. modify my class (override some method(s) or better by implement some interface (hopefully empty)) As a result I would be able to use it in repeaters. I did it in my example, but I think and hope it could be done in some better way. Petr Sakar Eelco Hillenius wrote: > >> Hello, >> would it be possible to make some little changes in component markup >> lookup, >> which would allow to control if the markup is inherited or is in the html >> file ? Currently if I want to specify for formComponent own lookup, I >> have >> to extend Panel, which is little bit painful. I've created example of >> such >> functionality - >> http://www.chare.eu/test/panel.zip >> The main goal is to be able to produce lot of forms using same components >> without >> the need to write html for form (only once for component). The embedding >> of >> such components in panel is little bit painful, so I tried a bit >> different >> approach. > > Check out FormComponentPanel. > > Eelco > > -- View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14837979.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
