Comments on: Memo from 2006: CamiTools incompatible with Camino http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/ A journal at al-Qâhira fî Amrîkâ Fri, 13 Jan 2012 20:41:10 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Smokey http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6690 Smokey Sun, 21 Dec 2008 00:09:51 +0000 http://www.ardisson.org/afkar/?p=118#comment-6690 …and <code>flashblock.css</code> from your <code>~/Library/Application Support/Camino/chrome</code> folder, too. …and flashblock.css from your ~/Library/Application Support/Camino/chrome folder, too.

]]> By: Smokey http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6686 Smokey Wed, 17 Dec 2008 20:14:46 +0000 http://www.ardisson.org/afkar/?p=118#comment-6686 In addition to the locations mentioned in my previous comment, you may also need to remove a <code>flashblock.jar</code> file from your <code>~/Library/Application Support/Camino/chrome</code> folder. That file contains CamiTools/CamiFlash’s copy of Flashblock, which is horribly outdated and which will not function correctly in Camino 1.6.6 or Camino 2.0b1pre nightly builds since November 2008. In addition to the locations mentioned in my previous comment, you may also need to remove a flashblock.jar file from your ~/Library/Application Support/Camino/chrome folder.

That file contains CamiTools/CamiFlash’s copy of Flashblock, which is horribly outdated and which will not function correctly in Camino 1.6.6 or Camino 2.0b1pre nightly builds since November 2008.

]]> By: geomom http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6511 geomom Sun, 10 Aug 2008 04:28:38 +0000 http://www.ardisson.org/afkar/?p=118#comment-6511 Got it! Thanks! Got it! Thanks!

]]> By: Smokey http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6510 Smokey Sun, 10 Aug 2008 03:29:00 +0000 http://www.ardisson.org/afkar/?p=118#comment-6510 geomom, CamiTools itself is pretty easy to remove: inside the Camino profile folder (<code>~/Library/Application Support/Camino</code>, where <code>~</code> represents your user folder) is a <code>PreferencePanes</code> folder. Inside of that folder should be a <code>CamiTools.prefPane</code> file, which you can simply move to the Trash. (If CamiTools isn’t in that folder but is still showing up as installed in Camino, look in the same place but start from the <code>Library</code> folder at the top level of your hard disk rather than from the one in your user folder.) Unfortunately, it’s much more difficult to get rid of any of the changes CamiTools might have made that could be causing other problems. The easiest way to do so is to quit Camino, completely throw away your current Camino preferences files (<code>prefs.js</code> and <code>user.js</code> in your <code>~/Library/Application Support/Camino</code> folder) and the <code>chrome.rdf</code> file in the <code>chrome</code> folder inside your Camino profile folder, and then re-set all of your preferences when you launch Camino again. (Your bookmarks, history, cookies, and passwords won’t be touched by this.) It’s not pretty, but it’s the easiest way to be sure to root out all the remnants of CamiTools. :-( If you have any questions about the process, please feel free to stop by the <a href="http://forums.mozillazine.org/viewforum.php?f=12" rel="nofollow">Camino support forum</a>. geomom, CamiTools itself is pretty easy to remove: inside the Camino profile folder (~/Library/Application Support/Camino, where ~ represents your user folder) is a PreferencePanes folder. Inside of that folder should be a CamiTools.prefPane file, which you can simply move to the Trash. (If CamiTools isn’t in that folder but is still showing up as installed in Camino, look in the same place but start from the Library folder at the top level of your hard disk rather than from the one in your user folder.)

Unfortunately, it’s much more difficult to get rid of any of the changes CamiTools might have made that could be causing other problems. The easiest way to do so is to quit Camino, completely throw away your current Camino preferences files (prefs.js and user.js in your ~/Library/Application Support/Camino folder) and the chrome.rdf file in the chrome folder inside your Camino profile folder, and then re-set all of your preferences when you launch Camino again. (Your bookmarks, history, cookies, and passwords won’t be touched by this.) It’s not pretty, but it’s the easiest way to be sure to root out all the remnants of CamiTools. :-(

If you have any questions about the process, please feel free to stop by the Camino support forum.

]]> By: geomom http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6509 geomom Sat, 09 Aug 2008 14:33:47 +0000 http://www.ardisson.org/afkar/?p=118#comment-6509 Stoopid Question! How do I remove CamiTools? I've had it installed since before the dawn of time and have no idea how to remove it :-) Thanks! Stoopid Question!
How do I remove CamiTools? I’ve had it installed since before the dawn of time and have no idea how to remove it :-)
Thanks!

]]> By: Smokey http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6508 Smokey Fri, 08 Aug 2008 18:23:46 +0000 http://www.ardisson.org/afkar/?p=118#comment-6508 For more information about InputManagers and why applications have no control over them, see <a href="http://www.macjournals.com/news/inputmanagerhacks.html" rel="nofollow">this article</a> from MacJournals. (Hat tip to <a href="http://escapedthoughts.com/" rel="nofollow">Stuart</a>; I’d missed this before.) For more information about InputManagers and why applications have no control over them, see this article from MacJournals. (Hat tip to Stuart; I’d missed this before.)

]]> By: Smokey http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6500 Smokey Wed, 30 Jul 2008 20:35:42 +0000 http://www.ardisson.org/afkar/?p=118#comment-6500 Kurt: No, Camino doesn’t use the blocklisting code (in theory we could hook up the part that works on NPAPI plug-ins), but these are also completely different kinds of “add-on” code. Some of them (like CamiScript) are even written as InputManagers, which Cocoa automatically loads into every application process and therefore are impossible to prevent from loading (which is one of the main reasons Apple is deprecating InputManagers). Kurt: No, Camino doesn’t use the blocklisting code (in theory we could hook up the part that works on NPAPI plug-ins), but these are also completely different kinds of “add-on” code. Some of them (like CamiScript) are even written as InputManagers, which Cocoa automatically loads into every application process and therefore are impossible to prevent from loading (which is one of the main reasons Apple is deprecating InputManagers).

]]> By: Kurt http://www.ardisson.org/afkar/2008/07/30/memo-from-2006-camitools-incompatible-with-camino/comment-page-1/#comment-6499 Kurt Wed, 30 Jul 2008 19:30:08 +0000 http://www.ardisson.org/afkar/?p=118#comment-6499 Why not just blocklist the extensions? I'm not sure if Camino also uses this code from Firefox or not...if the later, disregard then. Why not just blocklist the extensions? I’m not sure if Camino also uses this code from Firefox or not…if the later, disregard then.

]]>