Em Sexta, 22 de Setembro de 2006 15:13, o Andreas Hanke escreveu: > Hi Ricardo, > > Ricardo Cruz schrieb: > > I understand that you guys don't go with Yast-GTK by default (the > > package selector should still be loved for a bit longer :)), but it would > > be nice if you did the needed arrangement to /sbin/yast2, so if people > > choose to install it and are using Gnome/XFCE, that frontend is used. > > what do you think about adding a a possibility to override the > auto-guessed setting. Maybe a setting YAST2_PREFERRED_FRONTEND somewhere > in /etc/sysconfig with these values: > If people would like that, it doesn't hurt to have... But it may make more sense to make that user specific, no? Having such a option in a file under ~/.yast2/. But we can just as well eat from both cakes; just load both files from the /sbin/yast2 script and, if ~/.yast2/frontend exists and the option variable is set, it would overrule the global setting.
Anyway, I don't currently have the opportunity to follow the factory development, so that's out of my scope. Also, since yast-gtk isn't installed by the Gnome pattern or any other, it will just be installed if the user chooses to, so it isn't something we need to make ready for this release. > auto: Guess the best matching of the installed frontends for the current > environment, i.e. gtk for GNOME, > qt for KDE and maybe fvwm2 Actually it may make more sense to use the GTK frontend on FVWM. FVWM seems to have some GTK+ hooks that make them use its colors and more. > Possible use case: GNOME is slightly broken in Factory right now, I'm > using KDE therefore but still want to test yast2-gtk ;-) > Okay. By the way, you can always test it by going directly to the source rather than using the yast2 launcher. That is, for the printers setup tool: kdesu /usr/lib/YaST2/bin/y2base /usr/share/YaST2/clients/printer.ycp gtk Or fooling yast2 script by doing: xhost + localhost su - WINDOWMANAGER=gnome yast2 Notice that any GTK application in Suse KDE is pretty ugly. It uses a theme that emulates the KDE one, but it has some problems like using big fonts and etc. Also, yast-gtk look is designed to feel like the interface provided by GtkAssistance (that will obsolete GnomeDruid), which is used by Gnome setup tools and I believe will be by XFCE as well. So, it will feel pretty alien elsewhere. Not that yast-qt feels much better in KDE. ;) Which btw I would vote to add a kde feeling to it and integrate it on kcontrol for a future release. > Another question (slightly off topic, sorry): How and where do I report > bugs involving yast2-gtk? bugzilla.novell.com? Which information is > needed - just the usual /var/log/YaST2, something else? Whom do I assign > this to? > I don't know how to work with bugzilla much.. The other mail bug report was my first experience with it actually. :/ There is a YaST section... I guess we probably should use that, because the user doesn't necessarly know if its the interface that is not showing the right information or the backend that is providing false information. I don't really want to have to go check the bugzilla website and look for new bugs. Is there any mechanisms so that I can get report notifications to Yast by email? Then I could even set a filter on text like "interface" and "gtk" to read those more carefully. Meanwhile, you may email to the maintainers listed on AUTHORS. Cheers, Ricardo > Andreas Hanke -- New crypt. See /usr/news/crypt. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
