on 2/9/00 6:23 PM, Kevin A. Burton <[EMAIL PROTECTED]> wrote:
> Good point. What about /topnavigation or /bottomnavigation? This would
> also allow /leftnavigation and /rightnavigation which will someday be
> needed.
That is what you would define in your Layout.
> This is necessary with what I am doing right now with JetSpeed. For
> Avantgo syncronization I need to give it a URL with very raw content
> (now GIFs, HTML 3.2 etc). Therefore I want to null out my navigation
> (/topnavigation/JetSpeedNoNavigation) so that there is as little content
> as possible.
ok.
> Granted I could do this with my own Layout.... But it would be more
> open if I could just call RunData.getTopNavigation(), etc and then
> provide a default if it is null or the user specified one if it != null.
You are still missing the point. That is not how you should access the
navigation stuff. You simply get a Layout which has defined which
Navigations to include.
Allowing people to access the Navigations directly like that is a bad design
idea. Let me remind you of this image:
<http://java.apache.org/turbine/images/ModuleObjectLayout.gif>
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
