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. Thanks. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
