Thomas Boehme wrote:
>
> 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...
>
I agree as well that "customize everything" is not a desirable property for
the general product so I propose that we don't implement this in the
default profiler implementation.
If a site requires this kind of flexibility, it should be easy to subclass
the Profile interface, write a new Profiler to handle the stylesheet
selection and write Navigation/Layout classes tied to this specific
subclass of Profile.
--
Rapha�l Luta - [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]
