On 13/12/2018 17:46, Istvan Gabor wrote:

I don't know if the subject term correctly describes what I want. How can I identify the toolkit an application uses? For example how can I find out whether my pulseaudio or audacious program uses gt2 or gtk3, or my vlc uses qt2/qt3/qt4?

For example if I want to change the look of pulseaudio sliders I have to know which theme to modify, gtk2/gtk3 etc.

That's a good question, to be fair. I have never looked into it, because I avoid themes & themeing as much as possible. You could look at the package's dependencies in Yast's software management module -- but it's possible some apps might statically-link the libraries they use, so it might not tell you. If so you could Google the specific version of the specific app, and if you can find its developer, they might describe what it uses. -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/13/18 11:46 AM, Istvan Gabor wrote:

Hello:

I don't know if the subject term correctly describes what I want. How can I identify the toolkit an application uses? For example how can I find out whether my pulseaudio or audacious program uses gt2 or gtk3, or my vlc uses qt2/qt3/qt4?

For example if I want to change the look of pulseaudio sliders I have to know which theme to modify, gtk2/gtk3 etc.

Thanks,

Istva

One way would be to run the app under strace, e.g., "strace -eopen [exe_name] 2> strace.out" and then examine strace.out for the files that are opened, then run "rpm -qf "file" to determine which package a selected file comes from.  This you could do right now, but it's a little tedious.  You may see quite a few such files indicating ENOENT (the sought file doesn't exist) which can signify that the exe is looking for another library that's not installed, which may in turn indicate an easy way to update or customize the app... but check out the code first. Another and I think better way would be to download the source rpm.  Obviously that will tell you the linked libraries (which, btw, is likely the term you were looking for) and, if you're going to play around with an app's GUI widgets, you'll want to download the source anyway.  Sometimes the README talks about compiling with a different GUI, so be sure to look there, otherwise you'll have to poke around through the source files, again, something you'll be doing anyway if you go on to trick out the code. hth, have fun. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org