One last thought on this, perhaps a selection list of features to place into a *hidden* menu that was password protected would be easier to implement at configure time. I'll play around with the idea when I get time.
Apologies, please forgive my mailing list ignorance. On Mon, Oct 21, 2013 at 6:07 AM, Frank Gevaerts <fr...@gevaerts.be> wrote: > On Mon, Oct 21, 2013 at 06:01:13AM -0400, benjamin brown wrote: > > Should this be a custom build or should it we make it an option in the > > configure script, something like a kids mode or safe mode option. I'm > all > > for an easy fix to raise the quality of life for someone, but there is > more > > than one person in the world that can benefit from this. Understandably > > the features that need disabled are not going to be the same for > everyone, > > perhaps a graduating scale could be implemented "safe, safer, safest". > > It's just something to think about. > > It is indeed something to think about, but historically settings that > disable UI functionality have been *very* contentious. > > Frank > > PS: please don't top-post on this list > > > > -- > "Debugging is twice as hard as writing the code in the first place. > Therefore, if you write the code as cleverly as possible, you are, > by definition, not smart enough to debug it." - Brian W. Kernighan >
