[Greasemonkey] Edit scripts in "Manage" with version 0.3b - keep getting First time Alert

Simon Bünzli helmi79 at yahoo.de
Sun May 8 22:51:57 EDT 2005


dmccunney wrote on 08.05.05 04:55:
> I *have* daydreamed a bit about a stand-alone Javascript interpreter
> that ran outside the context of a browser.  CSS, XUL, and Javascript
> could be the basis for a wonderful alternative Windows shell.  Right
> now, the pieces aren't all there, but maybe down the road a bit...

The pieces *are* there, if you replace XUL by HTML. Search Google for 
"Hypertext Application" and "Windows Script Host". The former is a way 
of writing simple apps using HTML, CSS and JScript/VBScript (they'll be 
run in a chrome-less Internet Explorer window); the later is a scripting 
framework which per default uses JScript (this is Microsoft's 
interpretation of the ECMAScript standard of which JavaScript is 
Netscape's) and VBScript - but can be extended to Python, Perl, etc.

As for the problems you could get by just launching a user script file, 
see my post in bugzilla:
http://bugzilla.mozdev.org/show_bug.cgi?id=10107#c2

I've further attached my solution to this problem: let a hidden pref 
(greasemonkey.editor) point to the local path of the editor to be used. 
If the pref is not set, offer the user a Find Dialog to locate an 
editor. The first time, you want to edit a script, you'll thus have to 
tell Greasemonkey what your tool should be. That way, you don't have to 
mess with any file associations, you don't get a long message (which 
might rather confuse basic users) and you could still cancel editing, if 
you thought it over again...

Not that this solution should be final, but I consider it to be much 
more user friendly than the currently existing one.

Cheers,
Simon



More information about the Greasemonkey mailing list