Re: dev-planning Digest, Vol 43, Issue 9

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: dev-planning Digest, Vol 43, Issue 9

cecilca

Juan cesar martinez
----- Original Message -----
From: <[hidden email]>
To: <[hidden email]>
Sent: Sunday, July 12, 2009 8:00 PM
Subject: dev-planning Digest, Vol 43, Issue 9


> Send dev-planning mailing list submissions to
> [hidden email]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.mozilla.org/listinfo/dev-planning
> or, via email, send a message with subject or body 'help' to
> [hidden email]
>
> You can reach the person managing the list at
> [hidden email]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dev-planning digest..."
>
>
> Today's Topics:
>
>   1. Re: Starting to think about Firefox.next - light weight
>      themes .. old-style themes (bird)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 11 Jul 2009 20:25:38 -0700 (PDT)
> From: bird <[hidden email]>
> To: [hidden email]
> Subject: Re: Starting to think about Firefox.next - light weight
> themes .. old-style themes
> Message-ID:
> <[hidden email]>
> Content-Type: text/plain; charset=ISO-8859-1
>
> At the meantime, I've written an article about the UI where I describe
> the above method:
> http://www.tudobom.de/articles/yatt/#light_weight
>
> The method works, but it's still too limited because it makes only
> possible to override the browser window's styles and has no control of
> global widgets. It means if I want to modify, e.g., the appearance
> from buttons, I have to declare a style overlay for each window where
> buttons appear... Impossible. It could be a lot better if I can
> determine styles globally for the widgets.
>
> A solution could be what Dave proposed, enabling the override
> instruction for themes. For me it makes more sense the override
> instruction for themes as for extensions, if is guaranteed that these
> overrides will only take effect if the theme using them is the
> actually used theme.
>
> Another approach could be an @import in content/xul.css (@import url
> ("chrome://customskin/skin/customskin.css");, for example) that would
> make possible to override styles for the XUL elements. But all themes
> using this approach will obligatory have to register a "customskin"
> package...
>
> As I said before, I think it's important, is to provide the two ways
> for make themes. A "light-weight", override approach for simple themes
> and the "heavy-weight", substitute approach for more complex themes.
>
>
>
> ------------------------------
>
> _______________________________________________
> dev-planning mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-planning
>
>
> End of dev-planning Digest, Vol 43, Issue 9
> *******************************************
---------------------------------------
    Red Telematica de Salud - Cuba
     CNICM - Infomed

_______________________________________________
dev-planning mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-planning