Le mercredi 26 juillet 2006 à 09:05 -0400, Matthias Clasen a écrit : > On 7/26/06, Fernando Herrera <[EMAIL PROTECTED]> wrote: > > Humm I'm seeing a problem here. What about GNOME/GTK+ applications > > launched outside a gnome-session? (for example people using KDE). > > > > They won't get the gtk-modules XSETTING and then they won't be accesible at > > all. > > > > I guess that the solution that Kristian pointed (gtk loading auto > > loading "runtime modules" provided by the platform) may solve this > > problem: > > > > - gtk_init --> load_init_modules: > > - gnome a11y module --> Check a11y gconf key --> load gail and friends > > - bug-buddy module --> install segv handler. > > > > the downside of this method is that if we have installed gnome a11y > > modules then we are adding a little bit of overhead to only-gtk > > applications (loading gnome-module because it is installed, loading > > gconf, checking a11y). > > > > GTK+ programs running outside a session can either fall back to the > GTK_MODULES envvar or use an xsettings manager even if they > are running under, say, KDE. That was the initial idea of xsettings > anyway, and I believe there is a xsettings manager for KDE that > some distributions use.
xsettings-kde : ugly hack but it works not so bad.. I might add accessibility in it too but I need to check if KDE has some accessibility key. http://cvs.mandriva.com/cgi-bin/viewvc.cgi/soft/xsettings-kde/ -- Frederic Crozat <[EMAIL PROTECTED]> Mandriva _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list