Re: G3 colors

by Bharat Mediratta :: Rate this Message:

Jens A. Tkotz wrote:

> Hi,
>
> the only benefit i see for splitting css files is "better" structure.
> The author says its easier to maintain for example three smaller file
> than one big file.
>
> I do not agree.
> For example lets say there is a color.css
> I have .gAdminbar {}
> I would have it in main.css AND in color.css
> So i have to switch between two files depending on what i am changing.
> If there will be "colorpacks" you would need to ship main.css,
> green_color.css and red_color.css
> So i don't see a simplification and the structure is not that better.

Chad and I discussed this a little bit. Really what we're talking about
here is how we structure the CSS in the default theme that Gallery ships
(right now in Gx, all the CSS is in the default theme). I am not
thrilled about it because when I get in there to modify CSS I always get
irritated by having to bounce between several files to figure out where
to put what. But I defer to Chad/Jakob/Jens on this.

> And another reason is, that the client has to do more HTTP requests.
> See http://developer.yahoo.com/performance/rules.html

I agree. IMO, we should use a css combiner like we do with JS files so
that we load all JS/CSS with a single request.

-Bharat

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
__[ g a l l e r y - d e v e l ]_________________________

[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]

« Return to Thread: Themeing G3