Re: Lockdown stuff

["Seth Nickell" <seth gnome org>]

You have to make it clear *why* something is disabled or people can and 
will waste endless time on it. HIG has examples for gconf-locked 
settings, I believe.

-seth

On Thu, 16 Oct 2003 1:57AM -0800, Ross Burton wrote:
> On Thu, 2003-10-09 at 01:35, Markus Berg wrote:
> >  It would be nice to have a UI for setting mandatory gconf-settings
>
> I'm very late into this thread...
>
> gconf-editor has a "Set as Default" entry in the right-click menu,
> adding "Set as Mandatory" should be about 10 minutes work, if you copy
> and paste. At this point gconf-editor will need a preferences dialog so
> you can set the "default" and "mandatory" paths, without having to run
> ./configure again.  Maybe the entry should read "Set explicit source"
> and allow you to pick from the sources available.
>
> >  and that the final UI would reflect the
> >  locked-down status.  For instance if Nautilus (and the control panel)
> >  would remove the "Desktop background" menu items if those gconf-keys 
> > are
> >  read-only.
>
> The examples I've seen of lock-down in GNOME tend to disable instead of
> hide the widgets.  Personally I'm not sure what is better -- from a
> support point of view I'd say disabling would be more obvious, as
> settings are not "magically" disappearing.
>
> Ross
> --
> Ross Burton                                 mail: ross burtonini com
>                                           jabber: ross burtonini com
>                                      www: http://www.burtonini.com./
>  PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
>
> _______________________________________________
> desktop-devel-list mailing list
> desktop-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/desktop-devel-list
-Seth