How about: 4. Remove settings from preferences and provide a command-line tool (fltk-options?) that allows a user to make changes to the per-user (for non-root) or global (for root) settings.
I can see adding options to FLUID for its own use, but not for applying to all apps. On Dec 16, 2010, at 5:54 PM, 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: > > > 1: changing the settings requires the user password or system password. This > will make the casula user stop and think, but it is quite uncomfortable. > > 1a: the menu at the bottom left has three settings: demo, user, system. > Changing away from "demo" requires the password > > 1b: the user can change all settings, but only when he finally clicks OK< we > ask for the password > > 1c: a visual lock icon must be clicked and the PW must be entered before any > changes can be done. Until then, everything is grayed out. > > > 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... . > > 2a: ... *and* ask for a password, options as above > > > 3: add an FLTK settings dialog to Fluid. Easy, quick, but not obvious at all. > _______________________________________________ > fltk-dev mailing list > [email protected] > http://lists.easysw.com/mailman/listinfo/fltk-dev ________________________________________ Michael Sweet, Easy Software Products _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
