----- Original Message ----- From: "Jason van Zyl" <[EMAIL PROTECTED]> To: "Turbine Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, March 05, 2002 6:16 PM Subject: Re: small presentation and questions
> On Tue, 2002-03-05 at 20:11, Warner Onstine wrote: > > Hi all, > > I may be doing a presentation on Turbine 2 at a small Java Users Group here > > in Tucson and wanted to get some info on 3: > > If you ask some specific questions we can try to answer them. In short > the core will be very small and everything will be made up from discrete > components. I know that's but that's the short answer. We also have a > very flexible pipeline mechanism for displaying content. > > > What are the different subprojects and their functions? > > ie - fulcrum, maven, stratum are the ones I'm unclear on. > > Fulcurm: decouple services framework. > Stratum: reusable components made up from services and utility code in > turbine that is better suited in the form of a component. All of the > stratum code will either be culled in favour of commons components or > moved to the commons proper. I've been trying to pay attention to Maven, but am still unclear as to the overall purpose of it (I guess) or its fit within turbine. From what I can gather Maven is supposed to be some kind of code metrics system, this (I assume) will be moved into commons when ready. > > Is there a planned release for 3, yet? > > Still in the works. > > > Is there an anticipated release for 2.2? > > On the status report I said we are shooting for a beta in the next two > weeks (Martin, could you please update the site). The last remaining > issue is getting Fulcrum to work with Turbine 2.2. Cool, if Fulcrum is going to be in 2.2, what will be the big change in 3? > > Just something brief and why it was necessary to do it this way for > > decoupling services. > > I don't understand the question: are you asking why we decoupled the > services? We want the services framework to be generally useful. > Hopefully something that can go to the commons as well. Now, re-reading it, I'm not sure what I was asking =). I understand the need for de-coupling the services as there is a demand for being able to use the services independent of the framework. If a service is reliant on the database (ie - a particular table or schema), how will this need be met within the framework? How does reliance on one service from another get met in the new framework (another way of phrasing it)? > > Also, what decoupled services are going to be available > > for things like Struts (I will be presenting to a struts-heavy crowd). > > Anything that is currently in the fulcrum repository will be available > for use with any application. It is no longer dependent on Turbine at > all. Cool, is anyone working with Fulcrum and Struts right now, or looking into how these two will fit together? -warner > > Thank you all for your time and a truly great web framework, I learn more > > about it each time I want to build something. > > > > -warner > > > > +warner onstine+ > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- > jvz. > > Jason van Zyl > [EMAIL PROTECTED] > > http://tambora.zenplex.org > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
