Xfce Wiki

Sub domains
 

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
dev:system-wide-settings [2009/11/14 23:18] – Punctuation kitchmdev:system-wide-settings [2009/12/18 20:52] 198.103.172.9
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=====
Line 66: Line 66:
 ^System Level ^Belongs To ^Interfaced By ^ ^System Level ^Belongs To ^Interfaced By ^
 |Desktop Environment|Xfce|**Xfce4 Settings Manager**, **Time and Date**| |Desktop Environment|Xfce|**Xfce4 Settings Manager**, **Time and Date**|
-|Widget Toolkit subsystem|GUI|GTK+2 +|Widget Toolkit subsystem|GUI|GTK+2| 
-|Window Manager subsystem|GUI|Xfwm +|Window Manager subsystem|GUI|Xfwm| 
-|Windowing System subsystem|GUI| +|Windowing System subsystem|GUI
-|Graphics Server subsystem|GUI| +|Graphics Server subsystem|GUI
-|X Graphical Interface or GUI|X Window System|xorg.conf, **Screensaver** (XScreenSaver)|+|X Graphical Interface or GUI (if used)|X Window System|xorg.conf, **Screensaver** (XScreenSaver)
 +|Framebuffer (if used)|OS video|CLI|
 |Network System|OS|file manager, browser, email client, Samba| |Network System|OS|file manager, browser, email client, Samba|
 |The Storage and File Management System|OS|file manager| |The Storage and File Management System|OS|file manager|
-|Framebuffer (if used)|OS video|CLI| 
 |Operating System(OS)|self|CLI| |Operating System(OS)|self|CLI|
  
Line 106: Line 106:
 |Appearance-Settings Tab|Move to Desktop-Panel tab|These settings all appear to be panel-related.| |Appearance-Settings Tab|Move to Desktop-Panel tab|These settings all appear to be panel-related.|
 |Hardware|Create New|Group all hardware items here| |Hardware|Create New|Group all hardware items here|
-|Display|Move to Hardware as tab|Entitle it Xorg Display.+|Display|Move to Hardware as tab|Entitle it Xorg Display.|
 |Mouse|Move to Hardware as tab| | |Mouse|Move to Hardware as tab| |
 |Keyboard|Move to Hardware as tab| | |Keyboard|Move to Hardware as tab| |
Line 113: Line 113:
 |Notifications|Move to Desktop|Is a part of the desktop| |Notifications|Move to Desktop|Is a part of the desktop|
 |Panel|Move to Desktop|This is really part of the arrangement of the desktop| |Panel|Move to Desktop|This is really part of the arrangement of the desktop|
-|Power Manager|Move to Hardware(?)|Hard to say about this.  It is pretty unique.  Needs to be expanded to have better control with lower level in the OS to handle shutdowns and suspend to disk or RAM| +|Power Manager|Move to Hardware(?)|Hard to say about this.  It is pretty unique.  Needs to be expanded to have better control over the lower levels in the OS, so as to handle shutdowns and suspend to disk or RAM in a more intuitive manner.
-|Preferred Applications|Expand Options|Also pretty unique.  Needs more options.|+|Preferred Applications|Expand Options|Also pretty unique.  Needs more options.  There must be a dozen more than just the three categories listed.  ie, where is the PDF viewer?|
 |Printing|Move to Hardware| | |Printing|Move to Hardware| |
 |Removable Drives and Media|Move to Hardware| | |Removable Drives and Media|Move to Hardware| |
Line 120: Line 120:
 |Window Manager|Move to Desktop|As much as people like to see it as separate, to the user it will always remain as part of the DE| |Window Manager|Move to Desktop|As much as people like to see it as separate, to the user it will always remain as part of the DE|
 |Window Manager Tweaks|Move to Desktop|"| |Window Manager Tweaks|Move to Desktop|"|
-|Workspaces|Move to Desktop| |+|Workspaces|Move to Desktop|"|
  
  \\  \\