you could also create: mypage_de.html
which would be completely german then.
The problem is that you then have to maintain 2 pages if the component
structure changes.
johan
Nick Heudecker wrote:
Okay, new problem. I need to retrieve localized messages for the HTML
pages. Things like
Maybe I'm still thinking with a Struts mindset, but doesn't that seem
just a bit excessive?
On 7/12/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
Wicket is very Java centric, so yes, it means that you need to add
labels as components, and if you want to attach localized strings to
them, you
Hi,
i'm new to Wicket and just got passed the reading-all-about-it phase
and starting to do a little app. just wanted to jump in here with a
quick question related to the locale post.
I made the experience that using localized templates is quite ok if
you're not exclusively dealing with
yes wicket does that.
It looks up html like a resourcebundle and you also can have different
styles
MyPage.html
MyPage_locale.html
MyPage_style_locale.html
and in 1.1 you now also have:
MyPage_variation_style_locale.html
locale can be de_DE or de
style is a global session thing (that you
Well, it's a matter of making choices really. For Wicket it is a design
decission to make everything a component, and nest those components
hierarchical. This has advantages and disadvantages. To start with the
disadvantages: some things - like you localized labels - are more
verbose than they
On 7/12/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
Well, it's a matter of making choices really. For Wicket it is a design
decission to make everything a component, and nest those components
hierarchical.
How about dynamic changing of component structure in runtime or at
least swapping
