Re: G3 colors

> Hi Chad,
>
> I'm pretty much +/- 0 on most of these discussions. Whatever you guys choose
> will be fine. I'm certainly *not* going to waste time caring how the curly
> brackets are arranged, how many tabs are used for indentation, or what style
> of capitalisation is used for variable names. I'll leave that to the real
> programmers ;-)
>
> -Alec
>
>
>
> ----- Original Message -----
> From: "Chad Kieffer" <chad@...>
> To: "Alec Myers" <alec@...>
> Cc: <gallery-devel@...>
> Sent: Monday, October 27, 2008 5:08 PM
> Subject: Re: [Gallery-devel] G3 colors
>
>
> Hi Alec,
>
> We discussed the multiple CSS file approach during the code sprint.
> Jens brings up good points that I agree with. Although G3 may likely
> provide css file compression to collect separate css files for
> combination, this would add an extra level of complexity.
>
> I think it's best for now if we stick with a single css file per media
> type and  promote a standard grouping of CSS definitions in that file.
> We can use comments to identify and explain each group in the file.
>
> I don't see how a single file approach would hinder or complicate
> theme or module driven color changes.
>
> - Chad
>
> On Oct 27, 2008, at 10:08 AM, "Alec Myers" <alec@...> wrote:
>
>> On the basis of that page, here's a wacky idea: noticing that the
>> slowest
>> part of loading a new gallery page is downloading (in my case) 48
>> individiual thumbnails why not have gallery pre-build and cache the
>> thumbnails for each page as a single jpg (sprite-like) and repeat it
>> to show
>> the individual images?
>>
>> ----- Original Message -----
>> From: "Jens A. Tkotz" <jens@...>
>> To: <gallery-devel@...>
>> Sent: Monday, October 27, 2008 3:13 PM
>> Subject: Re: [Gallery-devel] G3 colors
>>
>>
>> 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.
>>
>>
>> And another reason is, that the client has to do more HTTP requests.
>> See http://developer.yahoo.com/performance/rules.html
>>
>> - Jens
>>
>>
>>
>> Quoting Brandon Sussman <Brandon@...>:
>>
>>> On Monday 27 October 2008 00:48:03 Chad Kieffer wrote:
>>>> We'll probably opt to document how to clone a theme and alter
>>>> it's color via CSS.
>>> I imagine many folks feel that color adjustment is very important to
>>> individualization but...
>>>
>>> In ALA's latest article (
>>> http://www.alistapart.com/articles/progressiveenhancementwithcss ),
>>> Aaron
>>> Gustafson discusses separation of css into functional units ( e.g.
>>> type.css,
>>> layout.css, color.css).  I think this makes good structural sense.
>>>
>>> Seems to me this is fine to begin with.  If the correct hooks and
>>> loops
>>> are
>>> there,  making manipulations available in a GUI can be accomplished
>>> if
>>> that
>>> ever bubbles to the top of the to-do list (which is probably already
>>> several
>>> volumes long in some folks minds :)
>>>
>>> --
>>> -----------------------------------------------------------------
>>> | WRWeb Services                   |           http://WRWeb.net |
>>> | 1482 Pleasant St.                |              (603)648-2251 |
>>> | Webster, NH, 03303-7613          |            19TBJ8040800540 |
>>> -----------------------------------------------------------------
>>> | Web Sites Designed and Supported |Think Locally, Buy Locally! |
>>> -----------------------------------------------------------------
>>>
>>> ---
>>> ---
>>> -------------------------------------------------------------------
>>> 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 ]
>>>
>>
>>
>> --
>>
>> Ich sag mal .... Charisma
>>
>> ---
>> ----------------------------------------------------------------------
>> 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 ]
>>
>>
>>
>> ---
>> ----------------------------------------------------------------------
>> 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 ]
>
>
>
> -------------------------------------------------------------------------
> 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 ]