On 16.12.2010, at 23:56, Matthias Melcher wrote: > > OK, so for 1.3 we have introduced user configurable settings, globally and > per user. > > In order to have a program that changes these settings, I have modified > test/preferences. But this program is now easily confused for some demo, > causing the user to change system wide settings, and later wondering why the > visible focus is gone in all FLTK apps. > > Please comment on your preferred solution:
Generally I would avoid asking the user for a password. Instead, we could popup a dialog that warns the user that he's now entering a real (system) setup dialog - probably like a splash screen that must be confirmed when the program or the dialog is started. If we need system rights, then we should tell the user about it, and that's IMHO enough. > 1a: the menu at the bottom left has three settings: demo, user, system. > Changing away from "demo" requires the password > 2: create a new application (suggested name "Flavor"), parallel to Fluid, > with the same directory structure and Makefile setup. This will make it > obvious to the user that this is a "serious" app, and not just a test. This > is also a lot of work... . > 3: add an FLTK settings dialog to Fluid. Easy, quick, but not obvious at all. My f(l)avorite (pun intended) option is (2) w/o a password but with a warning as described above. In this case we could warn the user only when he really writes the changes. This should not be done with a simple OKAY button - I suggest something like "write setup options" or similar. BTW.: flavor is cute, but maybe flsetup or similar would better show what it really is: a setup program. My 2nd choice would be (3), 3rd would be (1a), but with a warning only instead of a password. If we choose (2), I could maybe try to help with makefile additions for the new program, maybe also CMake, but I'm not sure about the latter. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
