Development:Porting or Using Firefox Extensions with Camino - Revision history

Sardisson: /* Non-exhaustive list of extensions known to work in Camino 2.1 */ Add JSONView, which provides inline, syntax-hightlighted display of .json files

2012-04-27T22:10:12Z

Non-exhaustive list of extensions known to work in Camino 2.1: Add JSONView, which provides inline, syntax-hightlighted display of .json files

Sardisson: /* Non-exhaustive list of extension-related differences between Camino and Firefox */ add the bug reference, since i found it again

2012-01-12T06:20:37Z

Non-exhaustive list of extension-related differences between Camino and Firefox: add the bug reference, since i found it again

Sardisson: /* Non-exhaustive list of extension-related differences between Camino and Firefox */

2012-01-09T22:21:47Z

Non-exhaustive list of extension-related differences between Camino and Firefox

Sardisson: /* Non-exhaustive list of extension-related differences between Camino and Firefox */ add jetpack, too

2012-01-09T22:21:13Z

Non-exhaustive list of extension-related differences between Camino and Firefox: add jetpack, too

Sardisson: /* Non-exhaustive list of extension-related differences between Camino and Firefox */ one more tweak

2012-01-09T22:19:04Z

Non-exhaustive list of extension-related differences between Camino and Firefox: one more tweak

Sardisson: /* Non-exhaustive list of extensions known to work in Camino 2.1 */ add inline disposit

2012-01-09T22:14:01Z

Non-exhaustive list of extensions known to work in Camino 2.1: add inline disposit

Sardisson: typo

2012-01-09T22:04:36Z

typo

Sardisson: few more tweaks

2012-01-09T22:02:50Z

few more tweaks

Sardisson: /* Non-exhaustive list of extension-related differences between Camino and Firefox */

2012-01-09T21:57:25Z

Non-exhaustive list of extension-related differences between Camino and Firefox

Sardisson: /* Non-exhaustive list of differences between Camino and Firefox */

2012-01-09T21:52:47Z

Non-exhaustive list of differences between Camino and Firefox

