[Building Sakai] Portal NEO Prefix

[Steve Swinsburg]

Agreed. Remove the prefix to reduce confusion and make whatever is set as the skin be the one to use without prefixing. I've also had this problem and its a pain. 

Cheers
Steve


Sent from my iPhone

On 16/03/2013, at 9:13, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> Getting rid of the prefix seems like the right move to me.
> We would need to let anyone running 2.9 know that the path was
> shifting back to the more typical one but it will avoid confusion in
> the next release so I think it is better to just endure the pain now.
> 
> -AZ
> 
> 
> On Fri, Mar 15, 2013 at 6:08 PM, Sam Ottenhoff <ottenhoff at longsight.com> wrote:
>> Yeah, I think neo has proved itself as our look-and-feel future.  I'm
>> generally looking here to get rid of this prefix if possible so we don't
>> need to update tools like STAT-345...
>> 
>> --Sam
>> 
>> 
>> On Fri, Mar 15, 2013 at 3:41 PM, David Adams <da1 at vt.edu> wrote:
>>> 
>>> I was just looking at this earlier this week. There's also a new
>>> property "portal.templates" that specifies what VM templates to use
>>> when rendering the HTML. Hardcoded into the portal logic, it checks to
>>> see if portal.templates is "neoskin" and if it is, it ensures that the
>>> skin name (property skin.default) is prefixed with the value of
>>> property portal.neoprefix.
>>> 
>>> I assume the reasoning behind it was to make sure you don't
>>> accidentally specify a non-"neo" skin. But in practice it's turned out
>>> to make things much more confusing. In our case, our developers
>>> updated the "default" skin directory with their new neoportal CSS,
>>> thinking that since skin.default was set to "default" that meant (as
>>> it has up through 2.8) that the skin directory would be named
>>> "default". But nope, it was "neo-default" that was actually getting
>>> served.
>>> 
>>> Doh.
>>> 
>>> -dave
>>> 
>>> 
>>> Sam Ottenhoff wrote:
>>>> Can someone explain the need for the 2.9+ property called
>>>> portal.neoprefix with a default value of "neo-"?  I understand that it means
>>>> your "default" skin now becomes "neo-default", but why was it needed?
>>>> 
>>>> We are starting to see some requests like this one:
>>>> 
>>>>  https://jira.sakaiproject.org/browse/STAT-345
>>>> 
>>>> The tools include a link to the tool.css file, but it's not the one they
>>>> expect because the tool has no idea about this neoprefix.
>>>> 
>>>> So, is neoprefix necessary?  Do we need to patch the tools to make them
>>>> neo-aware?
>>>> 
>>>> Thanks,
>>>> Sam
>>>> _______________________________________________
>>>> sakai-dev mailing list
>>>> sakai-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>> 
>>>> TO UNSUBSCRIBE: send email to
>>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>>> "unsubscribe"
>> 
>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org
>> with a subject of "unsubscribe"
> 
> 
> 
> -- 
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"