Chrome Tailor

[Erik Vold]

Rocketeers,

I've started a node based cli (which uses jpm) to wrap chrome extension code in a jetpack, which I'm calling `chrome-tailor`.

https://github.com/erikvold/chrome-tailor

I published it to npm but that seems to have caused some error so it might take a couple days to correct that.  So if you want to hack on this, clone the git repo, `npm install`, and use `npm link` afterwards.

I've only barely started implementing an action button, and I'm using a fake `chrome.tabs.query` implementation, this is bare bones.

I think building this out will make any gap between the apis we provide and the apis google chrome provides, and could one day enable thousands more extensions to work on Firefox in an e10s friendly way.

I'm hoping someone is willing to help me out ;)

Regards,

Erik

[Noit Saab]

This is absolutely awesome. So many people have chrome extensions and are trying to convert them them to Firefox. I hope someone helps you out with this!

---

Date: Thu, 16 Apr 2015 15:38:50 -0700
Subject: [jetpack] Chrome Tailor
From: ev...@mozilla.com
To: mozilla-la...@googlegroups.com

--
You received this message because you are subscribed to the Google Groups "mozilla-labs-jetpack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mozilla-labs-jet...@googlegroups.com.
To post to this group, send email to mozilla-la...@googlegroups.com.
Visit this group at http://groups.google.com/group/mozilla-labs-jetpack.
For more options, visit https://groups.google.com/d/optout.

[Erik Vold]

Oh I forgot to mention a simple test!

If you checkout https://github.com/erikvold/google-chrome-extension-examples/tree/master/tutorials/getstarted

`cd` to it, then run `chrome-tailor xpi`, then a xpi will be created!

Erik

[Erik Vold]

Rocketeers!

I've done quite a few updates to `chrome-tailor` today.

Currently the "browser_action" is implemented, along with these APIs:

* chrome.extension.getURL
* chrome.extension.inIncognitoContext
* chrome.extension.isAllowedIncognitoAccess
* chrome.extension.isAllowedFileSchemeAccess
* chrome.extension.setUpdateUrlData
* chrome.history.addUrl
* chrome.history.deleteAll
* chrome.history.deleteUrl
* chrome.tabs.create
* chrome.tabs.duplicate
* chrome.tabs.getCurrent
* chrome.tabs.query
* chrome.tabs.remove

I've also created some working examples at https://github.com/erikvold/chrome-tailor/tree/master/examples

Finally, `chrome-tailor run -b nightly` now works!!

More to come!

Regards,

Erik

On Thu, Apr 16, 2015 at 3:38 PM, Erik Vold <ev...@mozilla.com> wrote:

[Dietrich Ayala]

This is *fantastic*. Can't way to try this out.

Would be rad to see this implement new tab page API too.

[Erik Vold]

newtab overrides are now implemented!

0.0.3 has been released! https://www.npmjs.com/package/chrome-tailor

npm is fixed!

also implemented:

* chrome.browserAction.onClick.addListener
* chrome.topSites.get
* chrome.tabs.executeScript

More tomorrow!

E

[Erik Vold]

oh also background pages are now implemented!

E

[Noit Saab]

Lots of newbies make a chrome extension and cant figure out how to make a firefox extension and the post about it on forums and Stackoverlow. So this will be real real welcome!

---

Date: Fri, 17 Apr 2015 02:49:21 -0700
Subject: Re: [jetpack] Re: Chrome Tailor
From: ev...@mozilla.com
To: mozilla-la...@googlegroups.com

[Anurag Rana]

I developed a chrome extension which is available at chrome store. I have the code with me in a directory. I have installed chrome-tailor. Now I am not sure how to proceed with converting chrome extension to firefox extension. Please help.