Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:system-wide-settings [2009/11/14 23:35]
kitchm Edit
dev:system-wide-settings [2010/10/02 17:26] (current)
Line 4: Line 4:
 =====Introduction===== =====Introduction=====
  
-As the title implies, this category is an attempt to bring together all various system settings into one simple interface. ​ It will seek to suggest ​that each component programmer be allowed to continue to focus upon their own individual modular component of the whole, while at the same time, bringing together some sort of standardized method for reaching out to each module and interfacing with the settings ​of said module as appropriate for centralizing control.+As the title implies, this category is an attempt to bring together all the various system settings into one simple interface. ​Its goal is that each component programmer be allowed to continue to focus upon their own individual modular component of the whole, while at the same time, bringing together some sort of standardized method for reaching out to each module and interfacing with its settings for the purpose ​of centralizing control.
  
-Further, this roadmap will be useful in eliminating those desparate ​mechanisms of settings control that lead to odd behavior, overlapping subjects and loss of user control. ​ Important as simplicity of user interface (intuitiveness) may be, eliminating unnecessary buggy behavior across the whole desktop environment is of paramount import, and hopefully will be largely addressed by this effort. ​ It is possible to eliminate a large portion of bugs by just simplifying and standardizing. ​ That can be win/win all the way down the road.+Further, this roadmap will be useful in eliminating those disparate ​mechanisms of settings control that lead to odd behavior, overlapping subjects and loss of user control. Important as simplicity of user interface (intuitiveness) may be, eliminating unnecessary buggy behavior across the whole desktop environment is of paramount import, and hopefully will be largely addressed by this effort. It is possible to eliminate a large portion of bugs by just simplifying and standardizing. That can be win/win all the way down the road.
  
-We will here attempt to bring together ​first an overview of the issue from the standpoint of the user, followed by a suggested description of a possible solution, and a concise discussion with a focus upon creating a concensus ​and roadmap.+We will here attempt to first bring together an overview of the issue from the standpoint of the user, followed by a suggested description of a possible solution, and a concise discussion with a focus upon creating a consensus ​and roadmap.
  
-Note: It is not necessary to discuss the issue of whether or not some problem exists, but rather note the user'experiences,​ and address ​it with a desire to improve that experience and make it ever more "​goof-proof"​. ​ The old adadage ​that states, "If it ain't broke, don't fix it" has always been misleading and is no friend to programmers. ​ The proper way to view it is to recognize that nothing is perfect and that everything can be improved. ​ That should be our goal here, so that when nothing else is being accomplished, ​polishing of the product will always ​take place. ​ Programmers can know they'​re on the right track when they cease hearing a user state something like "Where is the #​@!$&​%ing location to set my preferred PDF viewer? I'm tired of seeing GIMP start up instead!"​.+Note: It is not necessary to discuss the issue of whether or not some problem exists, but rather ​to note the users' experiences,​ and address ​them with a desire to improve that experience and make it ever more "​goof-proof"​. The old adage that states, "If it ain't broke, don't fix it" has always been misleading and is no friend to programmers. The proper way to view it is to recognize that nothing is perfect and that everything can be improved. That should be our goal here, so that polishing of the product will always ​be taking ​place. Programmers can know they'​re on the right track when they cease hearing a user state something like "Where is the #​@!$&​%ing location to set my preferred PDF viewer? I'm tired of seeing GIMP start up instead!"​.
  
-All are welcome to submit here.  ​Programmers and users alike. ​ Please take your discussion to the links indicate so that we can keep this neat.  Thank you all.+All are welcome to submit hereProgrammers and users alike. Please take your discussion to the links indicate so that we can keep this neat. Thank you all.
  
 =====Overview===== =====Overview=====