Home page is in the wiki now. Or stay here for developper's corner.

See also the project's thread in opera forums.

There are two kinds of custom styles:

• .style files add rules on top of the current stylesheet
• .css files replace the whole stylesheet.

.css are best avoided unless absolutely necessary: .styles are smaller, easier to maintain, can be combined with others and are less likely to break when something changes.

The style editor makes it easy to try changes without having to clear and reload style each time. #swdev url hash makes it show up in options.

For toolbar button styling it'll look for a data: url on these selectors (highest priority first)

#toolbar_button.block_all img  { background-image:url('data:...') }
#main_button.block_all img     { background-image:url('data:...') }
.block_all img                 { background-image:url('data:...') }

same for .filtered, .relaxed and .allow_all, plus a special .disabled for the disabled icon. it doesn't do multi-line matching so it must all be on the same line, and the image should be 18x18 or strange things will happen.

With 1.5.2 autoscrolling is available: if the menu doesn't fit on the screen js can set max-height automatically for the host table and the details menu content to make use of the space available. It only kicks in if it finds overflow-y is set but not max-height.

With a copy of the repo it's possible to work with image files directly, it handles generating data: urls behind the scene. Useful if you're dealing with images a lot.

• Get a fresh copy of the repository (see Hacking below)

• Add your style patch rules at the end of src/scriptweeder.css (don't change anything else ! If you want to change a rule, copy it first).

• Add extra images to img directory and reference them with url('../img/whacky_image.png'). To set width and height automatically, add a /*img_size*/ comment.

• To test changes, just type make and try the generated scriptweeder.js.

  Right now you're actually changing the default style, so either use rescue mode or make sure you reset custom styles with Options->Back to default.

• Type make custom.style once you're happy with the changes.

  Style file is ready in custom.style !

Creating a completely new stylesheet is just as easy: just replace the whole .css and type make. The generated stylesheet is in src/scriptweeder.inlined.css.

For example the source for glowballs looks like this using the repo method:

/* mode icons (small) */
.block_all img         { /*img_size*/ background-image:url('../img/block_all_16.png'); }
.filtered  img         { /*img_size*/ background-image:url('../img/filtered_16.png');  }
.relaxed   img         { /*img_size*/ background-image:url('../img/relaxed_16.png');  }
.allow_all img         { /*img_size*/ background-image:url('../img/allow_all_16.png'); }
.menu .block_all img, .menu .filtered  img, 
.menu .relaxed   img, .menu .allow_all img     { margin: 3px }

/* mode icons (fat) */
.fat_icons .block_all img              { /*img_size*/ background-image:url('../img/block_all.png'); }
.fat_icons .filtered  img              { /*img_size*/ background-image:url('../img/filtered.png');  }
.fat_icons .relaxed   img              { /*img_size*/ background-image:url('../img/relaxed.png');  }
.fat_icons .allow_all img              { /*img_size*/ background-image:url('../img/allow_all.png'); }
.fat_icons .menu .block_all img,  .fat_icons .menu .filtered  img, 
.fat_icons .menu .relaxed   img,  .fat_icons .menu .allow_all img      { margin: 4px }

The extension version is in the extension branch.

The script is put together from the different bits and pieces in the src directory. You'll need some kind of unix environment with git, perl, make and base64 (for windows get cygwin).

To get a copy of the repository, do

git clone 'https://github.com/lemonsqueeze/scriptweeder.git'

Then make to build.

UI layout is generated from scriptweeder.ui, css from scriptweeder.css. Image references in the css are turned into data: urls automatically, so it's a convenient tool for hacking styles.

UI code lives in ui.js, userjs_ui.js manages widgets and the injected iframe, and the filtering logic is in core.js.

utils directory has a few things which could be useful outside of this project:

• google_nojs.js example showing how to disable javascript but still allow userjs to run. This one does it for google search.
• block_event_listeners.js userjs to block page event listeners.
• event_logger.js userjs to log all events
• page_event_logger.js regular script to see what events page is getting.

xml_macros (tools directory) takes care of expanding xml macros. Useful if you need modularity in xml or html. Syntax is inspired from fxmacro (couldn't get it to build so ended up writing this instead).