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.
I do not want to start any discussion about how wicket works (in a style wicket x echo), I'm very happy with wicket and thanks to all developers... I only think, that the Panel can be improved or added some new functionality to wicket, which would enable developers to created 'panel like components' without need to extend Panel (eg. implement some interface (like IHeaderContributor) or override some method, ...) so the reuse of existing components in repeaters would be easier. But may be I overlooked something, so please let me know, if there is some easier way and more elegant way than I the one selected. I do appreciate any comments (even the bad ones) and suggestions Petr Sakar -- View this message in context: http://www.nabble.com/Change-of-panel-tp14797276p14797276.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
