On 9/14/06, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > Some more food for thought or what we should support and what not. > > Transparent containers allow you to add a component to the transparent > container and the markup is expected to be in the transparent > containers parent. Thats why it is called transparent. I'm fine with > this use case and I think we should support it. > > In contrast with a bordered page you add the component to a container > (e.g. Page) and the markup can be found in any transparent container > which is also a child of Page. In order to find the markup for the > component you hence must scan the Pages markup file the components > markup as well as the markup associated with all transparent > containers also add to Page. This use case (e.g. bordered pages), IMHO > we shouldn't support. > > I currently believe there is too much magic involved in the latter use > case and as already mentioned you'll find quite some clunky code in > the code base already to just support that use case. I'd much try to > stay as close as possible to the 1:1 mapping of component hierarchy > and markup hierarchy.
+1 Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
