forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject Re: [jira] Commented: (FOR-934) i18n language override menu
Date Fri, 22 Sep 2006 08:58:52 GMT
Sjur Moshagen wrote:
> Den 21. sep. 2006 kl. 12.10 skrev Thorsten Scherler:
> 
>>> I've not been following the i18n discussions, but I have to admit that
>>> when I saw Thorstens comments I wondered "why not core?".
>>>
>>> I'm not doing the work on this so do it however you like. But if you
>>> want my (possibly uninformed) opinion then I'd say core is the right 
>>> place.
>>>
>>
>> Hmm, after all the feature contains a dispatcher contract. Further who
>> said core cannot be in a plugin?

In my previous reply I missed the "contains a dispatcher contract" part...

I got the impression that this code would work with skins too is that 
not the case?

The dispatcher contract should be part of the dispatcher, not part of 
core, or another internal plugin. We do not have a mechanism for plugin 
dependencies and I don't think this use case warrants one.

If the i18n work is useless without this contract then this is of no use 
to Forrest users who are not using dispatcher, therefore it is a 
dispatcher feature.

Can it be generalised for skins?

Ross

Mime
View raw message