Beautiful solution Guido! I cleaned it up a bit and it looks like:
public WOActionResults performActionNamed(String actionName) {
if(!context().hasSession()) {
ERXLocalizer localizer =
ERXLocalizer
.localizerForLanguages(context().request().
On 15.05.2008, at 17:34, Rams wrote:
I think I will look into direct actions and hiding the session in a
cookie perhaps :-)
Why? You can use a sessionless application easily with the correct
localizer!
Do something like this in your base "performActionNamed":
public WOActionResults perfo
I just wanted to say thanks again everyone, and correct one
misstatement...
I've discovered that a sessionless ERXComponent localizer() indeed
does use the default localizer in both localized and non-localized
components. I must have been mistaken earlier, as I thought it was
using the p
On May 15, 2008, at 11:46 AM, Daniele Corti wrote:
2008/5/15 Rams <[EMAIL PROTECTED]>:
Almost there I think...
That works, but now my sessionless localizer in my ERXComponent is
broken.
returns English strings in both components where
Because when you change ERXSession.setLanguage() to
As it's the session that sets the localizer for the current context,
you may want to add that code from ERXSession to
app.appendToResponse() or whereever.
Am 15.05.2008 um 15:42 schrieb Rams:
Almost there I think...
That works, but now my sessionless localizer in my ERXComponent is
broke
2008/5/15 Rams <[EMAIL PROTECTED]>:
> Almost there I think...
>
> That works, but now my sessionless localizer in my ERXComponent is broken.
>
>
> returns English strings in both components where
>
Because when you change ERXSession.setLanguage() to Japanese, or using
Properties file er.extensi
Almost there I think...
That works, but now my sessionless localizer in my ERXComponent is
broken.
returns English strings in both components where
returns the proper string in the Japanese component. Anyone ideas?
Thank you everyone!
On May 15, 2008, at 4:38 AM, Daniele Corti wrote:
2008/5/15 Rams <[EMAIL PROTECTED]>:
> Thank you both for responding! It has taken me a while to get back to
> this.
>
> Localizing strings seems to work fine. I have my English.lproj and
> Japanese.lproj folders in my Resources folder. I moved my Main.wo
> (ERXComponent) to my English.lproj fol
Thank you both for responding! It has taken me a while to get back to
this.
Localizing strings seems to work fine. I have my English.lproj and
Japanese.lproj folders in my Resources folder. I moved my Main.wo
(ERXComponent) to my English.lproj folder, and when I attempt to
create a Mai
Hi TIA
In addition if you are not using sessions you can get your localizer
with
ERXLocalizer.defaultLocalizer()
and if you are using ERXComponent's you can call
localizer()
directly from the component
Regards,
Cail
and if you are not using sessions
On 13/04/2008, at 10.
Hi TIA,
very simple and Apple Style as usual...
Just add the language resources you need in your Resources folder. I
for example have a
German.lproj and
English.lproj
Inside these folders add your Localizable.strings file with the key-
value-pairs for the localized strings (if you use Unico
Hi all,
Can anyone point me in the direction of information regarding how to
localize a WOLips project. The process was fairly straightforward in
xcode, but I can't seem to find any info on WOLips. I would like to
know how to localize components as well as strings.
TIA
--
Learn how to
12 matches
Mail list logo
