Comments on: Finding unused entities in your Firefox extensions http://www.chrisfinke.com/2008/04/22/finding-unused-entities-in-your-firefox-extensions/ Christopher Finke is a software engineer at Mahalo. He is available for birthday parties and bar mitzvahs. Sat, 30 Aug 2008 03:08:02 +0000 http://wordpress.org/?v=2.6.1 By: Stephen http://www.chrisfinke.com/2008/04/22/finding-unused-entities-in-your-firefox-extensions/#comment-70311 Stephen Thu, 22 May 2008 22:00:28 +0000 http://www.chrisfinke.com/?p=722#comment-70311 Before I start diving into the sensitive Firefox files, can you please tell me where the link goes, where the script goes, and where do I view the results to do the pruning? Thank you Before I start diving into the sensitive Firefox files, can you please tell me where the link goes, where the script goes, and where do I view the results to do the pruning?

Thank you

]]> By: Philipp Kewisch http://www.chrisfinke.com/2008/04/22/finding-unused-entities-in-your-firefox-extensions/#comment-70039 Philipp Kewisch Wed, 21 May 2008 09:36:25 +0000 http://www.chrisfinke.com/?p=722#comment-70039 While this script will probably catch every entitiy, it won't work for all properties. I only realized this after fitting the script for my purposes and wondering that there were so many unused properties. If your extension compiles property names at runtime, then this script will obviously not catch them, i.e calGetString("repeatDetailsDay" + day_of_week(byday[0])) where repeatDetailsDay1 to repeatDetailsDay7 are vaild property strings. This script is a good start though. While this script will probably catch every entitiy, it won't work for all properties. I only realized this after fitting the script for my purposes and wondering that there were so many unused properties. If your extension compiles property names at runtime, then this script will obviously not catch them, i.e

calGetString("repeatDetailsDay" + day_of_week(byday[0]))

where repeatDetailsDay1 to repeatDetailsDay7 are vaild property strings. This script is a good start though.

]]>