On 1/17/02 10:16 AM, "Chris Shenton" <[EMAIL PROTECTED]> wrote:
> John McNally <[EMAIL PROTECTED]> writes: > >> It is a great way to structure many applications. It does not work so >> well in a portal environment, though. > > Can you explain more? We're working on a proxy-like application which > is close enough in behavior to a portal that I'm concerned about > future directions. > > >>> 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. > > Can you explain what is meant by "valves"? I've seen them referenced > in the code, but nothing in the various HowTo's. That's because turbine3 is a work in progress and hasn't been released. > > Thanks. > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- 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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
