Hi Nathan, 2010/2/20 Nathan Pitman <[email protected]>: > I read that Firebug Lite themes can be created, I'd love to contribute > a Theme for Chrome on the Mac but would love some pointers on where to > start... :)
First of all, thanks for willing to contribute. This is something I was thinking for a long time, and is something that Mac users will love, I'm sure! We may also consider using this new Mac theme as the default theme for the Mac platform, once Firebug for Firefox has different themes for those platforms. To get started, read the section "d) Development mode" under Install instructions: http://getfirebug.com/releases/lite/beta/#Install When you run the "build" version of Firebug Lite (single .js file) you won't load the HTML / CSS files used in the UI. Otherwise, the application will be loaded with a "injected" version of these files (for cross-domain and performance reasons). The injected file can be found at "content/firebug/chrome.injected2.js". Therefore, you'll need to run the application in "development mode", so you can work with the HTML and CSS as separated files. Once in development mode, you can tweak the CSS file and see the changes without having to "build" the application every change you made. Before downloading the Firebug Lite code, I suggest you download the Firebug for Firefox's theme code, and look how Firebug manages the two different styles: http://fbug.googlecode.com/svn/branches/firebug1.6/skin/classic/ You will see a "mac" and "win" directories with different CSS files for each platform: http://fbug.googlecode.com/svn/branches/firebug1.6/skin/classic/mac/ http://fbug.googlecode.com/svn/branches/firebug1.6/skin/classic/win/ After that, download the Firebug Lite code: http://fbug.googlecode.com/svn/lite/branches/firebug1.3/ Please note that currently Firebug Lite is using only 1 giant CSS file, instead of several CSS files as Firebug. I'm not satisfied with this, because it makes the file harder to maintain, and it makes customizations (like the one you're willing to do) more difficult. I'm planning to change this soon (use separated CSS files, and implement a better mechanism to change themes), so in the meantime I suggest you create a single new CSS file (like mac.css for instance), and override the styles you need to change. This will make it easier to maintain the new theme for Mac when the changes in the theme files structure happens. If you have any other doubts I'll be glad to give you instructions. regards, Pedro Simonetti. > > -- > You received this message because you are subscribed to the Google Groups > "Firebug" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/firebug?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
