[horde] Color Schemes

[Michael M Slusarz]

Working my way through my mailboxes...

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Michael M Slusarz <slusarz at horde.org>:
>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>> Zitat von André Schild <a.schild at aarboard.ch>:
>>>
>>>>>> Hi everybody,
>>>>>>
>>>>>> Is there a website to download different color schemes for  
>>>>>> horde 5.1/5.2?
>>>>>> Some users ask for that.
>>>>>> I know that is possible to duplicate the default theme and create one,
>>>>>> but developers do make a better job on that.
>>>>>>
>>>>>
>>>>> Take a look at the mailing lists (13-02-2014 and 24-01-2014),  
>>>>> there are some
>>>>> themes discussion and shares.
>>>>
>>>> [Andre Schild]
>>>> Have there been any ideas about using SASS for theme building?
>>>> This would allow us to change colors in a simpler way.
>>>>
>>>> André
>>>
>>> Yes, but as with many ideas, we lack time/funding to really get to this.
>>
>> Actually, it shouldn't be that difficult to add this functionality  
>> ... now that we have the CssMinify library.  A SASS library could  
>> be implemented as a driver.
>>
>> The bigger issues are instead:
>>
>> 1.) Deciding on the preprocessor to use.  We would need to decide  
>> on a single solution, since trying to maintain multiple solutions  
>> would be difficult.  I know of LESS also, but IIRC SASS is sort of  
>> the best-in-class solution.
>>
>> 2.) Configuration/performance issues.  If we decide to use SASS, I  
>> assume we would have to parse every file with it - trying to create  
>> a system where only certain files are parsed would be way too  
>> unwieldy.  The problem with this becomes that we pretty much  
>> require static compilation of CSS for performance reasons.  Since  
>> we don't require this now, and this requires extra legwork at  
>> installation time above/beyond PEAR install, this is a major  
>> decision to make for the project.
>
> I didn't assume we would built CSS during run-time or  
> deployment-time, but really during development. We would distribute  
> both LESS/SASS and CSS to Git already.

The problem still comes if the *admin* wants to use LESS/SASS on their  
system.  Without adding additional SASS configuration options, I don't  
see an easy way to automate this.

I still am intrigued by this.  (Just for inheritance aspect of SASS.   
That alone is worth the price of admission.)

michael

___________________________________
Michael Slusarz [slusarz at horde.org]