DOM Inspector as extension
- mai9
- Posts: 1619
- Joined: January 15th, 2003, 3:41 pm
- Location: Barcelona
- Contact:
DOM Inspector as extension
Is it possible to pack DOM Inspector as an extension?
I want this because not all builds include it, and if they do, I have to decide to install it the same moment I am installing FF. If you want it afterwards you have to reinstall the whole Firefox.
Can DOMi be an extension?
(is there anybody willing to pack it?)
I want this because not all builds include it, and if they do, I have to decide to install it the same moment I am installing FF. If you want it afterwards you have to reinstall the whole Firefox.
Can DOMi be an extension?
(is there anybody willing to pack it?)
- mai9
- Posts: 1619
- Joined: January 15th, 2003, 3:41 pm
- Location: Barcelona
- Contact:
- CatThief
- Posts: 1854
- Joined: January 19th, 2004, 12:19 am
- Location: Northeast USA
- mai9
- Posts: 1619
- Joined: January 15th, 2003, 3:41 pm
- Location: Barcelona
- Contact:
- mai9
- Posts: 1619
- Joined: January 15th, 2003, 3:41 pm
- Location: Barcelona
- Contact:
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
I have managed to 'port' the Dom inspector to the 20040801 build... So, its doable but NOT easy tho
NOT FOR THE FAINT OF HEART
I basically took pieces of what comprises the DOM inspector from vaious builds until something worked (properly)
you will need :
inspector.jar ( TB ver NOT FF ver) from the most recent TB build that had it
winInspectorMain.ico ( goes in tbappdir\chrome\iconsdefault )
inspector.dll ( goes in TBappdir\components.. ver 1.7.20040.14587 works for me )
inspector.xpt ( goes in TBappdir\components )
inspector-cmdline.js ( goes in TBappdir\components )
inspector.js ( goes in TBappdir\defaults\pref )
the inspector GUID folder from FF ( goes in TBappdir\extensions )
the inspector folder ( that goes in TBappdir\res.. get it from the last TB build to have the DOM inspector )
you *might* need gkgfx.dll to be in TBappdir as well ..
before you run TB,
be shure to delete the TBappdir\chrome\chrome.rdf that will recreate the entries in the correct overlayinfo folders
be shure to delete the TBappdir\components\xpti.dat TB will recreate it correctly
be shure to delete the TBappdir\components\compreg.dat TB will recreate it correctly
if something is still broken, check if there are any entries for the DOM inspector in your profile
there should be ( it is on mine anyway )
<RDF:Description RDF:about="urn:mozilla:package:inspector">
<c:selectedLocale RDF:resource="urn:mozilla:locale:en-US:inspector"/>
<c:selectedSkin RDF:resource="urn:mozilla:skin:classic/1.0:inspector"/>
</RDF:Description>
in the chrome.rdf of your profile
38,inspector.xpt,0,2980,1086739864000
in your xpti.dat file ( you might have to mess with the item number )
lots of entries in the compreg.dat file ( i *think* you can delete the file and have TB recreate it )
PLEASE don't hold me responsible for screwing up your install, just b/u everthing and you should be fine
EDIT: turns out you also need to delete the XUL.mfl file too
Good Luck
NOT FOR THE FAINT OF HEART
I basically took pieces of what comprises the DOM inspector from vaious builds until something worked (properly)
you will need :
inspector.jar ( TB ver NOT FF ver) from the most recent TB build that had it
winInspectorMain.ico ( goes in tbappdir\chrome\iconsdefault )
inspector.dll ( goes in TBappdir\components.. ver 1.7.20040.14587 works for me )
inspector.xpt ( goes in TBappdir\components )
inspector-cmdline.js ( goes in TBappdir\components )
inspector.js ( goes in TBappdir\defaults\pref )
the inspector GUID folder from FF ( goes in TBappdir\extensions )
the inspector folder ( that goes in TBappdir\res.. get it from the last TB build to have the DOM inspector )
you *might* need gkgfx.dll to be in TBappdir as well ..
before you run TB,
be shure to delete the TBappdir\chrome\chrome.rdf that will recreate the entries in the correct overlayinfo folders
be shure to delete the TBappdir\components\xpti.dat TB will recreate it correctly
be shure to delete the TBappdir\components\compreg.dat TB will recreate it correctly
if something is still broken, check if there are any entries for the DOM inspector in your profile
there should be ( it is on mine anyway )
<RDF:Description RDF:about="urn:mozilla:package:inspector">
<c:selectedLocale RDF:resource="urn:mozilla:locale:en-US:inspector"/>
<c:selectedSkin RDF:resource="urn:mozilla:skin:classic/1.0:inspector"/>
</RDF:Description>
in the chrome.rdf of your profile
38,inspector.xpt,0,2980,1086739864000
in your xpti.dat file ( you might have to mess with the item number )
lots of entries in the compreg.dat file ( i *think* you can delete the file and have TB recreate it )
PLEASE don't hold me responsible for screwing up your install, just b/u everthing and you should be fine
EDIT: turns out you also need to delete the XUL.mfl file too
Good Luck
- mai9
- Posts: 1619
- Joined: January 15th, 2003, 3:41 pm
- Location: Barcelona
- Contact:
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
- mai9
- Posts: 1619
- Joined: January 15th, 2003, 3:41 pm
- Location: Barcelona
- Contact:
-
- Posts: 0
- Joined: December 31st, 1969, 5:00 pm
Ok, I *think* I have it sorted...
I have made an XPI but have only tested it in my environ and *seems* to work
What I did to test is deleted my TB app dir completely ( profile was untouched )
try to install the inspector.xpi and although it did NOT show up the the EM, the 'DOM inspector' menu option *did* appear in the tools menu following a TB restart..
The Dom inspector *seems* to work ( can navigate nodes and all )
the xpi is at www.supportware.net/mozilla/inspector.xpi
Good luck
EDIT: the extension that I repackaged is ONLY for TB as the new TB versions do NOT include the DOM inspector ( I *am* talking about zip builds )
I have made an XPI but have only tested it in my environ and *seems* to work
What I did to test is deleted my TB app dir completely ( profile was untouched )
try to install the inspector.xpi and although it did NOT show up the the EM, the 'DOM inspector' menu option *did* appear in the tools menu following a TB restart..
The Dom inspector *seems* to work ( can navigate nodes and all )
the xpi is at www.supportware.net/mozilla/inspector.xpi
Good luck
EDIT: the extension that I repackaged is ONLY for TB as the new TB versions do NOT include the DOM inspector ( I *am* talking about zip builds )
Last edited by Old Ausdilecce on August 7th, 2004, 1:15 am, edited 1 time in total.
- Kasteo
- Posts: 670
- Joined: August 24th, 2003, 9:16 am
- Location: Thailand
Amazing... It works. Thank you, I thought I would never seen DOM Inspector in the Thunderbird again.
Noia 2.0 theme for Firefox & Thunderbird
- Compaq Presario 2190US, 2.4GHz, 1024MB DDR RAM, 40GB 5400rpm HDD.
- Windows Server 2003 Enterprise, Gecko/20040925 Firefox/0.10 (MOOX M3)
- Compaq Presario 2190US, 2.4GHz, 1024MB DDR RAM, 40GB 5400rpm HDD.
- Windows Server 2003 Enterprise, Gecko/20040925 Firefox/0.10 (MOOX M3)