MCBastos <[email protected]> wrote:
> Interesting post about preference dialogs:
>
> <http://limi.net/checkboxes-that-kill>
>
> Food for thought. That was about Firefox, but Seamonkey has probably
> even more options exposed through the main preferences interface. Are
> there some of them that should be hidden because they do more harm than
> good?
>
> I used to work under the assumption that Seamonkey is mostly used by
> power-users who use it exactly for those exposed features, but recently
> posted statistics show a large drop of SM usage on weekends --
> suggesting those users use SM only at work, and something else at home.
> That is, they don't use SM by choice, but because it's company policy.
> Those groups of users would benefit from a streamlined, idiot-proofed
> preferences system.
We already have that!
During installation, add a file like this (with .js extension) into
the installdir\defaults\pref directory:
// mozilla.cfg forced settings
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
In the installdir, add a file mozilla.cfg structured like this:
// Locked preferences for Mozilla SeaMonkey
try {
lockPref("app.update.auto", false);
lockPref("app.update.enabled", false);
lockPref("app.updatecheck.override", true);
lockPref("xpinstall.enabled", false);
} catch(e) {
displayError("lockedPref", e);
}
(just some examples, add any pref that you want to lock)
Result: the prefs cannot be changed by the user, the UI will show
"disabled" checkmarks and input fields.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
