RE: Are navigation classes in for the same fate as screen classes in Turbine-3

["Weaver, Scott" <Sw...@rippe.com>]

That's great news!  Your short explanation cleared up a lot Turbine-3 vs.
Turbine-2 of questions (for me anyways).

Thanks,
Scott

-----Original Message-----
From: Jason van Zyl [mailto:jvanzyl@zenplex.com]
Sent: Friday, January 11, 2002 12:52 AM
To: Turbine Users List
Subject: Re: Are navigation classes in for the same fate as screen
classes in Turbine-3


On 1/8/02 10:21 AM, "Weaver, Scott" <Sw...@rippe.com> wrote:

>> From what I gather, screen classes will not be used in Turbine-3.  Will
> navigation classes also go the way of the Dodo?
> 
> I think this is an important question as it will affect (at least myself,
> anyway ;) the way developers create there apps in 2.1 and 2.2.
> 
> My apologies if this has been asked before.

No problem. Turbine 3 at the core will have no knowledge of a screen,
navigation or layout but the model (the classic model) will still be a valid
usage pattern. Scarab is currently using Turbine 3 along with screens,
navigations and layouts. How you structure your view will be determined by
the collection of valves used. Turbine will be stripped down to a core
system upon which anything can be built. The classic model was the first
thing implemented and works so your screen, navigation and layout templates
can be used in Turbine
 
> Thanks,
> Scott
> 
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>

-- 

jvz.

Jason van Zyl

http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons



--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>