I also don't see where is the problem in having two different interfaces to the package manager. That's the whole point in my opinion. GNOME and KDE are different environments with different philosophies and different users. So having a perfect GTK clone of the YaST-qt tools is not the point: a theme would have been enough for that.
My point was not about GTk vs QT and which was better or worse... it was about the change in workflows. Do you run one computer with one window manager? or do you administer multiple computers across multiple locations? If it was one computer with one window manager, I could care less, but the issue arises when you are dealing with more than one wm on multiple computers... If you guys who are disagreeing here read carefully what I wrote, I am not advocating GTK over QT, or QT over GTK. I am saying that the tool itself needs to have a common workflow regardless of window manager. Does it make logical sense to develop a core tool (that should NOT be window manager specific) in two different paths? YAST should not be KDE or Gnome or any window manager centric. It is a common tool for setting up and administering openSUSE.. not Gnome.. not KDE. This is the issue. C. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org