Version listing for a package

[Atri Bhattacharya]

Hi Ricardo!
You might remember we had some discussion [1] about the region where the list of all available versions from all subscribed repos is shown for a package. I suggest that we try having an action button (like the one you had implemented while testing various things for 11.3 [2]) instead of the present radio-boxes that require having an, often obscure, "Install" button below the entire list. What do you think?

--
Atri

[1] http://groups.google.com/group/yast2-gtk/browse_thread/thread/b729b0d14dca8977
[2] http://yast2-gtk.googlegroups.com/web/save_remove.png?gda=-DAS2EIAAADmhecnusWXSoSUpze0S1v4JacXIAXrnY9GLv1ebRe3c_ekIKGG_w_dYLP1rTUXRH9V4u3aa4iAIyYQIqbG9naPgh6o8ccLBvP6Chud5KMzIQ&gsc=l6d_HwsAAACIoWLNqrFuDDCmPFW9t1qp

[Ricardo Cruz]

Hi Atri,

First of all, I'd like to hear from others too! :)

But here are my impression:

There are two advantage to the current radio-boxes:
* more similar to the qt plugin
* you can select a version number without installing it,
and see the information texts changing (well, I don't
remember if all of them change, but I think some do...)

One big disadvantage of the radio-boxes is that a few
people have complained they didn't see the "Install"
button at first, and thought clicking the radio-box was
enough to install the version.

Should we try drawing a border around it to see
if that looks good enough? If that looks too bad, we
could also try only drawing the left-side of the border
along the height of the box...

Anyway, let's please not try many megalomaniac
changes. :) I have to budget my time: besides, I am
under the impression that PackageKit or webyast,
will be candidates for replacing our software manager
in the future... (But I dunno what's being done in those
fronts.)

By the way, there is some work being done in LibreOffice
to make it easy to re-design the dialog windows. I am sure
your input will be most appreciated there. I will contact you
when there are news from those lands.

Cheers,
Ricardo

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Ricardo Cruz]

Okay, here are screenshots for the
borders...

[Atri Bhattacharya]

On 9 December 2010 05:23, Ricardo Cruz <rpm...@alunos.dcc.fc.up.pt> wrote:

Hi Atri,

 First of all, I'd like to hear from others too! :)

Good luck with that :)

 

Should we try drawing a border around it to see
if that looks good enough? If that looks too bad, we
could also try only drawing the left-side of the border
along the height of the box...

The border on all four sides looks good.

Bye

--
Atri

[Ricardo Cruz]

Quoting "Atri Bhattacharya" <badsh...@gmail.com>:
>> Should we try drawing a border around it to see
>> if that looks good enough? If that looks too bad, we
>> could also try only drawing the left-side of the border
>> along the height of the box...
>>
>>
> The border on all four sides looks good.

But does it help though? The idea is to transmit some
notion that those check-boxes are part of a greater
agglomerate... when the button is not visible...

Anyhow, we can give a try to using push-buttons...
Would you go for buttons with only icons or text?
The text probably occupies too much space, right?

Should we also show the remove icon, or the install
button icon for the package list too, like we show the
upgrade one?
Would that imply we should lose the check-box, and
maybe replace it with an icon: or keep it, at least
for now? (It sounds it could be confusing to have
two identical actions very close to each other...)

Thanks,

[Atri Bhattacharya]

Hi!

On 9 December 2010 20:58, Ricardo Cruz <rpm...@alunos.dcc.fc.up.pt> wrote:

Quoting "Atri Bhattacharya" <badsh...@gmail.com>:

Should we try drawing a border around it to see
if that looks good enough? If that looks too bad, we
could also try only drawing the left-side of the border
along the height of the box...

The border on all four sides looks good.

 But does it help though? The idea is to transmit some
notion that those check-boxes are part of a greater
agglomerate... when the button is not visible...

I don't know what it does for a new user who would not know a button exists, but to me it conveys that the whole box is one widget and each item in it therefore a part of a greater whole. But that's just me.
 

 Anyhow, we can give a try to using push-buttons...
Would you go for buttons with only icons or text?
 The text probably occupies too much space, right?

I think yet that this would be the best solution. I think we should have buttons with icons only.
 

 Should we also show the remove icon, or the install
button icon for the package list too, like we show the
upgrade one?
 Would that imply we should lose the check-box, and
maybe replace it with an icon: or keep it, at least
for now? (It sounds it could be confusing to have
two identical actions very close to each other...)

I guess it would be for the best to have either the check-box or the action buttons, and not both of them. In case we do use action buttons in this widget, it would probably feel more consistent to have such buttons for all of the actions -- install, remove or upgrade.
 

Bye
--
Atri

[Atri Bhattacharya]

On a second reading, I think I misunderstood the last bit earlier. If you are thinking about buttons in the general package view (and not just the version list widget), I think that is unnecessary. The update button is there because it is a special case, the simple check-box thing doing well enough for the install and remove actions.

--
Atri