PUBLIC MARKS from decembre with tags dev & userscript

var implementations = [ { site: "https://www.babelio.com/mabibliotheque.php", // regex to compare against site URL, similar to @include nextLinkSelector: ".fleche.icon-next", // css selector for the next link, tip: find the current page button and do next sibling contentSelector: ".mes_livres", // the content that will be added to from the next page javascript: false // set this to true if the website uses javascript to load content, 50% chance it'll work }, { site: "https://www.babelio.com/livres-", // regex to compare against site URL, similar to @include nextLinkSelector: ".pagination .icon-next", // css selector for the next link, tip: find the current page button and do next sibling contentSelector: "#debug", // the content that will be added to from the next page javascript: false // set this to true if the website uses javascript to load content, 50% chance it'll work } } ];

Working and updated forum....

What? The Greasespot Wiki will be updated to explain Greasemonkey 4 in detail. Until then, here's a quick summary. First, there is only an embedded editor. Browser Extensions have no access to the file system, so you can no longer author user scripts in your familiar text editor. There is only one object provided to user scripts now, named GM. It has several properties. One of them is info – the equivalent of the old GM_info. There are also several methods of this object: getResourceUrl, deleteValue/getValue/listValues/setValue, xmlHttpRequest. To use these methods you still need @grant, and use the new name, e.g.: // @grant GM.setValue The new form has a dot, where the old form has an underscore. You may specify both @grants, if you'd like to be compatible with Greasemonkey 4 and other user script engines at the same time. As of today, there is no support for: GM_log (use console.log), GM_addStyle, GM_registerMenuCommand, nor GM_getResourceText.

I'm the administrator of userstyles.org. I want to start offering my styles to Greasemonkey (and similar) users. For applicable styles on userstyles.org, just plunk "/style.user.js" at the end of the URL. (For example, http://userstyles.org/style/show/242/style.user.js ). Not all styles on the site can be converted into user scripts. For example, those affecting chrome wouldn't work. Those styles will return a 404 if you try to open their styles. I'd like some feedback on the format I'm using. Is the code the best it can be, are there problems with meta-data, etc. Thanks.

jQuery.copyCSS: Quick, simple jQuery extension to retrieve or copy all styles (with optional whitelist and blacklist) from an HTML element.

For use on production websites with any amount of traffic. Files are served via MaxCDN's super fast global CDN. No traffic limits or throttling. It's best to use a specific tag or commit hash in the URL (not a branch). Files are cached permanently after the first request. The catch: this is a free service, so there are no uptime or support guarantees.

Forum: MooTools - Forum d'entraide sur le framework MooTools.

JSMin is a filter which removes comments and unnecessary whitespace from JavaScript files. It typically reduces filesize by half, resulting in faster downloads. It also encourages a more expressive programming style because it eliminates the download cost of clean, literate self-documentation.You can automate this process with a minimizing application which you can find here and an on-line javascript version here ______ You should note that while comments are useful for maintaining the code, they are a liability itself in Javascript since they will be transmitted along with the code to each and every page load, which can create substantial bandwidth penalties and increase the load time of your page for users. This doesn't mean you shouldn't comment your code, just that once your code is "finished" you should make a backup copy with the comments, then strip out all the comments in the file which is actually sent to the user.

Well, here is how to run userscripts in chrome : * Add this flag to Google Chrome launcher : --enable-user-scripts - Now, create a folder in your user data directory. Name it as User Scripts. - Save your all GM scripts in this folder. - If you want to import all userscripts from Firefox — you need to do it manually. We have shown you the way to backup your Greasemonkey scripts. Just navigate to your GM script folder in Firefox data directory as describe in this post. Now, you can copy and paste every script’s file manuallyAnd, you are done! Restart the chrome — and visit any related site. It is quite possible that your favorite GM Script will do the magic. - Important fact : Chrome supports “Early Injection” – the ability to run scripts very early in the page’s lifecycle. In Firefox, userscripts run after page load. But in chrome, you can set it to run before page load. For this, you need to add an extra line in scripts meta data section : // @run-at document-start

The Order of Things to Learn Look to the "Resources" section for places to learn about these. 1. HTML. Hypertext Markup Language. Not the same "language" as JavaScript. This is a markup language, meaning it's a bunch of text that is meant to represent some type of structure, in this case, a web page. 2. XML. Extensible Markup Language. In case you didn't realize, HTML itself is a type of "XML". Learning XML is important because many popular websites (YouTube, Facebook, Last.fm) use XML to interact with data. Since you already know HTML by this point, understanding XML should be cake. 3. CSS. Cascading Style Sheets. This is the way HTML (should be) stylized. You'll want to learn this. 4. JavaScript. Learn all the basics: data types, functions, JavaScript's native functions like prompt, alert, etc. 5. The Greasemonkey Extras. Like I said, Greasmonkey == JavaScript, with a lot of extras. A specific page listing the API's can be found here.