Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Greasmonkey (Javascript)

Name: Anonymous 2009-03-31 14:32

Hey,
Sorry to annoy you /prog/, but I'm currently trying to get the hang of Greasemonkey (Firefox Add-on). Yes, I already tried googling and even found a tutorial, but it (honestly) sucks. (http://diveintogreasemonkey.org/)

May have a suggestion/link for a nice tutorial with preferably real-world examples, /prog/? The problem is that every single tutorial I find on the net is about installing the fucking Add-on and not about learning how to write scripts with it.

Help would be greatly appreciated.

Name: Anonymous 2009-03-31 14:34

Read SICP(JavaScript Edition).

Name: Anonymous 2009-03-31 14:37

>>2
Thanks - the trolling phase has just ended.
Now to the real answers *waiting*

Name: Anonymous 2009-03-31 14:38

>>3
Fuck you.

Name: Anonymous 2009-03-31 14:39

NO YOU!

Name: Anonymous 2009-03-31 14:42

>>3
There is a reason /prog/ recommends SICP: it helps you achieve SATORI, which you are quite far from.

Name: Anonymous 2009-03-31 14:44

There's this tendency among 14-year-olds to try to learn from tutorials instead of documentation. It's barely a step up from script kiddery, if you ask me.

Name: Anonymous 2009-03-31 14:46

IMHO: tutorials == documentation # most of the time
It's barely a step up from script kiddery, if you ask me.
Luckily no one asks you.

Name: Anonymous 2009-03-31 14:48

>>8
How the fuck would you know? You're googling for Greasemonkey tutorials, it's not like you have any context.

Name: Anonymous 2009-03-31 14:53

buy that book on the right

Name: Anonymous 2009-03-31 14:54

>>8
$ perl -e "tutorials == documentation ? print 'YHBT' :print 'IHBT'"
IHBT

Name: Anonymous 2009-03-31 15:12

>>1
Okay, here is your tutorial:
1. Create .user.js file
2. Add headers (like your name and copyright information [this is important!], just copypasta from another Greasemonkey script)
3. Each script basically runs when the page executes onload, so you don't have to explicitly hook any events.
4. Start JS'ing, e.g. window.close().
5. ???
6. Read JS reference, GM function reference, etc.

Name: Anonymous 2009-03-31 15:52

There's actually a "GreaseMonkey Hacks" book published by O'Reilly, which I came across when torrent hunting.

Name: Anonymous 2009-03-31 16:22

>>12
Each script basically runs when the page executes onload, so you don't have to explicitly hook any events.
They actually execute when the DOM is loaded and ready for manipulation. The onload() javascript event does not happen for some time after.

Name: Anonymous 2009-03-31 17:10

>>14
No, they don't.

Name: Anonymous 2010-12-17 1:40

This post brought to you by the Gay Nigger Association of America

Name: Anonymous 2010-12-21 7:20

Don't change these.
Name: Email:
Entire Thread Thread List