[yast-devel] redesign of repo module UI

older
[yast-devel] CSS: Which standard...

Martin Schmidkunz

17 Feb 2010 17 Feb '10

12:53

Hi! Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html The main differences to the current UI are: * compliance with basic concept of overviews as shown on gagarin.suse.de (OK, the edit string and delete functionality is missing, but I am sure you`ll figure it out :-)) * less information on screen * hints on priority * first implementation of enable/disable in YaST based on current survey results My usability questions are: * What do you think about the mock up? * What does "Keep downloaded packages" mean? * Does the target user group member know what the term "repository" is? I doubt that. * Does the target user group member know about "priorities"? Shouldn`t it be explained a little bit more? Tooltip? Looking forward to your comments! Cu, Martin ---------------------------------------------------------------- Martin Schmidkunz User Experience Specialist martin.schmidkunz@novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. Novell® Making IT Work As One™

Attachments:

attachment.htm (text/html — 2.8 KB)
Picture9.png (image/png — 182.8 KB)

Show replies by date

Josef Reidinger

17 Feb 17 Feb

13:13

Martin Schmidkunz write:

...

Hi!

Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html

The main differences to the current UI are: * compliance with basic concept of overviews as shown on gagarin.suse.de (OK, the edit string and delete functionality is missing, but I am sure you`ll figure it out :-)) * less information on screen * hints on priority * first implementation of enable/disable in YaST based on current survey results

My usability questions are: * What do you think about the mock up?

In general I like it. few improvements which I found usable - one click show details, second click on same repo hide it again (now it hides only if you click on another) - I prefer to show after click instead of show on focus because if someone move mouse not so fast it too much change. I think it could stress person if page do something even if they just move mouse

...

* What does "Keep downloaded packages" mean?

If RPM from which is package installed is stored on disc after installation or not.

...

* Does the target user group member know what the term "repository" is? I doubt that.

Maybe "Instalation sources" or package sources?

...

* Does the target user group member know about "priorities"? Shouldn`t it be explained a little bit more? Tooltip?

Yes it should be better explained. I prefer info icon next to priority which show help under input.

...

Looking forward to your comments!

Cu,

Martin

---------------------------------------------------------------- Martin Schmidkunz User Experience Specialist martin.schmidkunz@novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -----------------------------------------------------------------

Novell, Inc. Novell® Making IT Work As One™

-- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Stanislav Visnovsky

13:30

On streda 17 Február 2010 14:13:21 Josef Reidinger wrote:

...

Martin Schmidkunz write:

...
* Does the target user group member know what the term "repository" is? I doubt that.

Maybe "Instalation sources" or package sources?

Please, stick with repositories. Do not invent yet another term. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Klaus Kaempf

14:16

* Josef Reidinger [Feb 17. 2010 14:13]:

...

...
* What does "Keep downloaded packages" mean?

If RPM from which is package installed is stored on disc after installation or not.

If this setting is offered through the UI, we probably also need a 'clear package cache' button to prevent disk overflows in appliances. Klaus -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Patrick Shanahan

14:41

* Klaus Kaempf [01-01-70 12:34]:

...

* Josef Reidinger [Feb 17. 2010 14:13]:

...
...
* What does "Keep downloaded packages" mean?

If RPM from which is package installed is stored on disc after installation or not.

If this setting is offered through the UI, we probably also need a 'clear package cache' button to prevent disk overflows in appliances.

And/or an indication of partition remaining space. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Katarina Machalkova

13:35

Ahoj,

...

Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html

The main differences to the current UI are: * compliance with basic concept of overviews as shown on gagarin.suse.de (OK, the edit string and delete functionality is missing, but I am sure you`ll figure it out :-))

I'm not a big fan of the idea of unpacking a list item "on mouse over" - longer stay on such page makes me feel dizzy (in a sense: "like on stormy sea"). What I prefer is unpacking on demand, with some arrow icon hints. Like in jquery accordion demo: http://docs.jquery.com/UI/Accordion

...

* less information on screen * hints on priority

Spinbox would fit excellently here: http://plugins.jquery.com/project/spinbox

...

* first implementation of enable/disable in YaST based on current survey results

Was this really the survey result? I have to complete it and express my disagreement :) What was wrong with checkboxes? Isn't it an ideal UI element for values that can only be turned on/off?

...

* Does the target user group member know about "priorities"? Shouldn`t it be explained a little bit more? Tooltip?

Either tooltip, or some small help icon nearby (question mark, "What is this?") with a tooltip fB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

Josef Reidinger

13:54

Katarina Machalkova write:

...

Ahoj,

...
Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html

The main differences to the current UI are: * compliance with basic concept of overviews as shown on gagarin.suse.de (OK, the edit string and delete functionality is missing, but I am sure you`ll figure it out :-))

I'm not a big fan of the idea of unpacking a list item "on mouse over" - longer stay on such page makes me feel dizzy (in a sense: "like on stormy sea"). What I prefer is unpacking on demand, with some arrow icon hints. Like in jquery accordion demo: http://docs.jquery.com/UI/Accordion

Yes, I prefer it also. Just add also hide again on second click (accordion doesn't do it also)

...

...
* less information on screen * hints on priority

Spinbox would fit excellently here: http://plugins.jquery.com/project/spinbox

Looks good, but if priority is from fixed range, slider could be better - http://www.dhtmlgoodies.com/scripts/form_widget_amount_slider/form_widget_am...

...

...
* first implementation of enable/disable in YaST based on current survey results

Was this really the survey result? I have to complete it and express my disagreement :) What was wrong with checkboxes? Isn't it an ideal UI element for values that can only be turned on/off?

...
* Does the target user group member know about "priorities"? Shouldn`t it be explained a little bit more? Tooltip?

Either tooltip, or some small help icon nearby (question mark, "What is this?") with a tooltip

fB.

Martin Kudlvasr

18 Feb 18 Feb

11:49

On Wednesday 17 February 2010 14:54:40 Josef Reidinger wrote:

...

Katarina Machalkova write:

...
I'm not a big fan of the idea of unpacking a list item "on mouse over" - longer stay on such page makes me feel dizzy (in a sense: "like on stormy sea"). What I prefer is unpacking on demand, with some arrow icon hints. Like in jquery accordion demo: http://docs.jquery.com/UI/Accordion

Yes, I prefer it also. Just add also hide again on second click (accordion doesn't do it also)

Maybe this won't be so popular opinion, but I thought that Accordion fits for organizing many _different_ parts of a form/content. Here we are organizing many _similar_ parts of form. In our case I would expect the form to stay on one place and only change the data - much like in yast2-qt software repositories, but place selector of repositories on left side and single repository configuration on right side. I don't say that using the Accordion is bad, just that I think it was meant for different use-cases (go over large form/content which is divided into sections without scrolling). Martin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

kkaempf＠suse.de

13:06

* Martin Kudlvasr [Feb 18. 2010 12:49]:

...

Maybe this won't be so popular opinion, but I thought that Accordion fits for organizing many _different_ parts of a form/content. Here we are organizing many _similar_ parts of form. In our case I would expect the form to stay on one place and only change the data - much like in yast2-qt software repositories, but place selector of repositories on left side and single repository configuration on right side. I don't say that using the Accordion is bad, just that I think it was meant for different use-cases (go over large form/content which is divided into sections without scrolling).

Well, we looked into this topic last year and the accordion-style was accepted by all stakeholders (and UI designers ;-)). Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Martin Kudlvasr

17:03

On Thursday 18 February 2010 14:06:50 kkaempf@suse.de wrote:

...

* Martin Kudlvasr [Feb 18. 2010 12:49]:

...
Maybe this won't be so popular opinion, but I thought that Accordion fits for organizing many _different_ parts of a form/content. Here we are organizing many _similar_ parts of form. In our case I would expect the form to stay on one place and only change the data - much like in yast2-qt software repositories, but place selector of repositories on left side and single repository configuration on right side. I don't say that using the Accordion is bad, just that I think it was meant for different use-cases (go over large form/content which is divided into sections without scrolling).

Well, we looked into this topic last year and the accordion-style was accepted by all stakeholders (and UI designers ;-)).

I didn't know about that ... Well then, too bad for our stakeholders ;-) Martin

...

Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

J. Daniel Schmidt

17 Feb 17 Feb

14:44

On Wednesday 17 February 2010 13:53:21 Martin Schmidkunz wrote:

...

Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html

Thanks. Just two remarks: - Repositories need to be deletable - where to position the delete button? - Currently PackageKit does not support "services" but we will need to implement that. So then the list gets more complex as a "service" has many catalogs that can be enabled or disabled (but not deleted). Please take this into account when designing it. If you have questions I can explaint it to you. Btw. my personal impression of the layout: I find it hard to get a real overview of the repos if I only can see one of them in detail. The list should not get so long that we need to only display the alias name - well if it does, we have a different problem. What about displaying at least the url (in a second line, small) and a checkmark right before the alias name signaling if the repo is enabled. ... just my $ 0.02 Ciao, Daniel -- J. Daniel Schmidt SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Lukas Ocilka

14:56

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 17.2.2010 15:44, J. Daniel Schmidt napsal(a):

...

On Wednesday 17 February 2010 13:53:21 Martin Schmidkunz wrote:

...
Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html

I find it hard to get a real overview of the repos if I only can see one of them in detail. The list should not get so long that we need to only display the alias name - well if it does, we have a different problem. What about displaying at least the url (in a second line, small) and a checkmark right before the alias name signaling if the repo is enabled.

Exactly, you can see only on repository at the time. I guess that the green icon on the left side at least says that the repository is enabled. Anyway, it's, for instance, impossible to sort the current repositories by priority, name, 'enabled' flag, etc. Additionally, using sentences like 'Repository is currently enabled.', 'Keep downloaded packages is currently enabled.' does not help with easy understanding of the current status. What is important is: Status: Enabled Autorefresh: Enabled Keep packages: Enabled Bye Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFLfAOFVSqMdRCqTiwRAs0pAJ9Xgxgp0oo9EYs6EeTbI0ts18oVVwCffLWm rxp6zeYuoIHP3yOuEbtmrc0= =mlP/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Rajko M.

19 Feb 19 Feb

01:16

On Wednesday 17 February 2010 08:56:05 Lukas Ocilka wrote:

...

What is important is: Status: Enabled Autorefresh: Enabled Keep packages: Enabled

Which is left aligned as it should be. Forcing users to catch start of the line, line after line, is for me serious impediment for comfortable reading. -- Regards Rajko, -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

Ladislav Slezak

17 Feb 17 Feb

15:08

On 17.2.2010 15:44, J. Daniel Schmidt wrote:

...

On Wednesday 17 February 2010 13:53:21 Martin Schmidkunz wrote:

...
Please find an idea of repo module UI at: http://home.arcor.de/martin.schmidkunz/repos21.html

Thanks.

Just two remarks: - Repositories need to be deletable - where to position the delete button? - Currently PackageKit does not support "services" but we will need to implement that. So then the list gets more complex as a "service" has many catalogs that can be enabled or disabled (but not deleted). Please take this into account when designing it. If you have questions I can explaint it to you.

For services we could use the same layout as in the traditional yast, there is a small combo box in the upper right corner for switching between service and repository view.

...

Btw. my personal impression of the layout: I find it hard to get a real overview of the repos if I only can see one of them in detail. The list should not get so long that we need to only display the alias name - well if it does, we have a different problem. What about displaying at least the url (in a second line, small) and a checkmark right before the alias name signaling if the repo is enabled. ... just my $ 0.02

I agree, the most important value for users is URL and state (enabled/disabled). Another problem might be with priority - high priority repository shadows lower priority repositories. Maybe the priority should be displayed when it's different to the default (99). -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

J. Daniel Schmidt

19 Feb 19 Feb

14:37

On Wednesday 17 February 2010 16:08:25 Ladislav Slezak wrote:

...

For services we could use the same layout as in the traditional yast, there is a small combo box in the upper right corner for switching between service and repository view.

A service is nothing but a group of repos. So why not use the functionality of modern HTML and group the catalogs within a service. Btw. a repo of its own is handled as a service as well. So we really could make this visible and need no differentiator or a ComboBox switch. Martin, if you like I'll explain it to you and we could discuss this issue before you change the design. Ciao, Daniel -- J. Daniel Schmidt SUSE Linux Products GmbH Research & Development Maxfeldstr. 5 GF: Markus Rex, HRB 16746 (AG Nürnberg) D-90409 Nürnberg -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org

5181

Age (days ago)

5183

Last active (days ago)

List overview

Download

14 comments

12 participants

participants (12)

J. Daniel Schmidt
Josef Reidinger
Katarina Machalkova
kkaempf＠suse.de
Klaus Kaempf
Ladislav Slezak
Lukas Ocilka
Martin Kudlvasr
Martin Schmidkunz
Patrick Shanahan
Rajko M.
Stanislav Visnovsky