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.
Joel Kitching:

Thanks for the info. Anyway, now I'm used up with Deer Park Alpha icons:)
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...

Popular posts from this blog

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI