[opensuse] Designing Yast package selector
Hi there, In order to design the Yast-GTK package selector, I would like to know what you guys dislike about the Yast-Qt package selector and, if possible, how would you shape the interface to make it more of your liking. Something that we would like to drop is Qt's multi-icon box in favor of ordinary check boxes. For this, we were considering a tab to separate "installed" and "installable" packages whose lists would be in sync with the search panel. Re-installing or any other advanced action would still be possible via a right-click popup menu. Note: we don't really need the tabs approach to use ordinary check boxes. A confirmation dialog in the end may be suffice. Highlighting should also be considered (not only for this). The search/etc panel should probably use tabs rather than the ackward combo box to switch modes. We could avoid a clutter note book by reducing the number of modes. Some could be merged, others don't make sense in some situations. Mockup: http://rpmcruz.planetaclix.pt/trash/software-manager-mockup1.png Instead of the Proceed button, it might be nicer to have the package selector looking the same as the other setup tools (ie with. the Abort, Next buttons and header on top). In the end, a list of the user's selection should be presented, as well as packages that need to be installed or removed because of dependencies. Possibility to not install or remove some package may be nice. Mockup: http://rpmcruz.planetaclix.pt/trash/software-manager-mockup2.png It should be noted that flexibity is restricted and some compromises may need to be done. About Yast-GTK: http://en.opensuse.org/YaST2-GTK Cheers, Ricardo -- Jacquin's Postulate on Democratic Government: No man's life, liberty, or property are safe while the legislature is in session. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Ricardo Cruz a écrit :
ordinary check boxes. For this, we were considering a tab to separate "installed" and "installable" packages whose lists would be in sync with the search panel.
I think it very important to have together the installed and not installed packages. Suppose you are testing text editors. It's very important to know what are the installed ones _in the moment you choose to install an other_. If you choose to install vi, you can uninstall emacs in the same moment. May be simply use vertical colored columns to make a clear difference between installed and not installed (the icons are too small on most screens)
Note: we don't really need the tabs approach to use ordinary check boxes. A confirmation dialog in the end may be suffice.
a good thing should be a window with a summary of the operation planned. If you first use search to find an app, then choose to make security update, if you use a list to choose an editor then search to find a sound mixer, the result of your choices should be obvious
The search/etc panel should probably use tabs rather than the ackward combo box to switch modes.
the present system allows for many choices
In the end, a list of the user's selection should be presented, as well as packages that need to be installed or removed because of dependencies. Possibility to not install or remove some package may be nice.
yes thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Am Mittwoch, 26. Juli 2006 03:56 schrieb Ricardo Cruz:
In order to design the Yast-GTK package selector, I would like to know what you guys dislike about the Yast-Qt package selector and, if possible, how would you shape the interface to make it more of your liking.
First of all, is it planed to replace YaST-Qt with YaST-GTK, or is it just another alternate? It was hard enough to lose the YaST KDE-Conterolcenter integration and the Qt based SUSE-Watcher. Dropping YaST-Qt would be a clear sign for KDE users, they are no longer wellcome in the Novell/SUSE universe. -- Machs gut | http://www.iivs.de/schwinde/buerger/tremmel/ | http://packman.links2linux.de/ Manfred | http://www.knightsoft-net.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Wed, Jul 26, 2006 at 11:55:05AM +0200, Manfred Tremmel wrote:
Am Mittwoch, 26. Juli 2006 03:56 schrieb Ricardo Cruz:
In order to design the Yast-GTK package selector, I would like to know what you guys dislike about the Yast-Qt package selector and, if possible, how would you shape the interface to make it more of your liking.
First of all, is it planed to replace YaST-Qt with YaST-GTK, or is it just another alternate?
No.
It was hard enough to lose the YaST KDE-Conterolcenter integration and the Qt based SUSE-Watcher. Dropping YaST-Qt would be a clear sign for KDE users, they are no longer wellcome in the Novell/SUSE universe.
It will not be dropped. Ciao, marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Onsdag 26 juli 2006 11:55 skrev Manfred Tremmel:
First of all, is it planed to replace YaST-Qt with YaST-GTK, or is it just another alternate? It was hard enough to lose the YaST KDE-Conterolcenter integration and the Qt based SUSE-Watcher. Dropping YaST-Qt would be a clear sign for KDE users, they are no longer wellcome in the Novell/SUSE universe.
I believe YaST-gtk is a more or less unofficial project as part of Google Summer of Code. Don't think it will replace yast-qt in KDE installations - otherwise the openSUSE-community might diminish rather quickly. Also keep in mind a Qt/KDE replacement for Zen-updater is being worked on - also under Google SoC. However I sometimes ask myself if SUSE.. or openSUSE.. is turning into "two-distros-in-one" .. maybe they should be different products in bugzilla and maybe we should have an irc-channel for each. Sounds like I won't be able to help people who'll use YaST-gtk - since it'll be a completely revised ui. Martin / cb400f --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
Em Quarta, 26 de Julho de 2006 10:55, o Manfred Tremmel escreveu:
Am Mittwoch, 26. Juli 2006 03:56 schrieb Ricardo Cruz:
In order to design the Yast-GTK package selector, I would like to know what you guys dislike about the Yast-Qt package selector and, if possible, how would you shape the interface to make it more of your liking.
First of all, is it planed to replace YaST-Qt with YaST-GTK, or is it just another alternate? It was hard enough to lose the YaST KDE-Conterolcenter integration and the Qt based SUSE-Watcher. Dropping YaST-Qt would be a clear sign for KDE users, they are no longer wellcome in the Novell/SUSE universe.
Oh, no. Sorry for not stating it; Yast-GTK is just a new interface module like ncurses and Qt. It will just be used on Gnome, XFCE and other GTK-based desktop environment. Yast-GTK will actually be a good thing for KDE users because rather than the ackward Qt interface, you may now link it to KDE libraries, since you won't have Gnome users on your back complaining about dependencies. This will result in a KDE look and feel, and will allow developers to integrate it better with KDE. We will also work on improving Yast-core a bit so we can have icons on Ok/Cance/etc buttons, for example, so Qt interface will also benefit. Cheers, Ricardo -- The moon is a planet just like the Earth, only it is even deader. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
In order to design the Yast-GTK package selector
YaST -GTK?? Ummm... is this to be an alternate or a full on replacement for YaST-QT? I seriously hope that SUSE/Novell isn't doing what this sounds like.... GTK is a disaster. It's a mess when it comes to UI design and usability. Not to say QT is perfect, but it's a whole lot better than anything I've ever seen or used that was GTK based. Please... please tell me I'm inferring the wrong thing here. SUSE has dropped the SUSE Watcher in favor of a broken Zen/Run/GTK mess, and now... this? Gnome designers are very busy "simplifying" the UI... at this rate, in 2 years Gnome will be a big red button that you can press that is labeled "Do Stuff". Don't relegate the SUSE tools to this universe too... Sigh... C. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
On Wed, Jul 26, 2006 at 12:42:14PM +0200, Clayton wrote:
In order to design the Yast-GTK package selector
YaST -GTK?? Ummm... is this to be an alternate or a full on replacement for YaST-QT?
I seriously hope that SUSE/Novell isn't doing what this sounds like.... GTK is a disaster. It's a mess when it comes to UI design and usability. Not to say QT is perfect, but it's a whole lot better than anything I've ever seen or used that was GTK based.
Please... please tell me I'm inferring the wrong thing here. SUSE has dropped the SUSE Watcher in favor of a broken Zen/Run/GTK mess, and now... this?
Gnome designers are very busy "simplifying" the UI... at this rate, in 2 years Gnome will be a big red button that you can press that is labeled "Do Stuff". Don't relegate the SUSE tools to this universe too...
YAST GTK is a Google Summer of Code project. So it is a technical experiment. YAST will keep QT and NCURSES frontends of course. And everyone one, who expects YAST GTK to be faster then YAST QT should just get a big fucking clue. It will just look different. Ciao, Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
In order to design the Yast-GTK package selector, I would like to know what you guys dislike about the Yast-Qt package selector and, if possible, how would you shape the interface to make it more of your liking.
Now for something more constructive :-) (than my last comment) I actually find the QT bast YASY to be quite useful. In general, for package management I find it quite important to see the version I have installed next to the version that is available to install. This makes it easy for me to compare and decide if I want to, or need to upgrade/install. I also think it's very important that when you select a package, the dependancies are checked, and you are informed of the impact that initial package selection has - this is a major failign of the current YAST. You select a package, and you don't know the impact unless you click the Check Dependancies button, or you click apply/next and actually start the install. Smart (for example) does this nicely by immediately telling you what will be changed, including any updated, added to removed packages. Apt/Synaptic does this too... and in my opinion does it way better than Smart. If any replacement QT or GTK based could do this... it would be a nice improvement. C. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-help@opensuse.org
participants (6)
-
Clayton -
jdd -
Manfred Tremmel -
Marcus Meissner -
Martin Schlander -
Ricardo Cruz