25 Jan
2014
25 Jan
'14
7:04 a.m.
Darrell, All,
I have built both gtk-qt-engine & gtk3-tqt-engine packages. I am not sure what
should dictate the use or installation of one, or the other, or both? I don't
understand the difference. Both are designed to provide similar feel for gtk
apps running in TDE, with the former updating gtk-2.0 configs, and I presume the
latter does something similar for gtk-3.0 based apps. The confusion is why 2
applications? Why not just extend one, or the other, to cover both gtk-2.0 and
gtk-3.0 apps?
With 2 apps is there some logic that tells gtk-2 and 3 apps to use the
different engines to create different configs on icon-set or widget-style
changes? Are there now two configs in thelpcenter?
Initially, my first concern was that the packages would conflict. But after
building, it is apparent they will not:
tde-gtk-qt-engine-14.0.0-1-x86_64.pkg.tar.xz:
opt/trinity/share/applications/kcmgtk.desktop
opt/trinity/share/locale/de/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/bg/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/fr/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/nn/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/tr/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/es/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/ru/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/sv/LC_MESSAGES/gtkqtengine.mo
opt/trinity/share/locale/it/LC_MESSAGES/gtkqtengine.mo
opt/trinity/lib/trinity/kcm_kcmgtk.la
opt/trinity/lib/trinity/kcm_kcmgtk.so
usr/share/themes/Qt/gtk-2.0/gtkrc
usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so
tde-gtk3-tqt-engine-14.0.0-1-x86_64.pkg.tar.xz:
opt/trinity/lib/libtqtcairo.so.0
opt/trinity/lib/libtqtcairo.so.0.0.0
opt/trinity/lib/libtqtcairo.la
opt/trinity/lib/libtqtcairo.so
usr/share/themes/tdegtk/gtk-3.0/gtk.css
usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.so.0.0.0
usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.so
usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.so.0
usr/lib/gtk-3.0/3.0.0/theming-engines/libtdegtk.la
Anybody have both installed currently?
--
David C. Rankin, J.D.,P.E.
25 Jan
25 Jan
8:03 a.m.
New subject: [trinity-devel] Difference between: gtk-qt-engine & gtk3-tqt-engine
Darrell, All,
I have built both gtk-qt-engine & gtk3-tqt-engine packages. I am not
sure what
should dictate the use or installation of one, or the other, or both? I
don't
understand the difference. Both are designed to provide similar feel for
gtk
apps running in TDE, with the former updating gtk-2.0 configs, and I
presume the
latter does something similar for gtk-3.0 based apps. The confusion is why
2
applications? Why not just extend one, or the other, to cover both gtk-2.0
and
gtk-3.0 apps?
The GTK2 engine and the GTK3 engine have radically different designs. The
GTK3 engine uses the new TQt3 style API, whereas the old GTK2 engine
creates TQt3 widgets in the background and copies their contents to the
screen. The GTK3 engine is therefore much more efficient and uses much
less memory, but as GTK3 is not yet feature complete, glitches remain in
the rendering.
With 2 apps is there some logic that tells gtk-2 and
3 apps to use the
different engines to create different configs on icon-set or widget-style
changes? Are there now two configs in thelpcenter?
Same config. You can enable or disable each engine independently from the
same TDE control center module.
Tim
8:30 a.m.
New subject: [trinity-devel] Difference between: gtk-qt-engine & gtk3-tqt-engine
On 01/25/2014 02:03 AM, Timothy Pearson wrote:
The GTK2 engine and the GTK3 engine have radically
different designs. The
GTK3 engine uses the new TQt3 style API, whereas the old GTK2 engine
creates TQt3 widgets in the background and copies their contents to the
screen. The GTK3 engine is therefore much more efficient and uses much
less memory, but as GTK3 is not yet feature complete, glitches remain in
the rendering.
Thanks Tim,
While I've got you, if you get a chance, take a look at the k3b bug:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1858
It is an invalid use of incomplete type mpc_decoder... and error:
'mpc_streaminfo_init' was not declared in this scope issue. I don't think it
will be bad for a smart guy to fix :-). The 2 biggies I'm waiting on are k3b,
then I think k9copy will build. Thanks.
--
David C. Rankin, J.D.,P.E.
> With 2 apps is there some logic that tells
gtk-2 and 3 apps to use the
> different engines to create different configs on icon-set or widget-style
> changes? Are there now two configs in thelpcenter?
Same config. You can
enable or disable each engine independently from the
same TDE control center module.
Tim
9:52 a.m.
New subject: [trinity-devel] Difference between: gtk-qt-engine & gtk3-tqt-engine
On 01/25/2014 02:30 AM, David C. Rankin wrote:
Thanks Tim,
While I've got you, if you get a chance, take a look at the k3b bug:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1858
It is an invalid use of incomplete type mpc_decoder... and error:
'mpc_streaminfo_init' was not declared in this scope issue. I don't think it
will be bad for a smart guy to fix :-). The 2 biggies I'm waiting on are k3b,
then I think k9copy will build. Thanks.
Disregard,
I fixed it - bad header (mpcdec.h) from older musepack-tools... Bad stuff...
Bug closed.
--
David C. Rankin, J.D.,P.E.
4031
days inactive
4031
days old
3 comments
2 participants
participants (2)
-
David C. Rankin -
Timothy Pearson