Look at the list of problems I have with a solution like this. I don't
want this in core, or extensions. At best in wicketstuff-minis
I'd prefer having an example on the site showing this as how to build
custom components yourself, instead of adding it to core.
Instead of giving someone a fish, t
Johan, Martijn,
Thanks for the explanation and the solutions. I understand the issues
now.
Unfortunately for a new comers such as me, the problems are not obvious
and we're trying to map all what we've done with the traditional
frameworks to Wicket and hence we land up in trouble. e.g I'm us
public abstract class LabelLink extends Link {
private IModel labelModel;
public LabelLink(String id, IModel linkModel, IModel labelModel) {
super(id, linkModel);
this.labelModel = labelModel;
}
protected void onComponentTagBody(MarkupStream markupStream,
Com
There are several reasons:
* That would make the link too limited. It is a WebMarkupContainer,
meaning you can put an image, label, panel, table, div, fragment,
border, etc inside the link.
* The previewability would suffer and it add too much magic: what
would you do with text already inside the
