Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: jls on March 06, 2009, 06:19:25 PM
-
In the app window I would add a checked box named "show libraries and dev" that it should be unchecked by default. Infact I don't see the need for the user to see extensions like libxx, gtk+-2, glib1...
If u look at ubuntu, in the first menu there is a program called "add - remove programs" that is a list of choosed programs that is more user friendly then the one in synaptic.
So I would reorganize the extensions where each extension can be one of this 2 types:
-main program
-dependence, library, development
If the user will check the box they'll be showed
-
If the application you're downloading requires these packages, they're going to need to be downloaded, so why would there be any reason to hide them?
-
If the application you're downloading requires these packages, they're going to need to be downloaded, so why would there be any reason to hide them?
they'll be downloaded automatically, hide for the list to be more user friendly
-
It's a good idea in my opinion. Perhaps a second checkbox for extensions with modules?
-
One day we will have enough little library extensions to justify somehow hiding them. That is a small price to pay for being modular and not including dependent libs with each extension. I am sure a solution will emerge in time.
-
You'll do what you feel is best, and it wil probably be an improvement. I just don't see the correlation between making things invisible and making things user friendly. It's like the boot splash that most distros seem to prefer. If you aren't doing anything while that process...errr...processes, how does it benefit the user to pretend it's not there? If anything, I think it's LESS user friendly, because the user is unaware of what's happening and is less likely to understand the source of possible trouble.
If hiding is implemented, I hope you will consider making "verbose" an optional setting.
-
I agree with mikshaw for the most part.
But, I can see how some prefer not to know what goes on in their system. Taking the boot splash example, there is a reason why it's popular with them...
-
Though I don't see a direct need to do so now, categorizing the extension menu in some way could make sense when we get to, say, 500 extensions. That would be simply organization, not hiding the system from the user.
My preference would be categories instead of a toggle switch if it were to one day happen. But I myself am happy with the menu now.