Perhaps the developers could take a look at the prefs/options for IE, Safari, and OmniWeb (the main OS X competition, yes?) and if there's a pref/option that's in *all 3* -- make it plainly visible in the "easy" portion of Camino's options. And also make plainly visible, whatever options we vote for.
And then put the other stuff in some "Advanced" or "Esoteric" grouping, or a sub-grouping within that.
Ed Mechem hit it on the head.. why not do what Eudora does? i.e. have the most common preferences exposed and available via the GUI prefs dialog. Then have something akin to Eudora's x-settings.
It could start as a simple listing of all the the things one CAN specify. I've tried to "look around" but there seems to be no place which hosts a list of all the possible "user.js" settings and what they mean. Qualcomm DOES provide a list like that in addition to having a mechanism for actually setting those "hidden" prefs. As I said, I'd be happy with the list and I'll add them manually myself.
An easy mechanism (other than directly adding them to "user.js") would then be a feature request. But if we HAD such a comprehensive listing, we still be way ahead of the game.
BUT, there IS one big downside to the way Eudora does this. There is NO mechanism to retrieve any form of comprehensive list of exactly what all those settings are. This CAN become and issue if you are troubleshooting and need to "delete prefs." That may very well fix any application specific troubles, but now one is left with having to re-figure out all your x-settings.
For Camino, using an ASCII file is spot on and deals with the "need to toss the prefs" issue.
_______________________________________________
Camino mailing list
[EMAIL PROTECTED]
http://mozdev.org/mailman/listinfo/camino
