be implemented now?
Cheers,
Lars
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Geert Bevin
Sent: 25 November 2005 20:51
To: RIFE users list : questions, bug reports and suggestions.
Subject: Re: [Rife-users] localized login template
Hi Lars,
hmmm, good
Sent: 30 March 2006 11:00
To: RIFE users list : questions, bug reports and suggestions.
Subject: Re: [Rife-users] localized login template
Yes, you can tailor to priority of embedded elements now:
http://rifers.org/blogs/gbevin/2006/3/2/
rife_1_4_released#1_4_highlight04
On 30-mrt-06
users list : questions, bug reports and suggestions.
Subject: Re: [Rife-users] localized login template
Yes, you can tailor to priority of embedded elements now:
http://rifers.org/blogs/gbevin/2006/3/2/
rife_1_4_released#1_4_highlight04
On 30-mrt-06, at 10:53, Lars Grupe wrote:
Hi Geert
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Raoul Pierre
Sent: 30 March 2006 11:42
To: RIFE users list : questions, bug reports and suggestions.
Subject: Re: [Rife-users] localized login template
Lars,
With the patch I submitted yesterday to Geert about RIFE-258, it will
only
users list : questions, bug reports and suggestions.
Subject: Re: [Rife-users] localized login template
Yes, you can tailor to priority of embedded elements now:
http://rifers.org/blogs/gbevin/2006/3/2/
rife_1_4_released#1_4_highlight04
On 30-mrt-06, at 10:53, Lars Grupe wrote:
Hi Geert
Lars,
Should the path 'l10n/authentication/login' point to my login template?
No, to your resource bundle to be used by the template associated to the
element.
Pierre
___
Rife-users mailing list
Rife-users@uwyn.com
Hi Pierre,
maybe it would be a good idea for you to write a small documentation
piece about the features you implemented, as I do for the release
notes. This would make it easier for everybody and I can also just
integrate them in the release notes of the next version.
Feel free to use
Geert,
Have you any suggestion for the best place to put it in wiki? Atm a lot
about i18n is under Cook book Templates page. So may be a new entry
Translator there, even if it's possible to use it in other context.
Pierre
Hi Pierre,
maybe it would be a good idea for you to write a small
Geert
No,
it will be a property, you can set properties inside the rep tag
that will be used throughout the system.
You can override them in the site structure or for individual elements.
[...]
Since it should not store the element instance in the
LocaleProvider instance. The instance
Since it should not store the element instance in the
LocaleProvider instance. The instance will be constructor
through IoC and the element instance is not known in that
context. It's also much more appropriate since the element
instance changes at each request, and otherwise you'd
Geert,
Since it should not store the element instance in the
LocaleProvider instance. The instance will be constructor
through IoC and the element instance is not known in that
context. It's also much more appropriate since the element
instance changes at each request, and
No, if they are injected through IoC, the reference factory can
either provide the LocalProvider as a singleton,
singleton: is there no risk of confusion between 2 or more elements
from different threads?
Not with the interface I proposed:
ListLocale getLocales(ElementSupport)
since each
Geert,
either instantiate it at each use. This can then be injected into
a property. We still need to add simple reference factory features
to RIFE itself currently it delegates that to a repository
participant
can you give me a link to any howto.
Not a real howto, but this
No,
it will be a property, you can set properties inside the rep tag
that will be used throughout the system.
You can override them in the site structure or for individual elements.
On 3-dec-05, at 21:48, Raoul Pierre wrote:
Geert,
I think this method is better:
public ListLocale
Geert,
this is imho the job of a specific LocaleProvider implementation. Your
proposition could be a good fit for the DefaultLocaleProvider
implementation.
OK. Just to be sure, the only function of the interface would be:
ListLocale getLocales()
The element instance should be given to the
15 matches
Mail list logo
