Santiago,
You are absolutely right with regard to the business issues at stake, at
least from my/our point of view. But I disagree concerning the technical
correlation. Your approach to apply a skin is different from the "customize
everything" scenario. The latter might potentially allow users to
disable/remove things (like logos, ads, etc.) that the portal provider
wishes or is legaly obliged to keep on the page. Applying a skin (the way
you did it) is different because the portal provider creates and provides
the skins. The user can just choose from a finite set of options. Therefore,
as long the portal provider carefully controls the skins, there is no way
for the user to bypass anything.
Like you, I would be very reluctant to agree to a "customize everything"
customizer, as powerful as it might be...
Cheers,
Thomas Boehme
----- Original Message -----
From: "Santiago Gala" <[EMAIL PROTECTED]>
To: "JetSpeed" <[EMAIL PROTECTED]>
Sent: Friday, December 01, 2000 11:16 AM
Subject: Re: [profiler] navigations, stylesheets(css)
>
>
> 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
>
> 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.
>
> >
> > --
> > --------------------------------------------------------------
> > 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]
