Sometimes, with greasemonkey scripts, I reach the limit of what GM allows me to do.
For example, I recently got a request for a GM script that would scrape content from a page and then use that content as input to a bash script. Since GM scripts don't have access to the full power provided to real Firefox extensions by Components.classes, I can't do this in GM. (Currently, trying to use Components.classes in a GM script results in "Error: Permission denied for <$DOMAIN> to get property XPCComponents.classes"). Now I find myself in the position of writing a full Firefox addon, that will mostly act like a GM script (and will have to recreate some of GM - like detecting which URL is loaded in a page, so it knows when to run) just so I can have access to Components.classes. Which makes me want to just have Components.classes available to GM scripts so I never have to do this again. GM scripts already insulate themselves from malicious pages abusing GM_xmlhttpRequest() using XPCNativeWrappers, so wouldn't that suffice as security against those same malicious pages abusing access to Components.classes? Is there any reason *not* to make it available to script writers? Then scripts could start reaching toward the full power of an addon, but without requiring all the manifest and XML jargon that comes from making an XPI, and without requiring a user to restart Firefox on install. And I think that'd be pretty cool. Noah -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/greasemonkey-users?hl=en.
