Nicolas Pettiaux wrote:
>Le Mercredi 13 F�vrier 2002 20:15, Juan David Ib��ez Palomar a �crit :
>
>>Hi all,
>>
>>Regarding the future of zope internationalization, we're working on it
>>(as much as available time we've). Zope 3.0 will be multilingual, this
>>is the goal.
>>
>
>>Regarding the future of Localizer, I continue developing it, after all
>>Zope 3 will take a while to arrive and we need a solution for Zope 2.
>>Also, there'll be a Localizer product for Zope 3, because not all the
>>features that it provides will be implemented on Zope 3.0. I'll also
>>make as easy as possible the migration from Zope 2 to Zope 3, for
>>the stuff related to Localizer, of course.
>>
>>If there's somehing else you want to know about this just tell me.
>>
>
>Thank you for the note.
>
>Can we understand this by
>
>"in investing in Localizer, we get assured that the multilingual aspects that
>we add to any Zope2 based site/application can be used in the
>correspondingly adapted Zope3 site/application".
>
>This is important to know that we preserve the investment.
>
>Thanks
>
>Nicolas
>
First, this is free software, there isn't any warranty, there's only a
personal commitment, as much as available time allows. The only
way to be sure that something is done is to pay for it (talk with
St�fane for that).
Zope 3 is supposed to be backwards compatible with Zope 2, if this
is true an application based in Localizer will work inmediately in
Zope 3.
Then, what I mean to move a Localizer application from Zope 2 to
Zope 3?
The question is how to upgrade from, for example, Localizer 0.9 to
Localizer 0.10.
The policy I use to introduce changes in Localizer is similar to the
policy used by Python. New interfaces are introduced, old ones are
deprecated but preserved for a while, and then removed. How much
time an old interface is preserved depends on the users, I keep them
until everyone has moved to the new ones.
When a change is done in the way the information is stored, something
that rearely happens, I provide automatic or semi-automatic ways to
upgrade the objects.
This policy is the thing that matters.
Use case:
- Imagine you've an application for Zope 2 that uses Localizer 0.9
- Then Zope 3.0 is released
- You move your application to Zope 3 and keep using Localizer 0.9,
it works because Zope 3 is compatible with Zope 2
- I release Localizer 0.10. It keeps the old services, even if Zope 3.0
already provides them.
- You move your application to Localizer 0.10, without modifying it.
It works because Localizer 0.10 is backawards compatible with the
0.9 version.
- The same for Localizer 0.11, 0.12, etc..
- Then I release Localizer 0.15, where the old services have been
removed. Don't worry, I only will do that when everybody has
moved to the new services.
This is how the policy works. And for it to work comminication is
important. If you use Localizer, please subscribe to the mailing list,
I ask people if they still are using some Localizer interface before
changing it.
Also, keep in mind that we also use Localizer for our own applications,
so we're the first ones interested in an smooth upgrade.
--
J. David Ib��ez, Nuxeo.com
Debian user (http://www.debian.org)
_______________________________________________
FreePM Support List
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freepm-discuss
