Can a sandboxed Opera Addon be published?

Reply to Can a sandboxed Opera Addon be published? on Tue, 16 Feb 2016 11:47:40 GMT

shwetankdixit — Tue, 16 Feb 2016 11:47:40 GMT

Unfortunately, we don't have that as an option right now, but thanks for mentioning it. I'll see what we can do about it in the future.

Thanks

Reply to Can a sandboxed Opera Addon be published? on Tue, 16 Feb 2016 11:19:04 GMT

philipbattle — Tue, 16 Feb 2016 11:19:04 GMT

Hi,

What we're looking for is a way to publish our addon-on to a limited group, for testing. It is somewhat inconvenient for each beta tester to use "developer mode" and "Load Unpacked Extension" for each release.

Chrome allows us to test a "nightly version" of our product as it is only "Published to Testers"; A form of private, available only to a list of "trusted users" which is managed from the Chrome store developer dashboard.

Many thanks in lieu of your reply.

Rgs.

Philip

Reply to Can a sandboxed Opera Addon be published? on Wed, 10 Feb 2016 16:17:24 GMT

shwetankdixit — Wed, 10 Feb 2016 16:17:24 GMT

Can you please elaborate on what exactly do you mean by 'sandboxed' in this context?

We have something like 'developer mode'. On the extensions management page (type in 'opera://extensions' in the address bar to bring it up if you can't find it in the menu options) ... you can find a button called 'developer mode' in the upper right hand corner. Once you click that, developer mode is on.

Then you can load your extension from your local file system that you are developing. It will enable you to easily inspect the extension using the browser's developer tools, reload it, and pack it as a .nex file too.