| Simple/advanced
May 25 2006 on content about:config |
How about any config screens having a Simple/Advanced options button.
The config screen starts off in Simple mode, with "Advanced options" button sitting beside the "Save/cancel" buttons.
User clicks the button and gets an advanced version of the config window, the button now changes to "Simple options".
It's simple, intuitive and clean... and I believe tried and tested and familiar to most users. |
|  | | Re: Re: Might be dif
May 25 2006 on content Program suspend |
The mockup shows Firefox, AFAIK Firefox is a gtk based app, it stores it's state using mechanisms alien to KDE, hence KDE would have no state management for that application.
Suspending an app using the kill command is not what the user wants here, since I suspect he wants to resume it, possibly between reboots. |
| | | Too busy
May 25 2006 on content KDE Spectra |
I must agree with the other comments. First off, fantastic mockup work :)
Now, regarding the concept, the interface you're proposing is visually too busy for me. A GUI should make sense when you look at it... too many buttons and the users will easily get confused.
What is the meaning of clicking one of the "folder buttons" when you have a active selection of folders? Do we still have a context menu or does it go away? If we still have the context menu then why replicate the functionality? What happens if I want to define new actions, will this result in additional buttons under the folder? What if I have 10 such actions... the list goes on.
I personally like simple interfaces, intuitive, uncluttered. There is a tendency in KDE to swamp the user with options where frankly I end up using only a tiny fraciton of what is offered to me. Advanced options are still needed (which is what I like about KDE) but not by default. The concept may appeal to some and could be included, but please, not by default... I personally would want this to be turned off...
Therefore I'm afraid I need to give thumbs down for this idea. |
| | | In far future :)
Jul 19 2005 on content KGentooConf |
At present this utility is not really useful for me.
Some possible features that would make it attractive to me ;)
Don't forget the very useful files:
/etc/portage/package.keywords
/etc/portage/package.mask
/etc/portage/package.unmask
/etc/portage/package.use
In fact, /etc/make.conf USE flags should be seldom used and should only present a small generic subset (trust me, speaking from experience here ;) ). It's dangerous to also use the dev keywords (ie "~x86") globally. It's far better to use USE/KEYWORDS flags on a package-by-package basis in the above mentioned files.
Also note the 'equery' functionality, you can now query what use flags a package uses and what use flags are available. If you could link that into your utility and then populate the /etc/portage files, that woulud indeed be a powerful GUI. |
| |
Search people
Current visitors
New users
Birthdays
Most active users
Back
|
|
