Sebastiaan van Erk schrieb:
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!
maybe you should go to a doctor then?...
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...
whats difficult here? it gives you maximum flexibility and was just a
example(tm) which can be further simplified if you use other container
types - this was showed to me by Igor some time ago and it has proven
its success for me...
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!
usually this kind of code is present at 1 place within a project, not in
every class, just the raw baseclass (maybe in 2 baseclasses if you have
a designer who wants to have 2 completely different markups for 1
project) - compared to other existing poblems of webdeveloping (like
security and authorization) these 2-minutes i spend on this at all is
not really mattering...
Best,
Korbinian
Regards,
Sebastiaan
eg: html:
...
<div wicket:id="anything">Place to put anything</div>
-zip-
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
