it seems its mostly file system access which firefox extensions (running with chrome js priviledge) have access to via the XPCOM File I/O classes as documented here: https://developer.mozilla.org/en/Code_snippets/File_I%2f%2fO
even down to providing a File chooser UI widget.
Evolus Pencil (http://pencil.evolus.vn/en-US/Home.aspx) is a nice example of how this approach can be taken to build a native editor application (in this case diagram editor) with native filesystem access as a FF add-on.
I guess the other job would be to fix an webkit-prefix-isms in the css (less) styles, though having a very quick look at least in some places there are moz prefixes as well so perhaps brackets is already being tested within firefox as well?
Issue by maks Friday May 04, 2012 at 02:49 GMT Originally opened as https://github.com/adobe/brackets/issues/806
Would be nice to have an alternative to running within the brackets-app (aka chromium embedded) webshell.
Looking at the extensions implemented in: https://github.com/adobe/brackets-app/blob/master/src/win/cefclient/brackets_extensions.cpp
it seems its mostly file system access which firefox extensions (running with chrome js priviledge) have access to via the XPCOM File I/O classes as documented here: https://developer.mozilla.org/en/Code_snippets/File_I%2f%2fO even down to providing a File chooser UI widget.
Evolus Pencil (http://pencil.evolus.vn/en-US/Home.aspx) is a nice example of how this approach can be taken to build a native editor application (in this case diagram editor) with native filesystem access as a FF add-on.
I guess the other job would be to fix an webkit-prefix-isms in the css (less) styles, though having a very quick look at least in some places there are moz prefixes as well so perhaps brackets is already being tested within firefox as well?