@@ Line 35: / Line 35: @@
 ** Installation instructions: Unpack the extension and install the <code>inlinedisposition.js</code> file in your Camino profile’s <code>components</code> folder, then launch Camino.
 ** [http://code.kliu.org/misc/inlinedisposition/attachtest.pl Test page]
 * Certain content-blocking tools
 ** [https://bugzilla.mozilla.org/attachment.cgi?id=573330 Attachment 573330] on {{bug|656584}} illustrates how to convert a simple [https://addons.mozilla.org/en-US/firefox/addon/blocksite/ BlockSite] script into a JavaScript XPCOM component that Camino 2.1 can use.

@@ Line 12: / Line 12: @@
 *: Camino is an embedding application; it embeds the Gecko rendering engine,  and a certain amount of the Mozilla platform relevant to core web browser features, inside a native Cocoa application.  Camino does not use XUL for the browser’s user interface, and XUL in the content area does not work.  Any extension that relies on overlaying <code>browser.xul</code> will not work (or will require changes, e.g., to have an XPCOM component load ancillary scripts).
 *: Extensions that require UI for configuration will need a [[Development:Third-Party_Preference_Panes|Camino preference pane]] to allow the user to change Gecko preferences from Camino, or the user will have to edit the Gecko preference files directly.
-*: The supported mechanism for adding a toolbar button is an AppleScript [[Development:Camino_AppleScript_Guide#Implementing_Toolbar_Script_Items|toolbar script item]].  However, AppleScripts currently have limited access to Camino’s internals, and no AppleScript<->XPCOM bridge is known to exist.
+*: The supported mechanism for adding a toolbar button is an AppleScript [[Development:Camino_AppleScript_Guide#Implementing_Toolbar_Script_Items|toolbar script item]].  However, AppleScripts currently have limited access to Camino’s internals, and no AppleScript<->XPCOM or AppleScript<->XPConnect bridge is known to exist ({{bug|61356}}).
 * No Firefox-specific functions and libraries
 *: Camino does not have a <code>browser.js</code>, [https://developer.mozilla.org/en/FUEL FUEL], [https://developer.mozilla.org/en/Jetpack Jetpack], or any other Firefox-specific code or code wrappers/shortcuts.  If an extension talks to Gecko using Gecko APIs, there is a decent chance it will work, but anything that relies on Firefox code (e.g., finding the XUL <code>&lt;browser&gt;</code> element or talking to the <code>tabbrowser</code> JavaScript object) will not work (or will have to be rewritten).

@@ Line 10: / Line 10: @@
 * No XUL
-*: Camino is an embedding application; it embeds the Gecko rendering engine,  and a certain amount of the Mozilla platform relevant to core web browser features, inside a native Cocoa application.  Camino does not use XUL for the browser’s user interface, and XUL in the content area does not work.  Any extension that relies on overlaying <code>browser.xul</code> will not work (or will require changes, e.g. to have an XPCOM component load ancillary scripts).
+*: Camino is an embedding application; it embeds the Gecko rendering engine,  and a certain amount of the Mozilla platform relevant to core web browser features, inside a native Cocoa application.  Camino does not use XUL for the browser’s user interface, and XUL in the content area does not work.  Any extension that relies on overlaying <code>browser.xul</code> will not work (or will require changes, e.g., to have an XPCOM component load ancillary scripts).
 *: Extensions that require UI for configuration will need a [[Development:Third-Party_Preference_Panes|Camino preference pane]] to allow the user to change Gecko preferences from Camino, or the user will have to edit the Gecko preference files directly.
 *: The supported mechanism for adding a toolbar button is an AppleScript [[Development:Camino_AppleScript_Guide#Implementing_Toolbar_Script_Items|toolbar script item]].  However, AppleScripts currently have limited access to Camino’s internals, and no AppleScript<->XPCOM bridge is known to exist.

@@ Line 14: / Line 14: @@
 *: The supported mechanism for adding a toolbar button is an AppleScript [[Development:Camino_AppleScript_Guide#Implementing_Toolbar_Script_Items|toolbar script item]].  However, AppleScripts currently have limited access to Camino’s internals, and no AppleScript<->XPCOM bridge is known to exist.
 * No Firefox-specific functions and libraries
-*: Camino does not have a <code>browser.js</code>, [https://developer.mozilla.org/en/FUEL FUEL], or any other Firefox-specific code or code wrappers/shortcuts.  If an extension talks to Gecko using Gecko APIs, there is a decent chance it will work, but anything that relies on Firefox code (e.g., finding the XUL <code>&lt;browser&gt;</code> element or talking to the <code>tabbrowser</code> JavaScript object) will not work (or will have to be rewritten).
+*: Camino does not have a <code>browser.js</code>, [https://developer.mozilla.org/en/FUEL FUEL], [https://developer.mozilla.org/en/Jetpack Jetpack], or any other Firefox-specific code or code wrappers/shortcuts.  If an extension talks to Gecko using Gecko APIs, there is a decent chance it will work, but anything that relies on Firefox code (e.g., finding the XUL <code>&lt;browser&gt;</code> element or talking to the <code>tabbrowser</code> JavaScript object) will not work (or will have to be rewritten).
 * No Extension Manager or extensions system
 *: Camino does not include the Extensions Manager or a formal extensions system.  Camino 2.1 does register (JavaScript) XPCOM components from the profile’s <code>components</code> folder at startup, and it also registers chrome from the profile’s <code>chrome</code> folder at startup.  (In addition, Camino 2.1 will load NPAPI plug-ins from the profile’s <code>Internet Plug-Ins</code> folder, allowing for the installation of plug-ins that only Camino will use.)  As a consequence, many Firefox extensions that do work in Camino must be unpacked and manually installed, and any updates must also be manually downloaded and installed.

@@ Line 10: / Line 10: @@
 * No XUL
-*: Camino is an embedding application; it embeds the Gecko rendering engine,  and a certain amount of the Mozilla platform relevant to core web browser features, inside a native Cocoa application.  Camino does not use XUL for the browser’s user interface, and XUL in the content area does not work.  Any extension that relies on overlaying <code>browser.xul</code> will not work (or will require changes).
+*: Camino is an embedding application; it embeds the Gecko rendering engine,  and a certain amount of the Mozilla platform relevant to core web browser features, inside a native Cocoa application.  Camino does not use XUL for the browser’s user interface, and XUL in the content area does not work.  Any extension that relies on overlaying <code>browser.xul</code> will not work (or will require changes, e.g. to have an XPCOM component load ancillary scripts).
 *: Extensions that require UI for configuration will need a [[Development:Third-Party_Preference_Panes|Camino preference pane]] to allow the user to change Gecko preferences from Camino, or the user will have to edit the Gecko preference files directly.
 *: The supported mechanism for adding a toolbar button is an AppleScript [[Development:Camino_AppleScript_Guide#Implementing_Toolbar_Script_Items|toolbar script item]].  However, AppleScripts currently have limited access to Camino’s internals, and no AppleScript<->XPCOM bridge is known to exist.

@@ Line 30: / Line 30: @@
 *: Tells Google Analytics not to track your visits
 ** [http://www.ardisson.org/smokey/moz/ga-test.html Installation instructions and test page]
 * Certain content-blocking tools
 ** [https://bugzilla.mozilla.org/attachment.cgi?id=573330 Attachment 573330] on {{bug|656584}} illustrates how to convert a simple [https://addons.mozilla.org/en-US/firefox/addon/blocksite/ BlockSite] script into a JavaScript XPCOM component that Camino 2.1 can use.

@@ Line 1: / Line 1: @@
 Camino has had limited support for UI-less Gecko platform (“Firefox”) extensions for some time; for instance, in the Camino 0.x era, the third-party preference pane “CamiFlash” offered a Flash-blocking feature that used the Flashblock extension.
 Camino 2.1 added new features that may allow more extensions to work with Camino; however, as before, several caveats apply.
-As a general rule, extensions that have no UI (other than perhaps a toolbar button to toggle behavior on or off) and are implemented largely as JavaScript XPCOM components or XBL bindings to web content, or extensions that have already been ported to Safari or Google Chrome, are most likely to work, or to easily be made to work, in Camino 2.1.
+As a general rule, extensions that interact primarily with web content, have no UI (other than perhaps a toolbar button to toggle behavior on or off) and are implemented largely as JavaScript XPCOM components or XBL bindings to web content, or extensions that have already been ported to Safari or Google Chrome, are most likely to work, or to easily be made to work, in Camino 2.1.
 ==Non-exhaustive list of extension-related differences between Camino and Firefox==
@@ Line 10: / Line 12: @@
 *: Camino is an embedding application; it embeds the Gecko rendering engine,  and a certain amount of the Mozilla platform relevant to core web browser features, inside a native Cocoa application.  Camino does not use XUL for the browser’s user interface, and XUL in the content area does not work.  Any extension that relies on overlaying <code>browser.xul</code> will not work (or will require changes).
 *: Extensions that require UI for configuration will need a [[Development:Third-Party_Preference_Panes|Camino preference pane]] to allow the user to change Gecko preferences from Camino, or the user will have to edit the Gecko preference files directly.
 * No Firefox-specific functions and libraries
 *: Camino does not have a <code>browser.js</code>, [https://developer.mozilla.org/en/FUEL FUEL], or any other Firefox-specific code or code wrappers/shortcuts.  If an extension talks to Gecko using Gecko APIs, there is a decent chance it will work, but anything that relies on Firefox code (e.g., finding the XUL <code>&lt;browser&gt;</code> element or talking to the <code>tabbrowser</code> JavaScript object) will not work (or will have to be rewritten).