Stephane Bailliez <[EMAIL PROTECTED]> writes:
> > -----Original Message-----
> > From: Daniel Rall [mailto:[EMAIL PROTECTED]]
>
> > Lack of fluffy documentation has been an issue since I started using
> > Turbine a year and a half ago. Use of the API and source code is a
> > reasonable substitute, but doesn't do much to lower the learning
> > curve. The spin-off of Fulcrum and Torque in Turbine 3.0 has helped
> > with that quite a bit.
>
> Ergh, I'm a little bit scared for 3.0, considering what I see in the code,
> it really is a *major* change.
Definitely--that why it's a major version point increment. While the
2.x series is a stable version of Turbine's great code base, 3.0 will
provide a super clean, rock solid API which will survive many future
major point bumps.
> If I start using Turbine 2.1 for my app, I'm afraid I will have to use 3.0
> in some points because all the developpement now relies in 3.0 and it does
> not look like it will be that fast to migrate from 2.1 to 3.0.
I migrated Helm and another Tigris component by hand. Jon and John
did the same for Scarab. Jason will be providing tools to aid in
migration for those not interested in performing the surgery by hand.
> I looked at how localization is done in 3.0...and the localization service
> is gone. From what I can see in the readme.txt the plan is to merge most of
> it in the MimeType service right ?
The LocalizationService is certainly not gone. It has been moved into
Fulcrum (see
jakarta-turbine-fulcrum/src/services/java/org/apache/fulcrum/localization/),
which is where the services code now lives (allowing it to be more
easily be used stand-alone). Jon has recently done a bunch of clean
up on it.
Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
