I wanted to localize both value and title attributes of input element, but
got an error, that there can not be two wicket:message elements.
example:
input type=button wicket:id=addSomething
wicket:message=value:button.add wicket:message=title:button.title
Is this supported or not?
Regards,
I'm sorry, I had to look into WicketMessageTagHandler first. ;)
Previous question should be ignored. Thanks
shumbola wrote:
I wanted to localize both value and title attributes of input element,
but got an error, that there can not be two wicket:message elements.
example:
input
See org.apache.wicket.markup.html.basic.SimplePageTest and
org.apache.wicket.markup.parser.filter.WicketMessageTagHandler.
From that test:
html xmlns:wicket
body
wicket:message key=myKeyNotExstsDefault Text/wicket:message
wicket:message key=myKeyDefault Text/wicket:message
wicket:message
Please see the javadoc for WicketMessageTagHandler
Juergen
On 6/5/07, Jonathan Locke [EMAIL PROTECTED] wrote:
Is there something like wicket:message for localizing attributes like title
tooltips? I looked on the WIKI but there wasn't anything there.
--
View this message in context:
Is there something like wicket:message for localizing attributes like title
tooltips? I looked on the WIKI but there wasn't anything there.
--
View this message in context:
http://www.nabble.com/wicket%3Amessage-for-attributes--tf3874468.html#a10978311
Sent from the Wicket - User mailing list
Hi,
how do I turn off escape string in wicket:message ?
a typical use case is:
wicket:message key=copyright[Copyright here]/wicket:message
copyright=Copyright copy; 2005
I search the doc and source but nothing found...
It would be better one can add an attribute like
wicket:message key=foo
add a jira issue
-igor
On 3/7/07, Ingram Chen [EMAIL PROTECTED] wrote:
Hi,
how do I turn off escape string in wicket:message ?
a typical use case is:
wicket:message key=copyright[Copyright here]/wicket:message
copyright=Copyright copy; 2005
I search the doc and source but nothing
* Igor Vaynberg:
personally
input type=submit value=wicket:i18n:my_key/
looks better to me
Do you really mean to embed a namespace prefix inside the
attribute value? AFAIK there's no XML parser that can parse such
constructs without checking every attribute value manually.
Do you
well..this is what it would be...checking every attribute of every tag. this will be done only once when the markup is loaded into the cache so there wont be a performance hit.-Igor
On 8/3/06, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* Igor Vaynberg: personally input type=submit
that is correct. Which has the side effect that if the property files
(or db entry or whatever) changes, it will not be reflected in the
output generated. However this downside is a) only relevant for
development b) if the markup cache is cleared, than the markup will be
reloaded incl the new
see wicket:message. It exists a tag like wicket:message .. and as
attribute wicket:message. It is a first draft, not added by default (I
think), not needs some improvements to accomondate packaged refs etc.
as well. That is easily doable.
Juergen
On 8/3/06, Jean-Baptiste Quenot [EMAIL PROTECTED]
my primary concern is making it easy for our users.we are not talking about just wicket: we are talking about wicket:i18n: and wicket:packaged: prefixes - what do you really think the odds are with a user collission?
i agree that it is not as clean/safe as a separate attribute, but it is
Time for a vote then? Does anyone see any potential problems with the
whole issue?
Eelco
On 8/3/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
my primary concern is making it easy for our users.
we are not talking about just wicket: we are talking about wicket:i18n: and
wicket:packaged:
time for a vote? Which kind do we want now?i like the simple parsing one:input type=submit value=wicket:i18n:my_key/or if we want default values:
input type=submit value=Default Value wicket:message=value:my_key/both are fine by me and we could support both versions just fine.
johanOn 8/3/06,
I'll start another thead for voting.
Eelco
On 8/3/06, Johan Compagner [EMAIL PROTECTED] wrote:
time for a vote? Which kind do we want now?
i like the simple parsing one:
input type=submit value=wicket:i18n:my_key/
or if we want default values:
input type=submit value=Default Value
I think supporting both versions, while noble, is only going to confuse users. More importantly, it's going to confuse me. :)On 8/3/06, Eelco Hillenius
[EMAIL PROTECTED] wrote:
I'll start another thead for voting.EelcoOn 8/3/06, Johan Compagner [EMAIL PROTECTED] wrote: time for a vote? Which kind
We just don't tell you we support both. But I agree.
Eelco
On 8/3/06, Nick Heudecker [EMAIL PROTECTED] wrote:
I think supporting both versions, while noble, is only going to confuse
users. More importantly, it's going to confuse me. :)
On 8/3/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
personallyinput type=submit value=wicket:i18n:my_key/looks better to mei was also just thinking aboutimg src="">
which would autocreate image component with a packaged ref. not sure about resolution rules yet but this would def be helpful to inline images/css quickly-IgorOn 8/1/06,
Jean-Baptiste
On 8/2/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
i was also just thinking about
img src=wicket:packaged:foo.gif
which would autocreate image component with a packaged ref. not sure about
resolution rules yet but this would def be helpful to inline images/css
quickly
Would this also do
yes it should. the same way packaged refs would. You provide foo.gif
only to the packaged ref as well, right?
Juergen
On 8/2/06, Martijn Dashorst [EMAIL PROTECTED] wrote:
On 8/2/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
i was also just thinking about
img src=wicket:packaged:foo.gif
+1 for this. i don't like that other extra approachExcept when we say we wat that page to be displayed ok with default values:input type=submit value=Default Value wicket:message=value:i18n:my_key/
that could be a possibility for me.johanOn 8/2/06, Igor Vaynberg [EMAIL PROTECTED]
Yeah, that's the nice thing about Cocoons approach: it doesn't screw
up previewability.
Eelco
On 8/2/06, Johan Compagner [EMAIL PROTECTED] wrote:
+1 for this. i don't like that other extra approach
Except when we say we wat that page to be displayed ok with default values:
input
i dont know, the default value is worth it sure, but i really like wicket:message and wicket:packaged, etc. its a consistent way to modify tags attributes.so maybe even value=wicket:message:key:default, you lose the ability to use : for defalt but i think thats ok. the preview is not the greatest
you can use an attribute modifier to do this though.
I usually put a StringResourceModel on the button like this:new Button(buttonid, new StringResourceModel(key_in_properties_file, this, null)) {public void onSubmit() {...}
}
* Igor Vaynberg:
not from the markup no. we couldnt find any good syntax to specify the key
and that the value should be internationalized.
In Cocoon we use:
input type=submit value=my.i18n.key i18n:attr=value/
The name of the attribute to internationalize is indicated by the
i18n:attr
At least I like it better than any other idea we came with so far.
Juergen
On 8/1/06, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote:
* Igor Vaynberg:
not from the markup no. we couldnt find any good syntax to specify the key
and that the value should be internationalized.
In Cocoon we use:
Second that. If someone would care to issue a feature request for that
(or even include a patch, that would rock!) we can see whether we
could implement such a thing.
Eelco
On 8/1/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
At least I like it better than any other idea we came with so
should be simple to implement. Just modify the handler (IMarkupFilter)
which handles wicket:messages. No change to core required at all. It
is all plugplay. If someone wants to give it a try I'm more than
happy to support.
Juergen
On 8/1/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Second that.
Hi everybody,
I would like to know if there is a way to do localisation like
wicket:message but inside tags.
IE:
input type=submit value=my localized message/
Thanks,
--
Jean-Philippe Toupin
[EMAIL PROTECTED]
NetUltim / Ultimation s.e.n.c.
www.netultim.com
not from the markup no. we couldnt find any good syntax to specify the key and that the value should be internationalized. you can use an attribute modifier to do this though.in your specific example - if you attach a button to that input tag the button's model is used to feed the value attribute,
Hello,
I get an error while using wicket:message
in my html. Did you forget to add 'message' to the wellKnownTagNames or
do I need to do this myself?
thanks!
stacktrace :
Root cause:
java.text.ParseException: Unkown tag
name with Wicket namespace: 'message'. Might be you haven't installed the
yes, and it is already fixed in SVN trunk.
Juergen
On 4/5/06, Marieke Vandamme [EMAIL PROTECTED] wrote:
Hello,
I get an error while using wicket:message in my html. Did you forget to add
'message' to the wellKnownTagNames or do I need to do this myself?
thanks!
stacktrace :
Root
32 matches
Mail list logo
