Hi,
thanks for your answer. I was a surprised that there is no model
abstraction of link in wicket...
I will take a deeper look at the tabs package - thanks for the hint.
Johannes Schneider
John Krasnay wrote:
One idea would be to create a class that represents the logical idea of
a link,
One idea would be to create a class that represents the logical idea of
a link, e.g
public class NavEntry {
private String title;
private Class pageClass;
private PageParameters parameters;
...
}
Pass a list of these to the constructor of your panel, which then
renders these
Hi Johannes,
If you can hard code the links in your markup, it might be worth to try
autolinking.
Tom
Johannes Schneider wrote:
Hi,
I am new to Wicket and I really like the things I have seen so far. But
I also have a few questions.
At the moment I create a small page. Therefore I have
I don't want to hard code the links because I use the Component several
times with differen links. I also would like to use the component in the
next project too.
Johannes Schneider
Thomas Singer wrote:
Hi Johannes,
If you can hard code the links in your markup, it might be worth to try
