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

Koodankulam - another ISRO? And best critic from John Rubert

Mahendragiri ISRO is situated close to my hometown and now Koodankulam ... When ISRO was started, there were no industries. At that time, everyone was happy about the project as many believed that it would create more employment opportunities. (As per some conspiracy theories, Kanyakumari was sidelined for being Congress-fort then). Later on few guys got job there... and later on they complained that they're been transferred to other place for being local guys--by Anti-Tamil seniors. Few months ago, an Engineer from Secundrabad who's working in ISRO joined me in train. The guy shared some information... he's recruited/recommended by his Secundrabad colleague, his ambition is to work in NASA, his job is just to check meter and make a note of it..., many guys have similar boring jobs... Anybody who's complaining IT guys should talk to these ISRO guys! ISRO is a big example on how Indian government is spending crores of rupees lavishly. Majority of the projects--ac...
4 comments
Read more

Storing unicode texts in MySQL with phpMyAdmin

Today, I've received a personal mail/request from Sivanantham Hemamalini, working for IT leisure in Singapore. Since I was in company when received the mail, I couldn't answer immediately. If I understand the question right, it is about inputting Unicode texts especially Tamil in phpMyAdmin. PhpMyAdmin 's default characterset is iso-8859-1 and so if we enter anything in the form, browser will convert it into numerical html entities. Say for example, if we enter தமிà®´் and submit the form, it will convert it to & #2980;& #2990;& #3007;& #2996;& #3021; . Because of this browser's behavior, it will be difficult to store the Unicode text as it is. Solutions Immediate solution I could think of is changing or forcing the browser's character encoding into utf-8. In Mozilla Firefox, it can be set via View -> Character Encoding -> Unicode (UTF-8) Another elegant solution might be changing the phpMyAdmin configurations so that it send...
3 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