Thanks, Nino, for the clarifications.
On 18.02.2009, at 18:10, Nino Martinez wrote:
No. Just bundle the default with panel... You could create your own
resource loader but seems overkill...
Why do you want it working differently?
I am looking for a different way because I want to make the life
easier for the "users" of my components: You could consider "somediv"
to be an implementation detail of the component, something that the
designer of the component might want to change later on (as I did in
my example). -- If he does, it will, however, require the users of the
component to change their properties files. This happened to me
without me realising it until a user informed me that the description
of a field has suddenly changed from a very useful explanation to
"Enter some text" (the default message)...
You could also do it with resource models and labels.. etc the java
way...
Okay, I see. -- I know this issue is not so important. Still, Wicket
is such a pleasure to work with as far as coding reusable components
is concerned, that it would be cool to have an easy way to "export"
overridable keys which relieves me from adding lots of models that
clutter my code. Maybe a <wicket:export-message key="msg"
binding="somediv.msg"/> or an annotation? Well, just ideas... -- I
guess the bottomline for me is that I should not use <wicket:message>
if I need complete freedom inside my component.
Kaspar
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
