What function does tdebindings serve? Does anyone
actually
utilize the language bindings?
Primary function is to frustrate packagers and developers. :)
After R14 there are some applets I want to convert to Trinity. They are written in Python
with GTK GUI. I would like to convert the GTK hooks to TQt3 to integrate the applets.
A really big project I would like to find volunteers to help is to port a C project coded
in GTK to TQt3. The underlying base program needs no change, just the GUI side.
I have a few shell scripts I would like to convert to Python so I can add a GUI. KDialog
is bearable for small shell scripts but the few scripts I have in mind are large scripts.
Adding a GUI with KDialog would be a mess and would not provide the full point-and-click
functionality I envision. Rewriting would be better and Python seems suited for that kind
of app.
In other words, I see usefulness from tdebindings.
I think (I hope) the problem with building is simply that Tim has moved on to TQt3 and I
need to build from that base rather than Qt3. I built kdebindings 3.5.13 although I needed
several patches (bug report 597).
tdebindings is one of those packages most people avoid building. As a team, if we want to
provide a quality product, we need to ensure tdebindings will build even when we
personally don't have a use. :)
Okay, I'm off my soap box now.
Darrell