[opensuse-factory] some comments about usabilty, regarding repositories
I found quite hard to find how to add the Community Repositories. It take some time to me to find out that it is hidden in the Software Management module. I think the approach of 10.3, having a separated module to manage Community Repositories is better. Specially for new users, who don't have idea of such function. I found it because I know it so I started to search it. But, IHMO is not the best for new users. And, as I read in other messages, your target are the newbies. -- Kind Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lørdag den 26. April 2008 18:39:12 skrev Gabriel:
I found quite hard to find how to add the Community Repositories. It take some time to me to find out that it is hidden in the Software Management module. I think the approach of 10.3, having a separated module to manage Community Repositories is better. Specially for new users, who don't have idea of such function. I found it because I know it so I started to search it. But, IHMO is not the best for new users. And, as I read in other messages, your target are the newbies.
I think you're wrong. The almighty fantastic Ubuntu distribution which is a benchmark for what's right also "hides" repository management in the package management ui. I think it's more intuitive to new users that everything package management related is in the same place. The people who will be confused are experienced users such as yourself, who need to learn and adjust. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, Apr 26, 2008 at 2:01 PM, Martin Schlander
I think you're wrong. The almighty fantastic Ubuntu distribution which is a benchmark for what's right also "hides" repository management in the package management ui.
This is not Ubuntu. Why we should do the same as ubuntu ?? If I want that, I would choose it in the first place.
I think it's more intuitive to new users that everything package management related is in the same place. The people who will be confused are experienced users such as yourself, who need to learn and adjust.
I don't think so. -- Kind Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Gabriel wrote:
I found quite hard to find how to add the Community Repositories. It take some time to me to find out that it is hidden in the Software Management module. I think the approach of 10.3, having a separated module to manage Community Repositories is better. Specially for new users, who don't have idea of such function. I found it because I know it so I started to search it. But, IHMO is not the best for new users.
The icon is already back: https://bugzilla.novell.com/show_bug.cgi?id=381255 cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I think the approach of 10.3, having a separated module to manage Community Repositories is better.
Absolutely not. You start with wanting to install some software, and start the software module. Then you wait (10.3), and wait, and wait some more. Then you search for the software you want, and find it's not in one of the repos you have currently active (you do disable them, to only wait 10 times in the previous step, not 30 times). You start the repo module. It tells you "software management is already running", and exits. You swear, quit the software manager, start the repo module. You wait. You finish manageing repos and start the software module again. You wait, and then some more. Oh damn, repos still not right. Nuts. Combining the two under one software management hat is really making things so much easier. Having a direct entry point to it from a yast icon is a different matter, but would this even be considered or requested had the software module always included repo management? Is it really a good idea to put more icons there for the same module? In this case perhaps yes for historic reasons, but remember the user and group management icons for one tab each of the same module - that serves no useful purpose. Shouldn't the software icons in yast still be further reduced? Volker -- Volker Kuhlmann is list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2008/4/28, Volker Kuhlmann
I think the approach of 10.3, having a separated module to manage Community Repositories is better.
Absolutely not. You start with wanting to install some software, and start the software module. Then you wait (10.3), and wait, and wait some more. Then you search for the software you want, and find it's not in one of the repos you have currently active (you do disable them, to only wait 10 times in the previous step, not 30 times). You start the repo module. It tells you "software management is already running", and exits. You swear, quit the software manager, start the repo module. You wait. You finish manageing repos and start the software module again. You wait, and then some more. Oh damn, repos still not right. Nuts.
Combining the two under one software management hat is really making things so much easier. Having a direct entry point to it from a yast icon is a different matter, but would this even be considered or requested had the software module always included repo management? Is it really a good idea to put more icons there for the same module? In this case perhaps yes for historic reasons, but remember the user and group management icons for one tab each of the same module - that serves no useful purpose. Shouldn't the software icons in yast still be further reduced?
Volker
I totally agree... In 10.3 we had 6 or 7 modules doing similar things (Software Manager, Repository Manager, Community Repository, Online Update, Online Update Repository, Add-on Product, Patch CD Update, Automatic Update, etc...) Of course its not interesting to join all-in-one, but reduce the amount of icons should be very very nice and more usefull for the user...(as the "advanced" user probably will use more zypper than yast) regards, Luiz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Volker Kuhlmann schrieb: |>> I think the approach of 10.3, having a separated module to manage |>> Community Repositories is better. | | Absolutely not. You start with wanting to install some software, and | start the software module. Then you wait (10.3), and wait, and wait some | more. Then you search for the software you want, and find it's not in | one of the repos you have currently active (you do disable them, to only | wait 10 times in the previous step, not 30 times). You start the repo | module. It tells you "software management is already running", and | exits. You swear, quit the software manager, start the repo module. You | wait. You finish manageing repos and start the software module again. | You wait, and then some more. Oh damn, repos still not right. Nuts. This is 10.3. In 11.0 it is no problem to start the repo module with a running sw_single afaik. | | Combining the two under one software management hat is really making | things so much easier. Having a direct entry point to it from a yast | icon is a different matter, but would this even be considered or | requested had the software module always included repo management? Is it | really a good idea to put more icons there for the same module? In this | case perhaps yes for historic reasons, but remember the user and group | management icons for one tab each of the same module - that serves no | useful purpose. Shouldn't the software icons in yast still be further | reduced? Yes, the software tab should have less icons. Especially the update icons are way too confusing and mostly not even needed. - - Remove "Add-On Product" (this can be done through the repo module) - - Remove "Media-Check" (if openSUSE installed correctly the media should be correct as well. Most don't need it by default. However, it should still installable by zypper) - - Have only one update icon in which you can utilize: "online update", automatic-online-update, patch-cd-update (could be removed as well - install it if needed and not by default) - - Remove online update configuration: this should either pop up when utilizing "online update" as long as no online update repo is activated. The other option would be just to have the user select an update repo via the community repo manager. - - Remove "installation into directory". Most users don't need it. It should be an optional installation. So you end up with 3 icons: Online Update Software installation Installation sources (which include the community repos module) Why Installation sources should be called from yast fontend: It emphasizes that there is something like repos and makes it obvious to a new users he needs it. It should stay there for the old users who will search for it. It should stay there as to make it possible to explain to a new user from remote on how to add sources. It should stay there as it does not really have something to do with software installation. There are enough cases in which you want to add a repo without installing software, SO having to call the software module first is not good. It is ok to also have the ability to call the module from sw_single. It is still not right to remove the module from the main yast frontend. HTH Felix | | Volker | -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIFjzqaQ44ga2xxAoRAi56AKCH/aPsCLNihZu1IRD6c2sa1LgrNgCfVlEf ToNa2sDrDVHQvW3iAWG9BFw= =w+W6 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (6)
-
Felix-Nicolai Müller -
Gabriel -
Ludwig Nussel -
Martin Schlander -
Volker Kuhlmann -
¡ElCheVive!