[Building Sakai] Portal NEO Prefix

[Charles Severance]

Dave - Changing the meaning of the default skin in the behavior in the portal now that 2.9 is almost a year old will also cause confusion and breakage.

There is a simple fix that follows the original specification of Sakai 2.0.

We can communicate better - but breaking the architecture of the portal and its ability to have multiple simultaneous skins in order to avoid fixing tools in 4-5 places that happen to have worked since 2.5 is the wrong approach.

I don't understand how if enough people vote that wrong becomes right.  Lets just take this opportunity to get things right.

/Chuck

On Mar 17, 2013, at 7:39 PM, Adams, David wrote:

> I agree 100% with Steve here.
> 
> Breaking the longstanding behavior of a property is a bug. I'm not worried about the tools here, but even if all the tools worked correctly, the way this setting works currently is confusing and already causing problems as deployers who didn't write the portal code don't know which skin directory to update. So long as this remains this will continue to crop up as a problem.
> 
> I'm sure there are ways to keep the tools broken without confusing users if that is the goal.
> 
> -dave

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130318/7aaa16ff/attachment.html