PUBLIC MARKS from decembre with tags dev & greasemonkey

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.

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.

data: URI Generator The data: URI scheme allows you to build URLs that embed small data objects. data: URIs are supported by most modern browsers except for Internet Explorer. The lack of IE support is holding back widespread adoption of data: URIs, but they are still very useful in a couple of specific areas such as embedding graphics and other data items in Greasemonkey scripts. You can read more about data: URIs and see some examples of their use, or use the generator below to create your own. data: URIs are defined in RFC 2397.

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.

Ce script montre comment mettre en place YUI Test (YUI 3) pour une utilisation avec des scripts Greasemonkey. Il vous permet de tester n'importe quelle page, même ceux que vous ne possédez pas. Il a été créé pour que vous puissiez écrire des tests unitaires pour les scripts Greasemonkey. La majeure partie de ce script vient: http://wiki.greasespot.net/Code_snippets # YUI_Li ... Je n'ai fait que l'adapter pour une utilisation avec YUI test, et fournir des instructions pour la mise en place de vos scripts afin qu'ils puissent être testés. Le script comme il est prévu ici peut être utilisé pour tester n'importe quelle page Web dans le monde. Pour l'utiliser pour tester un script Greasemonkey spécifique, juste un changement est nécessaire (ajouter un @ Exigent tag); voir les instructions d'essai ci-dessous.

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

I have a Greasemonkey script that works just fine in Firefox and Opera. I struggle with getting it to work in Chrome, however. The problem is injecting a function into the page that can be invoked by code from the page. Here's what I'm doing so far: First, I get a helper reference to the unsafeWindow for Firefox. This allows me to have the same code for FF and Opera (and Chrome, I thought).

Chrome has a secret weapon. His name is Aaron Boodman, and he created Greasemonkey. He now works on the Chrome Extensions team at Google. Even though Greasemonkey on Chrome isn't yet as mature as the Firefox version -- 15-25% of scripts might not work on Chrome yet -- it will definitely get there with Boodman's help. If you need some scripts to get you started, you can scope out Download Squad's 10 Greasemonkey Scripts You Shouldn't Browse Without, or peruse the large selection at userscripts.org.

Jouant occasionnellement avec Greasemonkey, j’ai fait face a des problèmes récurrent liés à l’architecture de l’extention elle-même. * Comment réutiliser une bibliothèque déjà présente dans la page, * comment traiter un résultat XML * ou qu’est-ce qui fait que je n’arrive pas à mettre une Yahoo!/Google maps dynamiquement. Réutiliser une librairie(, fonction, variable) existante

The URI microformat takes advantage of OpenURL and existing link resolver solution.It defines a convention of plugging URI metadata in HTML page. If it is adopted and widely used,now a microformat-aware application (be a greasemonkey script, or a web service) can grab the identifier and point to your local OpenURL resolver, you immediately get the copy from local library. It is very similar to COINS, but it's much simpler and cleaner, anyone can understand and use it, and its aplication can be beyond traditional research library. e.g. in a public library, you can use amazon as catalog and immediately check if it's available in local collection. COinS provides a great number of additional capabilities that URI microformat can't support. Since COinS can't be dismissed for this reason, it doesn't make sense to me to create yet another standard that does the same thing with so little savings.I will grant that the COinS is less intuitive.....

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.

manipuler données XUL avec greasemonkey.....est-ce possible? par exemple pour modifier l'extension officielle de delicious.