David,
Please don't add any "getTopicBarFor<MediaType>" methods. They restrict the
implementation to those media-types that have abstract methods in the code.
There is enough "isHTML" and "isWML" in the code already...
Cheers,
Thomas Boehme
----- Original Message -----
From: "David Sean Taylor" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Monday, December 04, 2000 7:11 PM
Subject: RE: [profiler] navigations, stylesheets(css)
>
> Santiago Gala wrote:
> >
> >
> >
> > 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.
> > >
> > > Is anyone even interested in the profiler service supporting
> > profiling of
> > > either navigations or stylesheets?
> > >
> >
> > We had a discussion on that (in business terms). While from the
> > pure technical
> > point of view it could make sense that a user can customise the
> > whole page, from
> > a business point of view it could be dangerous:
> >
> > - The company making the portal can loose completely the corporate image
> > - Custom Navigations can loose/hide important links
> > - Thinks that are part of the business model (for instance ads,
> > or links to
> > other content) can be taken out by the user
> >
>
> >From my experience as an end user of portals like my yahoo maybe thats
not
> such a bad thing. I could remove the adverts :)
>
> Seriously, I agree the end user should not be capable of configuring (or
> removing) the standard navigations.
> I was considering how to better enable the site administrator/developer to
> configure the navigations and stylesheets per resource without having to
> write their own navigations.
>
> After looking into this, the only change Im now considering for the
> TopNavigation is to look at the CapabilityMap and decide which navigation
> content to display. In doBuild() of the TopNavigation, it would call a
> getTopicBarFor<MediaType>() for the basic media types. So this change is
> only for the default Jetspeed implementation. For others needing different
> behavior, they can implement their own navigations.
>
> The profiler could also be used to locate a stylesheet based on the
> capability map or profile information.
> I think there is a good case for having a different stylesheet based on
> media type, but less so on other profile information.
>
> We have a requirement for the navigation content (images, text) to depend
on
> the 'group' of a user.
> I am writing my own navigation implementation.
>
> > They (the business people) came with the idea that a user could
customise
> > content, and choose or even write skins (themes related with
> > turbine layouts,
> > stylesheets and XSLT transformations), but the navigations or the global
> > structure of the page would be fixed, except where the theme
> > repositions or
> > changes things.
> >
> > What is funny about the thing is that the demos we are doing are
> > using the skin
> > mechanism to switch Jetspeed to look completely similar to
> > different commercial
> > portals just by changing a user option. Thus, our maximum
> > strength, that is that
> > Jetspeed is somehow chameleonic in terms of layout, is dangerous
> > in the sense
> > that a portal can loose completely any community identity in the
process.
> >
> > So, I think that having the profiler know about skins,themes,
> > stylesheets or
> > however we name it is interesting. Nevertheless, there should be
> > either security
> > or other constraints on how the user can customise this part of
> > the system.
> >
>
> > We have discussed about having the page structure out of the
> > turbine navigation
> > mechanism and inside the PSML, but there were disagreements,
> > partly due to the
> > things I said before. I don't think it will happen in next
> > releases. Navigations
> > are an important part of any portal, being the part that has the
> > "institutional"
> > part of a customised page.
> >
>
> Thanks, that was some great first-hand experience and insight.
> I don't have as much experience as you in portal development. Its very
> valuable to learn from your experiences.
>
> David
> > >
> > > --
> > > --------------------------------------------------------------
> > > 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]
> >
> >
>
>
>
> --
> --------------------------------------------------------------
> 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]
