Re: [opensuse-ux] yast-gtk package selector
Il giorno ven, 29/06/2007 alle 19.54 +0100, Ricardo Cruz ha scritto:
Sex, 2007-06-29 às 18:39 +0200, Alberto Passalacqua escreveu:
Hello, Hi,
You meant to sent this to the opensuse-ux, right? No problem, but I will share your mail with the rest of the team, ok?
Sure. Sorry, I'm not subscribed to the yast-devel list. Feel free to spread my message :-)
I've just installed and tried it because it's not installed by default by alpha 5 GNOME one cd install.
Oh, so it is shipped in the CD, but is not installed by default? (I don't follow the Alphas, the two Novell guys on the team take care of that...)
Well, it was the first release of 1 cd install for alpha 5. Not a problem.
It is different if compared to the Qt version, but the general usage is quite simple.
There are some issue however, that I think has to be addressed:
* It builds the list of packages every time you switch visualization.
Would require some sweat, but it's fix-able. :) Would you say this must be fixed for 10.3? I can see how this would bother someone that is just giving a try to the package selector, but shouldn't bother close as much to the casual user who will not be jumping around the modes...
Yes, but it's quite annoying. I think it's common to switch from the pattern list to the category list for example. Btw, I would put the pattern list as default, like in the Qt version.
For example switching from "Patterns" to "Plain list" requires some time to rebuild the lists of packages, while under the QT version it is immediate.
yast-qt doesn't build the entire thing at one moment. For instance, their "plain list" equivalent is blank, and you need to search for something... This kind of approach would require significantly more work to be quick, but ok, can be done.
Yast-qt can show all the packages if you go to Groups -> All, without searching. However the issue which bothers me is the parsing at each switch. The way the whole list is shown is OK.
* If a package is installed, it is shown both in the Available column and in the Installed column, which is confusing. Probably this is an alternative to the Refresh function present in the QT version, but it should be made explicit.
Right... If you install some package from a repo, it wont't disappear from it. :) But okay, we can hide it; in fact, we did, and had a popup menu that allowed the user to re-install the package... This wasn't very elegant... You think its better though?
Well, you point of view is interesting. I didn't think that way because I was comparing to the Yast-qt installer. Now I'm in doubt. I like the idea of pools to represent repositories, and in this vision, I understand your idea of leaving the package in the "Available" pool too. However I think there should be a "Reinstall" function explicitly shown somewhere, because users accustomed to yast-qt installer might miss it.
Or, do you mean that even different versions of the package shouldn't be listed in the available pool
No. That would be too much :-)
* There's no way to immediately understand if there's a new version of a package (no highlight).
Okay, sounds useful. Some shaded red would be okay?
You can use the convention you like hehe. Yast-qt has some inconsistency itself. In Yast-qt software manager: - Blue -> There's a newer version available. - Red -> The available version is older than the installed one. - Black -> The installed version is the same available. In Yast-qt online update: - Blue -> Recommended update - Red -> Security update - Black -> Additional stuff
* There's no way to "Taboo" a package (or I didn't find it).
You're right, there isn't. Taboo means the package won't be installed no matter what, right? In what scenarios would you use it?
To block the installation of something under every circumstance. For example, I don't want wlan-kmp on my desktop because it conflicts with my ndiswrapper driver, and without tabooing it, it's reinstalled at every kernel update.
* There's no way to select a whole list of packages. To be honest it's possible to select it by using SHIFT+CLICK, but it's not exactly amazing.
Tell me what selection way you have in mind.
In Yast-qt you can select all the packages in a list and: * Upgrade (refresh) them unconditinally * Upgrade them if there's a new version * Taboo them (never install) * Remove them * Lock them (never change)
* Also, a cosmetic improvement would be to show the disk space usage permanently, maybe removing the tabs and showing disk usage and sources list in two boxes at the bottom of the main window. But this is a minor issue.
I actually wrote it that way at first; the sources table is a bit too wide though... Will check possible layouts and ask the others about this...
Hehe. Ok. But don't worry too much about that. It's just a matter of tastes. P.S. You sent the answer only to my address and not to the list. With kind regards, Alberto -- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
Sex, 2007-06-29 às 21:20 +0200, Alberto Passalacqua escreveu:
Il giorno ven, 29/06/2007 alle 19.54 +0100, Ricardo Cruz ha scritto:
Sex, 2007-06-29 às 18:39 +0200, Alberto Passalacqua escreveu: Would require some sweat, but it's fix-able. :) Would you say this must be fixed for 10.3? I can see how this would bother someone that is just giving a try to the package selector, but shouldn't bother close as much to the casual user who will not be jumping around the modes...
Yes, but it's quite annoying. I think it's common to switch from the pattern list to the category list for example. Btw, I would put the pattern list as default, like in the Qt version.
Okay, probably some option was added to the selector's interface that I wasn't told about. Will ask about that.
* There's no way to "Taboo" a package (or I didn't find it).
You're right, there isn't. Taboo means the package won't be installed no matter what, right? In what scenarios would you use it?
To block the installation of something under every circumstance. For example, I don't want wlan-kmp on my desktop because it conflicts with my ndiswrapper driver, and without tabooing it, it's reinstalled at every kernel update.
Alright, so we need to add some Taboo stamp element, and honor that property. Not sure how the user should set it... I am inclined to make the stamp clickable, being shadowed when disabled... But a popup menu option would be better so you can set it on multi-selection. We could have both, or maybe add a button for multi-selection; would rather avoid multiple paths though, especially state-dependent...
* There's no way to select a whole list of packages. To be honest it's possible to select it by using SHIFT+CLICK, but it's not exactly amazing.
Tell me what selection way you have in mind.
In Yast-qt you can select all the packages in a list and:
* Upgrade (refresh) them unconditinally * Upgrade them if there's a new version * Taboo them (never install) * Remove them * Lock them (never change)
Selecting a bunch of packages and removing them is possible; the opposite wouldn't work as good. On the available pool, the install button will either install or upgrade them, in case they are installed or not. So okay, on multi-selection we should make the possible actions explicit, and apply them in those cases where its appropriate...
P.S. You sent the answer only to my address and not to the list.
Sorry, I got the impression you replied to me privately, so I just used the "reply to author". Thanks, Ricardo
With kind regards, Alberto
-- To unsubscribe, e-mail: opensuse-ux+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-ux+help@opensuse.org
participants (2)
-
Alberto Passalacqua -
Ricardo Cruz