[Building Sakai] CLE Skins default and neo-defualt

[Steve Swinsburg]

Hi Mustansar,

Yes you can remove the other skins, they do not depend on each other. Just don't remove tool_base.css

For sakai.properties, to activate the neodefault skin (in trunk) you don't need anything in sakai.properties since it is the default, but you could have:
skin.default=default
skin.repo=/library/skin
Just like in earlier installs. You only really need properties if you need to override them or force it back to the old skin and layout.

I also note that we now have 17 different skins...
https://source.sakaiproject.org/svn/reference/trunk/library/src/webapp/skin/

cheers,
Steve


On 28/06/2012, at 4:16 AM, Mustansar Mehmood wrote:

> Thanks a lot for clarifying this to me. I hope part of the this conversation makes it into the skinning document for CLE as it gets released.
> I want to use "neo-default" and now I have a few questions for this case
> 1-Can we safely remove(delete) all other skins while using neo-default?
> 2-What would be recommended settings in sakai.properties file in addition to "skin.default=default"?
> On 06/27/2012 12:21 PM, Charles Hedrick wrote:
>> We have several special skins. Once we go to neo, the skins all have to be updated. It a site has a custom skin for which there isn't a neo version, the system doesn't fall back - it gives a pretty much unusable site.
>> 
>> On Jun 27, 2012, at 12:31 PM, Charles Severance <csev at umich.edu> wrote:
>> 
>>> Munstansar,
>>> 
>>> This is for a very specific purpose.   
>>> 
>>> Sakai 2.9 has a brand-new skin with new HTML markup that required significant changes to CSS, Velocity, Javascript and everything to support a lot of new portal features.  But for 2.9, I wanted to maintain the old skin as well for schools who had invested a lot in the old skin with local patches, etc.
>>> 
>>> So we made a copy of everything - velocity files, css, javascript, etc and left the 2.8 skin intact with no changes.  You can revert back to the 2.8 skin in 2.9 using this property
>>> 
>>> portal.templates=defaultskin
>>> 
>>> This is a transition strategy only and after 2.9, I intend to remove the old "defaultskin" and have only one skin (the neo skins) for 2.10.
>>> 
>>> This was a way for a school to go to 2.9 and not be forced to take the new portal layout / markup or to separate the moment where they installed the upgrade from the moment they changed all the skins.
>>> 
>>> If you like the new 2.9 skin - great use it - if you have too much invested in the old skin - switch it back for 2.9.  All your patches / skins should drop into the exact same place as 2.8 - that is why the new skin is in folders with "neo-" as prefix.
>>> 
>>> For 2.10, I want to "take off the training wheels" and go back to only having one skin (the neo skin).
>>> 
>>> /Chuck
>>> 
>>> 
>>> On Jun 27, 2012, at 11:47 AM, Mustansar Mehmood wrote:
>>> 
>>>> Hi,
>>>>     Among skins shipped with Sakai CLE 2.9.x there are two skins "defualt" and "neo-default". I am wondering if the are the completely separate skins or they have some relation with each other. 
>>>> The reason I am asking this question is that I changed the "neo-default" skin without any change in sakai.properties file which was set to use default skin, and the instance picked up the "neo-default" skin.
>>>> Regards,
>>>> Mustansar
>>>>  -- 
>>>> Mustansar Mehmood
>>>> Educational System Developer& Integrator
>>>> 
>>>> Information Technology  
>>>> 6100 Main St. MS 119
>>>> Houston Texas 77005
>>>> 
>>>> Phone:(713)348-2523
>>>> Fax  :(713)348 6099 
>>>> email:mustansar at rice.edu
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> I have yet to see any problem, however complicated, which, when,you  looked at it in the right way, did not become still more complicated. 
>>>>     -- Poul Anderson 
>>>> 
>>>> _______________________________________________
>>>> 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"
>> 
>> 
>> 
>> _______________________________________________
>> 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"
> 
> 
> -- 
> Mustansar Mehmood
> Educational System Developer& Integrator
> 
> Information Technology  
> 6100 Main St. MS 119
> Houston Texas 77005
> 
> Phone:(713)348-2523
> Fax  :(713)348 6099 
> email:mustansar at rice.edu
> 
> 
> 
> 
> 
> I have yet to see any problem, however complicated, which, when,you  looked at it in the right way, did not become still more complicated. 
>     -- Poul Anderson 
> 
> _______________________________________________
> 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"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20120628/4cc006bd/attachment.html