Hi Johan,
that really rocks! wicket really is a groovy framework.
-andi
On Jul 12, 2005, at 23:08 Uhr, Johan Compagner wrote:
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 i
Michael Jouravlev wrote:
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 i
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 c
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
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
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
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
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 for
I meant: in your markup directly, without having to code Java.
If you want to use e.g. localized labels in your markup, you can make
a reusable component, and address it like:
---
This SF.Net email is sponsored by the 'Do More With D
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 should use StringResourceModels.
If you want to use e.g. localized labels in your markup, you can make a
reusable component, and address it like:
Okay, new problem. I need to retrieve localized messages for the HTML
pages. Things like form field names and error messages. There must
be a way to just put a Wicket tag into the HTML markup without having
to add more Java code to the Page class.
--
11 matches
Mail list logo
