Sure there a dozens of ways todo this, mine is just one of them. Im
starting a new thread since it'll be more exposed then.
The idea is following:
Parent:
public class BasePage extends WebPage {
protected final String LINK_LABEL_ID = linkText;
protected final String LINK_ID = link;
EEK!, I'll try once more to create a new thread!
Nino Saturnino Martinez Vazquez Wael wrote:
Sure there a dozens of ways todo this, mine is just one of them. Im
starting a new thread since it'll be more exposed then.
The idea is following:
Parent:
public class BasePage extends WebPage {
Sure there a dozens of ways todo this, mine is just one of them. Im
starting a new thread since it'll be more exposed then.
The idea is following:
Parent:
public class BasePage extends WebPage {
protected final String LINK_LABEL_ID = linkText;
protected final String LINK_ID = link;
On 3/5/08, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote:
Sure there a dozens of ways todo this, mine is just one of them. Im
starting a new thread since it'll be more exposed then.
The idea is following:
Parent:
public class BasePage extends WebPage {
protected
James Carman wrote:
On 3/5/08, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote:
Sure there a dozens of ways todo this, mine is just one of them. Im
starting a new thread since it'll be more exposed then.
The idea is following:
Parent:
public class BasePage extends
Answer below:
James Carman Wrote:
Couldn't you use a VelocityPanel to generate your markup and have it
parse the markup after it's generated to avoid the whole need to use
the right markup ids part? I was thinking about doing something like
this for generating dynamic editor
On 3/5/08, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote:
Answer below:
James Carman Wrote:
Couldn't you use a VelocityPanel to generate your markup and have it
parse the markup after it's generated to avoid the whole need to use
the right markup ids part? I
James Carman wrote:
On 3/5/08, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote:
Answer below:
James Carman Wrote:
Couldn't you use a VelocityPanel to generate your markup and have it
parse the markup after it's generated to avoid the whole need to use
the
I do basically the same thing, but since the title does not change on my
pages I see no need to have a (dynamic) model for the property, plus I
just use the constructor to set it, which saves some loc. In other words:
public abstract class BasePage extends WebPage
{
// ...
public
The way I do it is; dont specify a title in your base page then just add the
title in the subpage:
base page.html
html
!-- anything shared in all the pages eg a base.css file --
head
/head
body
wicket:child/
/body
/html
subpage.html:
wicket:head
titlehard code or use wicket label to
On 3/4/08, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
I do basically the same thing, but since the title does not change on my
pages I see no need to have a (dynamic) model for the property, plus I
just use the constructor to set it, which saves some loc. In other words:
public abstract
On the other hand, I've also done something with listviews.. Allowing
sub pages adding markup items to menus etc Using the listviews as
place holders...
Kaspar Fischer wrote:
Ah, 'course! Should have thought of it, that's an option they mention
in Wicket in Action.
However, Sebastiaan's
On 3/4/08, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
James Carman wrote:
The problem with this approach is that you're not able to localize the
title if you hard-code it. What I've done is actually specify a key
for my messages file and I use that. So, every page has to define its
James Carman wrote:
The problem with this approach is that you're not able to localize the
title if you hard-code it. What I've done is actually specify a key
for my messages file and I use that. So, every page has to define its
page.title key in its PageClass.properties file.
That's what I
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of James Carman
Sent: Tuesday, March 04, 2008 10:53 AM
To: users@wicket.apache.org
Subject: Re: Page title when using markup inheritance
On 3/4/08, Sebastiaan van Erk [EMAIL PROTECTED] wrote:
James Carman wrote
could you share this technique? i think this might be a good idea.
Nino.Martinez wrote:
On the other hand, I've also done something with listviews.. Allowing
sub pages adding markup items to menus etc Using the listviews as
place holders...
Kaspar Fischer wrote:
Ah, 'course!
16 matches
Mail list logo
