and completely dynamic layout can also be done with the use of panels.
So your basepage only has the portions filled in where the panels are
placed.
But the my question is shouldn't you just make different pages?
johan
On 12/28/06, Carfield Yim [EMAIL PROTECTED] wrote:
I feel using Markup
hi, I am new to wicket, I have just done some examples tutorial starting
from the QuickStart app.
I am beginning to build a real webapp and I am wondering about the main
layout structure
I have done the Navomatic example and I am wondering if a good way is to use
borders to define the structure
imho much better to use markup inheritance for a common layout. that example
was written before markup inheritance was around.
-igor
On 12/27/06, Daniele Dellafiore [EMAIL PROTECTED] wrote:
hi, I am new to wicket, I have just done some examples tutorial starting
from the QuickStart app.
I
I agree with Igor. See
http://wicketframework.org/ExampleMarkupInheritance.html for a small
example of markup inheritance.
Martijn
On 12/27/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
imho much better to use markup inheritance for a common layout. that example
was written before markup
I feel using Markup interitance over Border is more similar to using
interitance over composition of code reuse. Markup interitance is more
convenience to use but if you like to do something more dynamice, like
change layout according to role, I think Border is more flexible for
that? Please
depends.
if you have a preset number of themes/etc then you can still use markup
inheritance in combination with styles/variations to load different markup
files for the base page.
if, however, you need to load themes dynamically via a factory or some such
then you have to use a border. but
