Re: Help with understanding the css for gnome shell, for the purpose of creating themes... ...

[dan <techno-mole ntlworld com>]

Hope I got this right, anyway thanks for the information, it doesn't 
matter if the colouring is hard coded in the js, it can be changed there 
rather than re-writing bits of code to allow editing in the css.

Many thanks.

Dan


gnome-shell-list-request gnome org wrote:
> Send gnome-shell-list mailing list submissions to
> 	gnome-shell-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mail.gnome.org/mailman/listinfo/gnome-shell-list
> or, via email, send a message with subject or body 'help' to
> 	gnome-shell-list-request gnome org
>
> You can reach the person managing the list at
> 	gnome-shell-list-owner gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gnome-shell-list digest..."
>
>
> Today's Topics:
>
>    1. Re: How to access 'Sytem' and 'preferences' (Owen Taylor)
>    2. Re: Use gjs_context_get_native_context() [solved]
>       (Michael Higgins)
>    3. Re: Use gjs_context_get_native_context() [solved] (Owen Taylor)
>    4. Two Problems, One Solution. (Apoorva Sharma)
>    5. Help with understanding the css for gnome shell, for the
>       purpose	of creating themes... ... (dan)
>    6. Re: Help with understanding the css for gnome shell, for the
>       purpose of creating themes... ... (Mads Villadsen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 24 Feb 2010 11:01:24 -0500
> From: Owen Taylor <otaylor redhat com>
> To: omer akram <om26er gmail com>
> Cc: gnome-shell-list gnome org
> Subject: Re: How to access 'Sytem' and 'preferences'
> Message-ID: <1267027284 10490 46 camel localhost localdomain>
> Content-Type: text/plain; charset="UTF-8"
>
> On Wed, 2010-02-24 at 10:29 +0500, omer akram wrote:
>   
> > gnome shell only shows applications in it. although system settings
> > apps can be searched in gnome shell but they dont apparently are
> > visible in any menu. are we gonna use gnome-control-center for all
> > type of settings and preferences? 
> >     
>
> Yes, the idea is to move away from having settings appear as
> 'applications'. The control center shell can be accessed from the user
> menu on the right of the panel, and should also appear as an application
> itself. (It doesn't currently - but that should be fixed.)
>
> (There is some work ongoing to redo the control center shell to embed
> the preferences within the window; not certain at this point if that
> will land for GNOME 3.0 or not - if not, we'd keep on using something
> like the current gnome-control-center.)
>
> - Owen
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 24 Feb 2010 11:31:58 -0800
> From: Michael Higgins <linux evolone org>
> To: gnome-shell-list gnome org
> Subject: Re: Use gjs_context_get_native_context() [solved]
> Message-ID: <20100224113158 3a5c61eb lappy evolone org>
> Content-Type: text/plain; charset=US-ASCII
>
> On Tue, 23 Feb 2010 22:36:24 -0800
> Michael Higgins <linux evolone org> wrote:
>
>   
> > On Tue, 23 Feb 2010 22:20:31 -0800
> > Michael Higgins <linux evolone org> wrote:
> >
> >     
> > [8<]
> >
> > Nevermind... Whatever it was seems to have resolved itself along the
> > way.
> >     
>
> When I reverted back to clutter-1.0.8, I believe.
>
>   
> > Sorry for the noise!
> >
> > Cheers,
> >
> >     
>
> Okay, more noise. I should probably go elsewhere, but...
>
> The problem, for me, begins (so it seems ATM) with updating to 
> clutter-1.1.12. Then mutter-2.29 fails to build because of a small
> handful deprecation warnings. (-Wall and -Werror were hard-coded at
> some point in the makefiles. Much better to see the warnings as
> warnings and have it build? Maybe.)
>
> Same handful of deprecation warnings and build failure on gnome-shell
> for the same reasons, but finally, this native context thing. I made a
> patch to reverse this commit so that I can still build gnome-shell.
> Oddly, it still works, but I see a little glitch here and there. ;-)
>
> The build fails with undefined error related to js_native_context, or
> something. My WAG is this is related to having older xulrunner libs
> than whoever committed these bits. I may at this point be too
> un-enamoured with this kind of fun and games to really find out, but if
> anyone happens to know.... ;-)
>
> Cheers,
>
>   


--
“ All of us are travelers lost,
our tickets arranged at a cost
unknown but beyond our means.

This odd itinerary of scenes
--enigmatic, strange, unreal--
leaves us unsure how to feel.
No post-mortem journey is rife
with more mystery than life. “