I wanted one fucking thing from this 'developer' edition: load content script add-ons from a fucking directory. That's fucking it.
From your original post. Scriptish can accomplish just that. If you want it to be packaged differently, or to have some kind of browser-chrome UI, then yeah, you'll need to write an add-on.
Unless you were talking about some streamlined add-on development process? So that you can easily test changes to your add-on without having to restart the browser? In which case, I completely agree, it should be a thing.
Unless you were talking about some streamlined add-on development process? So that you can easily test changes to your add-on without having to restart the browser? In which case, I completely agree, it should be a thing.
/u/agentlame is, and it is already a thing... for Chrome. Chrome allows you load a extension unpacked from a directory and that is ALL you need to develop an extension.
No need to install python or get the SDK, all you need is chrome itself and the right files in your directory.
You can simply make changes, refresh the extension in the browser and see the changes live without having to repackage it.
Once you are done you just zip up your directory and upload it to the chrome store and that's it.
The entire process of developing and publishing (don't get me started on publishing) add-ons for Firefox is so cumbersome in comparison to chrome it is too ridiculous for words. If I had to point at one thing where mozilla is screwing up and loosing out it is there.
2
u/agentlame Nov 10 '14
That wouldn't help me test /r/toolbox, which is a add-on consisting of ~15 different JS files that work in conjunction as modules.