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 change it at Java code.
2- If the style is going to be the same everywhere why bother in
parameterizing it at Java level?
Best
Ernesto
On Tue, Dec 23, 2008 at 3:54 PM, walnutmon <justin.m.boy...@gmail.com>wrote:
>
> I have found very little in my wicket books, and on this forum in terms of
> adding styles to components through java. Is this because it's outside of
> the scope of wicket?
>
> As an example. If I have a panel, and I want all of those panels to have a
> style class "someComponentClass", is it better to keep that information in
> the HTML? Or can I assign that behavior through the .java code?
>
> 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.
>
> best,
> justin
> --
> View this message in context:
> http://www.nabble.com/Applying-Styles-Through-Java-tp21145758p21145758.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
