Activity (RSS)

The actual ff ext file which is downloaded points to the location where the ff can find updates to the ff ext with updateURL node. Since the file where you can ...

True, but on the other hand they're pretty much all single words (or so: are namespace or homepage 2 words?) and furthermore do not contain acronyms like URL......

Every current @key is also completely lowercase http://wiki.greasespot.net/Metadata_block

List installed userscripts in a "scripts" or "userscripts" tab in Firefox "Add-ons" dialog.
This idea has also been mentioned on GM issue 1012.

This is a major...

Parse, save and restore scripts version by introducing a @version header tag.
This uso tag is very much used, as measured some time ago this year (sorry, cannot...

It could, but that would be a change of policy: header tag matching is case-sensitive in WM and GM.
I suppose i'd rather pick one and stick to it, case sensitiv...

Perhaps webmonkey could prefer @updateURL but accept a case-insensitive @updateurl, if @updateURL is not found? because if webmonkey uses @updateURL then @updat...

Implementation note: script version strings are compared using the standard nsIVersionComparator interface.

Let's go. :-)

Optional GUI feature, used among other things for "add-on" style userscript listing (see #15).
Possible implementations include:

• introduction of an @icon heade...

So far GM_setValue and GM_getValue only support integers, boolean and strings. It would be nice if they supported objects as well, in order to load/save a bunch...

Ok, i'm choosing @updateURL (over @updateurl): this way it is exactly the same as Mozilla install manifest.
Any objection?

You really seem to be interested in multiple @updateURL and i still fail to see where the value is (mirroring?). Perhaps you could expand on that a bit?

Ah fo...

Sounds good to me: i would vote for @updateurl (or @updateURL) for the same reason. We're down to a "case" decision. :-)

I guess sha1 is fine if webmonkey reme...

I guess sha1 is fine if webmonkey remembers the previously used sha1(s), and compares the potential update script's sha1 to these. This logic could get a little...

What's wrong with implicit (SHA1 based) version updates?

If there are two+ urls for updates, then with sha1 based version updates the urls would have to be up...

Maybe ask the user to confirm they understand they are overwriting a script that was edited

That sounds good to me. Only savvy users would edit a script anywa...

This does sound pretty good.

I'd like to identify scripts that have been user-edited since install time: should we still update?

Maybe ask the user to confirm...

Well, one reason this is not available yet is that i don't have a "perfect plan". :-)

Here is where i'm at:
I intend to support uso's @version tag: if the URL y...

Hey Olivier,

What is your plan for this feature?

E

With the new injection logic it is not possible to wrap scripts in a function from WM any longer. Impossible to protect the API similarly either.

The previous modification has been reversed with the new injection logic.
Re-open and schedule for 0.1a2.

Pushing back further refactoring to 0.1a2