On 17/12/10 07:14, Manolo Gouy wrote: >> (Matt said) >> 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: .... > > I think that putting an application with real effects in the test > directory is wrong even with password protection. The user can > believe the password query is a demo to illustrate how an FLTK > application can have password-protected features.
I agree with Manolo - I do not think we should put anything with "real" effects into the test/ or examples/ dirs, as someone (maybe most people) will use them without realising that they have actual, real, effects. > The 3rd option seems quite good. The new Fluid dialog can be > announced in the Doxygen doc of Fl::options(). Thus, prospective > users of it would be informed of how to proceed. If we can't have a real "app for that", and given the timescales I don't think we can, then this seems like a feasible option since it is clear that it is not simply a demo. I concede that fluid having this additional "non-UI-design" function does not seem very discoverable. Is there a clear demand for this functionality though? I know I have not encountered much with my users in this area - though I concede that my user-base is atypical, so not very representative. <aside> Since my users are all highly technical, support tends to be limited to mocking them for not instinctively knowing how to use the tool, rather than actually making things easier to use... ;-) </aside> _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
