Some Code
I know I don't post here nearly enough, however. I managed to get a little work done thanks to a little prompting, be it passive, by an older writeup from 
firefox_fangirl . A number of factors have finally got me to download the beta of FF4, but this time I decided to be a little intelligent about it. In the past I've installed them side by side which has amounted to little less then an absolute headache for some as lazy as I am to manage between preference conflicts and trying to run them side by side. Separating them out once the beta has gone gold proves to be another adventure in self loathing.
As a result I decided to just run FFPortable (running the Beta for 4) directly from the hard-drive. The one thing that bothered me about it was that there was a total lack of support built in for multiple profiles, which is something I make ... relatively heavy use of. In general, I have these profiles available.firefox_fangirl 's writeup at lifehacker. While all had their merits, I found many of them to be inelegant, or a bit too much work for someone as lazy as I. The Lifehacker writeup was pretty close to what I wanted, but it was a little involved and I had my concerns about wasting disk-space with multiple copies of the binaries (not that I don't have the space, I am just lazy and don't want to have to worry about it later).
Between all the information available it was pretty easy to see that some manipulation of the ini file to FFPortable would yield the results I want, but best way would be to do it through a gui. So I grabbed a copy of AutoHotkey and got to work. So here are the fruits of a Friday afternoon. It's definitely got a few things that can be added to it, and it's not in an executable form; although it's really simple to compile. Just install AutoHotKey, copy the code and place it in a text file named FFPortable-Manager.ahk, save the text-file, right-click and compile.
A small side note, I am not sure how much space I actually managed to save in disk-space, as there seems to be some IO issue dealing with the URLclassifier flat-file that makes it balloon to ridiculous sizes, I'll have to poke around and see if I can at least convince FF to use a shared file for all the profiles.
Obviously, due to the manipulation of the ini file this will NOT run off a CD as is, although I may produce a version using some quick copying to the temp directory that would accomplish the same.
Final note, is that currently it if you happen to run the portable executable instead of the manager it runs the last profile that was used. This is currently consistent with how vanilla Firefox works (give or take a few circumstances). Personally, I am thinking of changing this so that it runs any profile named Default so if you should decide to make the portable your default url handler the Default gets any url clicks from external programs.
firefox_fangirl . A number of factors have finally got me to download the beta of FF4, but this time I decided to be a little intelligent about it. In the past I've installed them side by side which has amounted to little less then an absolute headache for some as lazy as I am to manage between preference conflicts and trying to run them side by side. Separating them out once the beta has gone gold proves to be another adventure in self loathing.As a result I decided to just run FFPortable (running the Beta for 4) directly from the hard-drive. The one thing that bothered me about it was that there was a total lack of support built in for multiple profiles, which is something I make ... relatively heavy use of. In general, I have these profiles available.
- Personal
- Work
- GV/GC - Personal
- GV/GC - Work
- Q/A (Not used much since my job in 2008)
firefox_fangirl 's writeup at lifehacker. While all had their merits, I found many of them to be inelegant, or a bit too much work for someone as lazy as I. The Lifehacker writeup was pretty close to what I wanted, but it was a little involved and I had my concerns about wasting disk-space with multiple copies of the binaries (not that I don't have the space, I am just lazy and don't want to have to worry about it later). Between all the information available it was pretty easy to see that some manipulation of the ini file to FFPortable would yield the results I want, but best way would be to do it through a gui. So I grabbed a copy of AutoHotkey and got to work. So here are the fruits of a Friday afternoon. It's definitely got a few things that can be added to it, and it's not in an executable form; although it's really simple to compile. Just install AutoHotKey, copy the code and place it in a text file named FFPortable-Manager.ahk, save the text-file, right-click and compile.
A small side note, I am not sure how much space I actually managed to save in disk-space, as there seems to be some IO issue dealing with the URLclassifier flat-file that makes it balloon to ridiculous sizes, I'll have to poke around and see if I can at least convince FF to use a shared file for all the profiles.
Obviously, due to the manipulation of the ini file this will NOT run off a CD as is, although I may produce a version using some quick copying to the temp directory that would accomplish the same.
Final note, is that currently it if you happen to run the portable executable instead of the manager it runs the last profile that was used. This is currently consistent with how vanilla Firefox works (give or take a few circumstances). Personally, I am thinking of changing this so that it runs any profile named Default so if you should decide to make the portable your default url handler the Default gets any url clicks from external programs.
-
-
accomplished
-