Well, I dont want anything messy :) Hope, that one day I know enough of the internals, so that I can make suggestions that makes more sense. Now the messy thing for the web designer is that html will get into separate, small html-files. I was trying to figure how that could be enhanced.

2005/10/8, Eelco Hillenius <[EMAIL PROTECTED]>:
I can't see how that could ever work; Wicket doesn't work like that...
has to work with (sub)classes. Something like the following might:

MyPanel.html:
<wicket:panel class="$EditPanel">
<input type="text" wicket:id="something">
</wicket:panel>
<wicket:panel class="$ViewPanel">
<span wicket:id="something">
</wicket:panel>

public class MyPanel extends Panel {

public static class EditPanel extends Panel

EditPanel(String id) {
   super(id);
   add(new TextField("something", model));
}
}

public static class ViewPanel extends Panel

ViewPanel(String id) {
   super(id);
   add(new Label("something", model));
}
}

}

But... it would be quite messy in the end, so I wonder whether it
would be worth the effort.

Eelco


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to