Modifying OcUK
- Thread starter robmiller
- Start date
SpankLikeThis said:ok coolwill the final have the css in it too so i dont have to edit any files?
Yep but probably just in a lazy way - ie, you type in a bunch of hex values yourself, no kind of colour-picker or anything.
Well most of the things you can hack around. Take finding the thread's ID, for instance; it's not always in the URL, so I use this code:
to get it out of the search form's hidden input. It's mainly stuff like that, hacking around the problems you find. Most of it's pretty straightforward though.
As for the language, all Firefox extensions are coded in Javascript and XUL. This is the biggest thing I've ever written in pure JS but I've been pretty comfortable with it for a while. It's just getting used to the things that are different between writing JS for content and JS for XUL and content.
Code:
ocuk.threadId = selectSingleNode(doc, doc, "//input[@type = 'hidden' and @name = 'searchthreadid']").value;to get it out of the search form's hidden input. It's mainly stuff like that, hacking around the problems you find. Most of it's pretty straightforward though.
As for the language, all Firefox extensions are coded in Javascript and XUL. This is the biggest thing I've ever written in pure JS but I've been pretty comfortable with it for a while. It's just getting used to the things that are different between writing JS for content and JS for XUL and content.
Last edited:
SpankLikeThis said:ok cool
I've changed my mind: probably not. After coding it, it's too annoying to see the flash of default colours before the stylesheet is applied.
Bump because I created an SVN repository for the extension and I'm going to start working on it again now that I have more time
Just source. Run build.bat to build the XPI as well as a directory that you can use with Firefox's dynamic extension loading. To dynamically load the extension, create a text file called
in your profile/extensions directory, which should look be:
In it, simply put the full path to the build directory that the build script generates (in my case, C:\firefox\ocuk\build). When you start Firefox, it'll load the extension; simply restart Firefox whenever you update your source from the repository.
Code:
svn co http://svn.robm.me.uk/ocukbb/trunk/Just source. Run build.bat to build the XPI as well as a directory that you can use with Firefox's dynamic extension loading. To dynamically load the extension, create a text file called
Code:
in your profile/extensions directory, which should look be:
Code:
%appdata%\Mozilla\Firefox\Profiles\[b]some string of letters[/b]\extensionsIn it, simply put the full path to the build directory that the build script generates (in my case, C:\firefox\ocuk\build). When you start Firefox, it'll load the extension; simply restart Firefox whenever you update your source from the repository.
Nah it's fine
Here you go:
Here you go:
Code:
@-moz-document domain(forums.overclockers.co.uk) {
/*
** OcUK colour scheme changer
** By Rob Miller
*/
* { color:#000 !important; }
textarea, input { background:#ddd !important; }
body, .page, .thead, .tfoot, .alt2, .alt2Active, .panel { background-color: #fff !important; }
.alt1, .alt1Active, .panelsurround, .vbmenu_option { background-color: #fff !important; }
.alt2 { background:#dfdfdf !important; }
.vbmenu_control, .vbmenu_control *, .vbmenu_hilite, .vbmenu_hilite *, .tcat, .tcat * { background-color: #006598 !important; color:#fff !important; }
.vbmenu_popup { border: 1px solid #ccc !important; }
}Dunno how Opera's custom CSS works, but you'd just find out how to load a custom stylesheet and put this code in it:
Not sure if it lets you limit the CSS to certain domains or what-have-you.
Edit: It tells you how to do site-specific user CSS here:
http://operawiki.info/OperaUserCSS
Code:
/*
** OcUK colour scheme changer
** By Rob Miller
*/
* { color:#000 !important; }
textarea, input { background:#ddd !important; }
body, .page, .thead, .tfoot, .alt2, .alt2Active, .panel { background-color: #fff !important; }
.alt1, .alt1Active, .panelsurround, .vbmenu_option { background-color: #fff !important; }
.alt2 { background:#dfdfdf !important; }
.vbmenu_control, .vbmenu_control *, .vbmenu_hilite, .vbmenu_hilite *, .tcat, .tcat * { background-color: #006598 !important; color:#fff !important; }
.vbmenu_popup { border: 1px solid #ccc !important; }Not sure if it lets you limit the CSS to certain domains or what-have-you.
Edit: It tells you how to do site-specific user CSS here:
http://operawiki.info/OperaUserCSS