Quote:
Originally Posted by nekokami
I used to use custom profiles with earlier versions when several of us were using the same machine. I haven't used them in a while, but I suppose I could set them up for this purpose.
|
I find them extremely handy, and one of the big features of Firefox. I can do things like have a plain vanilla install copy I can use as a reference.
It's the sort of thing tailor-made for what you do, when you need to see things like your students will, but will still like to customize the version you use.
Quote:
I won't need collections of bookmarks to be shared between profiles, fortunately. The funny thing is, I'd think using a database would handle potential collisions better than a flat file. 
|
Some of the folks complaining think so too, and believe sqlite databases have "atomic" commits, so multiple browsers could theoretically access the same bookmarks file simultaneously.
I have a fair work around here. I use a freeware tool to create hard links to the places.sqlite file in each profile, which takes care of FF3 instances. I still have FF2, Mozilla Suite, Netscape and Flock installed, and those use the bookmarks.html file. To handle those, I went into about
:config and toggled the preference
browser.bookmarks.autoExportHTML to True. The location where Firefox will put the bookmarks.html file is controlled by the user.js file I mentioned in my earlier post.
So every time I exit Firefox, it exports the places.sqlite file to the desired bookmarks.html file. Older browsers that use bookmarks.html are pointed at that file by the user.js file, and they all see the latest and greatest version.
Unfortunately. it's one way. If I make changes in one of the older browsers, they won't be propagated to places.sqlite, and will be overwritten by the backup the next time I use FF3. That's not a deal-breaker, because I don't use them that often, and if I see a site I want to bookmark while using one, I drag the URL to my desktop, then import it to FF3 the next time I run it.
______
Dennis