> Korbinian Bachl wrote: > > you missed solution3: > > the real-wicket-way(tm) for multiple content-places in a tied page-area: > > Whaaa, I seriously hope this is not the real-wicket-way! My brain hurts! > > A framework is supposed to make things easy and readable! The code below > is just way too complicated to achieve something that should be easy... > > Preferably when doing simple stuff like this, I don't want to be > confronted with things like rendering (and adding render hooks), or with > keeping extra state about components being or not being initalized. Also > I don't want to have to copy this boiler plate for every time I want to > place some kind of component "hole" in a base page! >
Well said! I agree wholeheartedly. I suppose the reason I'm so passionate about this new multiple child/extends support is that it helps preserve simplicity for the wicket developer instead of making our more complex. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
