on 1/21/00 7:10 PM, Jonas Maurus <[EMAIL PROTECTED]> wrote:
> -1 on that (that is, if my vote counts :-) ). Turbine has zero l10n features
> by
> now, so you probably would just create confusion with that, don't you think ?
The reason that Turbine doesn't have that feature is because no one has
implemented it yet.
> Basically I'm not in favor of exporting anything from Jyve, because currently
> there is one LocalizationManager local to Jyve which handles all Jyve-specific
> stuff, with Jyve-specific resources. Exporting it to turbine would in fact
> break
> localization in Jyve as a "standalone product". I almost dare to say that it
> would be one more unnecessary connection between these two packages.
Excuse me, but Jyve and Turbine are extremely tightly integrated, ON
PURPOSE. I believe strongly in Turbine and the Turbine model, hell, I wrote
a good portion of it. There is no "unnecessary connection" between the two
because they are supposed to be tightly integrated with each other. I really
don't see this as a negative thing.
> Now, if you should go for the turbine-package and remove LocalizationManager
> from Jyve, it would be quite nice to have a short feature-freeze period with
> turbine, simply because as you probably know, too, Turbine does not build at
> the
> moment, moving in another package into the currently unstable source tree is
> probably not the best idea and you guys should get rid of the Collection.class
> mismatch between 1.1 and 1.2 anyway.
The collection mismatch has already been dealt with. Turbine builds just
fine. Also, just because a single portion of it doesn't build doesn't mean
that there are going to be issues with the rest of Turbine as a result.
As for feature freeze, Turbine isn't there yet. It will be in about 1-2
months probably. The reason is that we are adding developers on a daily
basis. I don't want to stunt that growth right now in any way.
> I would really like to discuss these issues over the week-end, because this
> would enable me to work on this on sunday or at least early next week.
I will be checking email, but I'm pretty strongly for adding localization
features to Turbine in a generic manner so that there can be maximum
code-reuse. When you decided to work on Jyve, by nature and association, you
also signed up to work on Turbine. I thought that I made this pretty clear
by expressing that you should also understand how Turbine works as well.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
