A question about the DJGM.co.uk Toolbar . . .

A section for all development and testing programmes and customised browsers written by SillyDog701 community. Featured products including Donzilla, Firescape, DJGM Distro, and Netscape Streamline.

Moderator: Don_HH2K

A question about the DJGM.co.uk Toolbar . . .

Postby DJGM » Thu 26 Jan, 2006 7:33 pm

Several weeks ago, I released the DJGM.co.uk Toolbar v1.0, but for Firefox only. Now that I've
upgraded/migrated from Mozilla App-Suite 1.7.12, to Seamonkey 1.0 beta as my primary web
browser, I'd like to make the toolbar available to install as a SeaMonkey extension.

Any idea how I should go about doing this? Would anyone be willing to help me out with this?
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8) Gecko/20051219 SeaMonkey/1.0b
SeaMonkey = Swiss Army Knife: It's versatile, reliable, and contains useful tools.
Windows Internet Explorer = Old Swiss Cheese: Full of holes, and it stinks!
User avatar
DJGM
diamond member
diamond member
 
Posts: 4550
Joined: Wed 19 Jun, 2002 1:03 pm
Location: Manchester, England, UK

Postby Don_HH2K » Thu 26 Jan, 2006 8:00 pm

I'd be willing to help.

As for going about porting it, there may not be a lot of work that needs to be done. First, you should see how much of it works in Seamonkey; try placing the .jarfile for the Toolbar in seamonkey/chrome, then manually register the JAR to Seamonkey in installed-chrome.txt using the same syntax that the preexisting entries follow, basing it on the JAR file's directory structure. So, let's say you had [tt]toolbar.jar!/content/chrome.rdf[/tt] and [tt]toolbar.jar!/locale/en-GB/locale/chrome.rdf[/tt], you'd add those into installed-chrome.txt like this:
Code: Select all
content,install,url,jar:resource:/chrome/toolbar.jar!/content/
locale,install,url,jar:resource:/chrome/toolbar.jar!/locale/en-GB/locale/


Then delete [tt]chrome.rdf[/tt], [tt]overlays.rdf[/tt], and [tt]stylesheets.rdf[/tt] from seamonkey/chrome (they will be rebuilt on launch) and fire up Seamonkey.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051205 Donzilla/1.0 (WML/1.3)
Laptop: HP Compaq nx6325 - Turion 64 X2 @ 2GHz, 2GB DDR2, 100GB HD, ATI Radeon X300, 15" LCD, Seven Pro
Handheld: Palm Treo 650 - Intel PXA270 @ 312MHz, 10MB RAM, 32MB flash, 2.7" LCD, Palm OS 5.4
User avatar
Don_HH2K
Moderator
Moderator
 
Posts: 5112
Joined: Sun 09 May, 2004 3:59 pm

Postby DJGM » Thu 26 Jan, 2006 8:40 pm

I was wondering ... since Mozilla App-Suite and SeaMonkey both use install.js script files for the
installation of extensions/themes would it work if I added an install.js file to the existing XPI?

If so, what would need to be written in the install.js file, or could I edit an existing install.js file
from a similar extension, such as the Netscape Toolbar that was bundled with Netscape 7.2.
UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8) Gecko/20051219 SeaMonkey/1.0b
SeaMonkey = Swiss Army Knife: It's versatile, reliable, and contains useful tools.
Windows Internet Explorer = Old Swiss Cheese: Full of holes, and it stinks!
User avatar
DJGM
diamond member
diamond member
 
Posts: 4550
Joined: Wed 19 Jun, 2002 1:03 pm
Location: Manchester, England, UK

Postby Don_HH2K » Fri 27 Jan, 2006 11:37 am

You may want to take a look at XPIMaker, which can be used to create XPI files. I've never used it before, so I don't know how much of the XPI-building process it performs for you.

Mozilla also has a guide to making install.js files compatible with Mozilla Suite XPIs available on the XPInstaller project homepage.
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Laptop: HP Compaq nx6325 - Turion 64 X2 @ 2GHz, 2GB DDR2, 100GB HD, ATI Radeon X300, 15" LCD, Seven Pro
Handheld: Palm Treo 650 - Intel PXA270 @ 312MHz, 10MB RAM, 32MB flash, 2.7" LCD, Palm OS 5.4
User avatar
Don_HH2K
Moderator
Moderator
 
Posts: 5112
Joined: Sun 09 May, 2004 3:59 pm


Return to SD701 DevZone

Who is online

Registered users: Google [Bot]