On Wednesday 11 April 2007 14:40, Ricardo Cruz wrote:
• We don't have a yast2-kde yet, only a yast2-qt.
We probably should, now that we have GTK for Gnome folks. We could use KDE file dialogs,
We have them anyway if KDE is installed. There is some magic in our KDE libs that supersede the KDE file dialogs with the standard Qt file dialogs. And besides, we don't use file dialogs too heavily anyway.
and we could push things like icons on buttons,
We already have everything in place for that. It's not a technical issue, it's more an issue of providing all the icons and have it consistent. It wouldn't do to have some buttons with icons and most others not. http://forgeftp.novell.com///yast/doc/SL10.2/tdg/PushButton_widget.html ("IconButton")
tooltips, etc.
Tooltips is another thing that does not in the least depend on KDE. Qt provides everything for it. But still all the texts would need to be written, proof-read, translated, and of course maintained. That's why so far we decided not to use them. Pushing the YaST2 Qt UI more towards KDE would only fuel the KDE haters flames IMHO. There is little, if anything, to be gained.
• There is a significant overhead to run the VM
I hear you. The Mono usage in Gnome makes me cripple. ;) I can live with Python because I can see clear advantages for both the programmer and the user (really nice to poke at its skeleton at run-time ;)). I personally never noticed any y2base overhead,
Look at "RSS" in "top" or related tools. It does come at a cost. You don't want that running without a good reason.
but I have never done any profiling on it, so... Possibly its touching on the log files may suck at startup?
Eh - huh? No. Do an "strace". Look at what it all does. Then think twice if the log file (singular, it's only one until they get wrapped) might be of any significance.
(of course, we could fix it...)
I guess the big point here: * The work is done. If it ain't broken, don't fix it.
That's a major point, too, of course.
I like ycp as much as anyone, but I don't think it is appropriate here.
Maybe. I would personally like to see it stretched a little bit :)
We should avoid doing things that affect all users just for the fun of it. In
particular when it comes to make heavy use of the users' machines' resources
without having a really good reason. This might heavily affect users'
acceptance of our distribution. There are already those who keep claiming
that SUSE distros use too many resources. We should not give them more
ammunition for them to shoot at us.
CU
--
Stefan Hundhammer