[dev] potential optimizations: static css and javascript

[Jan Schneider]

Zitat von Jan Schneider <jan at horde.org>:

> Zitat von Chuck Hagenbuch <chuck at horde.org>:
>
>> I was thinking this evening that it might be time to give up on the html.php
>> theme files and css.php processor script - it's probably just a barrier to
>> theme designers to not have straight .css files, and as far as I can 
>> tell, we
>> don't really use the ability to override things programattically all 
>> that much
>> anyway. Browser checks can be done other ways, etc. And it'd allow 
>> for better
>> caching, etc. The idea would be to leave the theme config files in
>> config/themes for things like graphics and whatnot, and to add a 
>> css/ directory
>> (name/location negotiable) to each app that'd hold top-level css files
>> (screen.css, print.css, etc.) with a themes/ directory for theme-specific
>> versions of those. We'd include two stylesheets (horde and app) 
>> explicitly in
>> apps that added their own css, but that's not a problem that I can see.
>
> While I like this idea generally, I see some problems that are not easy to
> circumvent with static CSS files, namely style sheets that use images,
> like:
>
> $css['body']['background-image'] = "url('" . $registry->getParam('graphics',
> 'horde') . "/themes/kolab/bg.png')";
>
> I can't really imagine dropping this design feature. Uh, wait, isn't the url
> relative to the CSS file?

Thinking a bit slow today. Yes, these paths are relative, but the "graphics"
directory is configurable. Perhaps we could live with this inconsistency,
requiring administrators to change CSS files if they want a different
graphics path.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/