Use the StringResourceModel with properties bundle, it is very powerful
because you can add dynamic data coming from the model. I've done some
things like this, assuming infoModel.dateFormat() returns a formated date :
new Label("tableTitle", new StringResourceModel("table.title", this, new
Model
No, javadoc is ok. You are right. My mistake, sorry.
-Original Message-
From: Jeffrey Schneller [mailto:jeffrey.schnel...@envisa.com]
Then is the javadoc wrong?
This was taken right from the javadoc?
http://wicket.apache.org/docs/wicket-1.3.2/wicket/apidocs/org/apache/wic
ket/model/Stri
s?
weather.overcast=Best take a coat to be safe
-Original Message-
From: Bernhard Michal [mailto:michal.bernh...@tigra.cz]
Sent: Friday, October 16, 2009 2:15 PM
To: users@wicket.apache.org
Subject: RE: Localization of values coming from my Model
It doesn't seem correct...
StringResourceModel expect string which is supposed to be resource key
to find localization in resource bundle.
I recommend you to read
http://cwiki.apache.org/WICKET/localization-and-skinning-of-applications
.html.
-Original Message-
From: Jeffrey Schneller [ma
-
From: Bernhard Michal [mailto:michal.bernh...@tigra.cz]
Sent: Friday, October 16, 2009 1:39 PM
To: users@wicket.apache.org
Subject: RE: Localization of values coming from my Model
Why don't you use special model for each component?
Because this is very specific thing - CompoundProperty
Why don't you use special model for each component?
Because this is very specific thing - CompoundPropertyModel is not
supposed for this kind of model value's processing stuff.
For example for activeString:
add(new Label("activeString", new AbstractReadOnlyModel() {
@Override
public Strin
