Forgot your password?
typodupeerror
Mozilla

Let Older Add-Ons Work With Firefox 3.0 164

mask.of.sanity informs us of a hack that allows old add-ons to work with Firefox 3.0. Short form: in about:config, create a new boolean and set extensions.checkCompatibility to false. "The fix, which requires a little boolean creativity, great for anyone not afraid of taking risks. The idea is to stop Firefox checking its version history, allowing defunct extensions to work... [Those who do] get the fix working will have to remove the code from the prefs.js file once the stable Firefox comes out, but will enjoy their [favorite extensions] in the meantime."

Comment Real life test for developpers (Score 1) 1229

Since the original question was about development I just made some test with an lib I'm working on. I compile the same source with the same build system (gnu make + gcc 3) on a PIII 600 Linux box and an iBook G3 700 machine. The iBook compiles in 6m45s when the Linux box compiles the lib in 1m55s. I also tried to compile the code on an external FireWire 7200rpm HD with exactly the same results just be sure the laptop wasn't lagging on the disk side. I did the same compilation on my PIV 1.6Ghz Dell Laptop with VC.NET and it took 2m30s to compile the lib on the internal disk (WinXP Pro). I think compilation times are quite revelent to using a box as a dev machine or not and in my case I think the choice is quite easy to make.

Slashdot Top Deals

Term, holidays, term, holidays, till we leave school, and then work, work, work till we die. -- C.S. Lewis

Working...