Skip to main content

Getting Deer Park Alpha 1 extensions

I've finally decided to test Mozilla Deer Park Alpha 1 (Firefox 1.1a1). The browser is really cool. They've changed the icon/logo--this is sometimes confusing. Apart from that, the major problem is incompatibility with existing extensions--which can mostly be solved by bumping targetApplication's maxVersion.

I did bumping for few extensions, but finally decided to search for a bit. Interestingly I found few wonderful resources; the best among is 'Unarmed' of mozillaZine forum's PHP script and his online service. The online bumping service is really great; it gets the URL of the extension and the version to be applied in the GET and gives you the bumped/hacked extension. Many extensions worked well--including the popular Web Developer / Webdeveloper extension ; sadly the HTML Validator extension didn't work even after bumping.

Having heavily inspired by the online bumping service, I have written a bookmarklet to access the service. I think the PHP script can be improved especially to handle redirect with CURLOPT_FOLLOWLOCATION. Anyway, it's a nice idea that PHP is used for repackaging XPI; that is to unpack/unzip the XPI files using PEAR Archive_Zip, fix the maxVersion in install.rdf and then packing/zipping it.

Bookmarklet

Links

Comments

Anonymous said…
I believe the icon is just for nightly, alpha and beta builds. So expect the icon to revert to its former self in the final 1.5 version.
Jul 28, 2005, 2:56:00 AM
R. Rajesh Jeba Anbiah said…
Joel Kitching:

Thanks for the info. Anyway, now I'm used up with Deer Park Alpha icons:)
Jul 28, 2005, 10:14:00 AM
Anonymous said…
Those people at google sure are nasty when it comes to version checks. I've tried every possible way I could find, but still haven't been able to get the new google toolbar working under Deer Park...
Oct 6, 2005, 3:06:00 PM
Post a Comment

Popular posts from this blog

Converting PSD with PHP/ImageMagick

After seeing feature rich options in Imagick PECL extension at Mikko Koppanen 's (the author) website and also impressed with ImageMagick 's features, I have decided to use it for the PSD to XHTML conversion website that I'm architecting and managing. Since, the team wants programming help for converting PSD images, I have tried it (documentation is sparse on PSD handling) Converting PSD to PNG/JPEG/etc Note that, flattenImages() is needed for layered/multi-page PSD file. <?php $im = new Imagick('test.psd'); $im->flattenImages(); $im->setImageFormat('png'); $im->writeImage('test.png'); ?> Extracting PSD layers One by one <?php $im = new Imagick('test.psd'); $im->setImageFormat('png'); for ($i = 0, $num_layers = $im->getNumberImages(); $i $im->setImageIndex($i); $im->writeImage('layer' . $i . '.png'); } ?> Note that, there is a better version below In a single call with writeIm...
5 comments
Read more

Google used PHP?

I wanted to know what are the pages in Google are powered by PHP . I have tried various keywords including "inurl"--but it produced huge list. So I tried "filetype:php" and it worked very nice. The real keywords are php filetype:php site:google.com Google used PHP?
2 comments
Read more

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...
Post a Comment
Read more