Forum OpenACS Development: Re: Master explanation

Collapse
8: Re: Master explanation (response to 1)
Posted by Dave Bauer on
Malte

I'd like to be a little more clever about it.

The reason for multiple files is to keep the CSS in the right place.

The trick would be to compile a master css from the appropriate files when necessary.

It would be easy to do this once Lee's work on template::head is complete. Hamilton is looking at completing this work.

The advantage is that you still get modularity and the system can consistently manage the files for you.

I think allowing editing of CSS files from the web interface is really a seperate feature from this since the end result is a file in the filesystem the rest of the features only need to know the location of the file and it should not matter where it came from. I'd also think most designers would rather upload a complete file than edit it in a web browser.

Collapse
9: Re: Master explanation (response to 8)
Posted by Malte Sussdorff on
Sorry, when I say "include" i meant really include with a reference, not physically copying all content there. Obviously we should keep the files separate. No need to compile the master.css in my opinion, CSS after all is smart in including other files and it gives you much leeway with the Webdeveloper edit function.