Thanks all ideas, I will try these to see which is better :-) On 9/7/06, Igor Vaynberg <[EMAIL PROTECTED]
> wrote:there are examples in extensions already that load markup from a different place - all you have to do is pass a parameter to the page - maybe a file name - and that page can use the ma
there are examples in extensions already that load markup from a different place - all you have to do is pass a parameter to the page - maybe a file name - and that page can use the markup from that file to render itself.
or another way is to use a regular page that adds a label whose model points
Actually I like this Page/Panel/Border class <-> markup enforcement
because it means there is no magic, it is a very simple rule, it is
very easy to understand. But this of course is my own opinion. If you
come up with an implemention which can be added to wicket-extension,
than it is fine by me. W
Hi all, Wicket provide very good page inheritance, and it's perfect for page layout.However, as far as I know, to apply layout to static, logicless page, we still need to create a blank page class:
public class MyStaticPage extends MyBaseLayoutPage { //does nothing} MyStaticPage
