At 19:12 2000-11-30, David Sean Taylor wrote:
>I'd like to open it up to discussion:
>
>(1) There is only one Top and one Bottom navigation. How could the profiler
>support different navigations based on a specified resource? To get around
>this in my Jetspeed installation, Im considering only using the navigation
>to write the stylesheet and scripts, and then displaying the actual
>'navigation top' as a portlet.
>(Perhaps I don't fully understand the originally intentions of navigations.)
>
>(2) There is only one stylesheet. Im thinking about different stylesheets
>based on media type, and a fallback mechanism. This would mean adding an
>interface to the profiler service: getStyleSheet() instead of coming from
>the JR.P and Util class.
I don't know, if this stays an issue when we switch to proper templating.
With JSPs for example, you can specify the css individually for each jsp.
All you need then, is to have different templates for different
devices/mediatypes. I'm not sure, how stylesheets are used with velocity
templates.
ingo.
>Is anyone even interested in the profiler service supporting profiling of
>either navigations or stylesheets?
>
>
>
>
>
>--
>--------------------------------------------------------------
>Please read the FAQ! <http://java.apache.org/faq/>
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
>Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
