Em Quarta, 23 de Agosto de 2006 14:09, o Andreas Hanke escreveu:
Hi,
Hey you,
Ricardo Cruz schrieb:
So with the Summer of Code over, it's time to announce the GTK+ interface for Yast
So you're asking for feedback? Here we go ;-)
Yes, that's always nice to get. :) *snip*
Which ones are interesting for me? No idea. Which ones are unneeded, and for what reason? No idea. Actually I know that I have all patches, but assuming that I didn't know that, I would have to conclude from the empty checkboxes that not a single patch is installed on my system.
YOU seems to be pretty damaged in my machine (takes forever to launch, etc), so I don't use it and I was just testing the interface. Anyway, the problem is that I thought Zypp would only report available patches :/... Now in SVN only available patches are displayed. Do you, as a user, have the need for an installed patches catalog? And btw, can you remove installed patches?
I don't know the reason, the reason seems to be missing functionality in the underlying libraries. OK, but still, in the Qt frontend the checkboxes at least have different colours, so it is hard, but possible to determine the status of a patch. In the ncurses frontend it's even possible to sort the patches by status.
Sort by status? Did you mean "sort by severity"? Either way, I have set columns to be sortable... It currently treats severity columns as strings, not by the actual severity value. I will try to get an enumeration of severaties to get that right.
What I want to have is an intuitive and, most importantly, _common_ view on the patches. Maybe it could be possible to merge ideas from the now three YaST frontends and agree on something that can be implemented consistently for all frontends.
That's the old SWT / Swing debate. Should we make the interfaces look familar between targets or should we aim for each target. Surely KDE and Gnome users have different tastes, thus they use the desktop they use. I understand the feeling that a user may get information on a website that doesn't apply to his Yast frontend, but only the package selector interface is different and if we make it easy to use, such websites won't be necessary.
Explaining the online_update module should not require more than a single wiki page with a single series of screenshots! Users are already complaining about the too many totally different UIs. Zen-Updater is totally different from Qt online_update and will stay different, OK, but now Gtk online_update is again different while it shouldn't be.
There is one more issue about the patch selector. Not only the interfaces are different, but they are accessed from different points. That is, some websites may say to use zen-updater, while others to use Yast. With the package selector, nobody in their right mind will say to use zen-installer and zen-updater. :) Maybe we shouldn't offer the YOU interface and direct the user to zen-updater? I dunno, but I guess the best is to provide it and the distribution should be the disabling it, if it wants to.
This is the perspective of a user who explained the existing patch management UIs to dozens of users and therefore has sort of an idea about the problems users are again and again running into. Of course I appreciate all the work you and the others are doing as developers ;-)
But aren't the problems more related with the so many choices? You have Yast, Zen, Synapitec together with the command tools, and different repository systems. You don't get to choose between the different Yast frontends, where just the look changes according to the environment. If the user has problems with the actual interface, that could be a problem though... I dunno, but I'd really like to avoid Yast-Qt's package selector... It's unnecesarly complex and I understand why it badly needs documentation. Anyway, we haven't yet discussed the Yast-GTK package selector interface with the Yast team. I will start a discussion about that next week. yast-public would be the appropriate place, so if you want to register (its very low traffic): http://forge.novell.com/mailman/listinfo/yast-public . Feel free to start it yourself, but I won't be active for some days. Cheers, Ricardo
So please consider these points as well and try to make this thing called YaST better documentable...
Andreas Hanke
-- "Ubi non accusator, ibi non judex." (Where there is no police, there is no speed limit.) -- Roman Law, trans. Petr Beckmann (1971) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org