incubator-adffaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Winer" <awi...@gmail.com>
Subject Re: Split up the CSS across multiple files
Date Fri, 16 Feb 2007 00:31:01 GMT
On 2/14/07, Chris Eidhof <eidhof.chris@oracle.com> wrote:
> Hey everyone,
>
> I really don't like very long files, and especially the long css-files.
> So I was wondering: why don't we split up the css-file into multiple
> files: one components-shared.css, and one file for each component. I
> think that this will create more overview, and it separates things a bit
> more. Also, I'm working on a project with a really large skin, so
> there's a lot of other issues with editing such a file (my scrollbar
> moves a lot of lines per pixel, I can't really browse anymore but have
> to search a lot, etc.). Mostly minor things, but it's still annoying.
>
> Furthermore, the project I'm working on has multiple skin-files, and I
> think it would be much more convenient to have my rules grouped by
> component instead of per skin. This is a related, but different feature.
>
> So the features I'm proposing:
> * Support @import for including other stylesheets

+1.

> * Separate large stylesheets into component-specific stylesheets

No reason not to, once we have @import.

> * Be able to define rules for multiple skins in one file (I guess we
> need to extend the syntax for that).

Eh, -1 I think...  this seems contrary to the idea of having
smaller files.  I'm not sure the benefit is worth the extra
syntax and code.

-- Adam

Mime
View raw message