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
dev:system-wide-settings:solution-discussion [2010/03/17 02:05] – Reply kitchmdev:system-wide-settings:solution-discussion [2010/10/02 17:26] (current) – external edit 127.0.0.1
Line 40: Line 40:
 >However, I can address the point about modules.  As I understand it, the meaning behind the use of the term "module" is a program that has no GUI and performs a particular task under the DE. The Settings Manager is their front end or GUI.  I can find no need for any type of modules that are needing any type of visualization on their own.  Therefore, there is no need for any reworking of any kind.  They simply loose their existing UI's as completely redundant.  This is the whole point of the suggestion.  There is only one UI.  Since others do it, there is no reason that Xfce can't do likewise. >However, I can address the point about modules.  As I understand it, the meaning behind the use of the term "module" is a program that has no GUI and performs a particular task under the DE. The Settings Manager is their front end or GUI.  I can find no need for any type of modules that are needing any type of visualization on their own.  Therefore, there is no need for any reworking of any kind.  They simply loose their existing UI's as completely redundant.  This is the whole point of the suggestion.  There is only one UI.  Since others do it, there is no reason that Xfce can't do likewise.
 > >
->The whole point of "unique" UI's is counter-productive because it adds unnecessary confusion, as well as overhead.  Worse, I can't find anything in their design that helps me understand what they do. +>The whole point of "unique" UI's is counter-productive because it adds unnecessary confusion, as well as overhead.  Worse, I can't find anything in their design that helps me understand what they do. - KitchM 
-+\\  
->We are told by the developers that they use Glade Interface Designer, so everyone is free to see what layouts they can come up with as they design their own suggested arrangements of widgets.  I also like the prettiness of icons, but they can exist on tabs just as easily, although a little smaller.  They should not be the an impediment to usability. +>
-+>>It is always tough to say how things could be put together.  We are told by the developers that they use Glade Interface Designer, so everyone is free to see what layouts they can come up with as they design their own suggested arrangements of widgets.  I also like the prettiness of icons, but they can exist on tabs just as easily, although a little smaller.  They should not be the an impediment to usability. 
->The categories are parially listed on other pages here.  There's a lot more than just Display and Hardware. - KitchM+>
 +>>The categories are parially listed on other pages here.  There's a lot more than just Display and Hardware. - KitchM
  
 ====Separation of Application Settings==== ====Separation of Application Settings====
Line 56: Line 57:
  
 > "Preferred Applications" - I think you are right it needs to be expanded. But just a thought - how does this relate to mime types and the applications that can open them, and the final xdg decision on which application opens them? But it may be handy to duplicate that option here. (The natural place for it seems to be in the file manager: file properties.) > "Preferred Applications" - I think you are right it needs to be expanded. But just a thought - how does this relate to mime types and the applications that can open them, and the final xdg decision on which application opens them? But it may be handy to duplicate that option here. (The natural place for it seems to be in the file manager: file properties.)
 +>>\\ 
 +>>I agree.  There is some lack of intuitive application to the settings.  The user can be mislead into believe one particular thing is being changed when it is actually something else.
 +>>
 +>>(By the way, you're doing fine.  This is not the best wiki engine, so I think you've made the best of it.)
 +>>
 +>>The issue of mime types is something that should be handled at the DE level in such a way that all applications know what is what.  That is not being done now.  This is most definately not a file manager issue; it is an environmental issue.  That one confusion is what causes so much trouble.  A file manager, on the other hand, is an application which interfaces directly with the OS-level connection to the file-system.  Entirely different and separate. - KitchM