I think this might depend on your use case:
1-If your are creating a component and you want it to tune to "look"
different on different "parts" of your pages it might be useful to have
something like:
component.add(new SimpleAttributeModifier("class", getMyStyleClassName());
So that you can chan
walnutmon wrote:
>
> Also, as an aside, where can I find wicket jars for the 1.3.5 release with
> javadocs contained so that I can see the javadocs from netbeans? I have
> had a heck of a time without them.
>
>
http://repo2.maven.org/maven2/org/apache/wicket/wicket/
At the moment I
You can do it in either but since its best to separate the display
from the logic, keep it in the HTML. Exception is if you need to
dynamically change the class etc.
HTML:
stuff
Java:
look at AttributeAppender
AttributeModifier that appends the given value, rather than replace
it. Thi
It depends :-) You may control the attributes of an element (e.g. attribute
"class") with
Component.add(new simpleAttributeModifier("class", "
someComponentClass");
Stefan
-Ursprüngliche Nachricht-
Von: walnutmon [mailto:justin.m.boy...@gmail.com]
Gesendet: Dienstag, 23. Dezem
