[Kde-bindings] clib test app not working...

Richard Dale Richard_Dale at tipitina.demon.co.uk
Wed Mar 24 16:42:45 UTC 2004


On Wednesday 24 March 2004 16:08, Dominique Devriese wrote:
> Richard Dale writes:
> > On Tuesday 23 March 2004 18:07, Dominique Devriese wrote:
> >> Hi,
> >>
> >> Is the clib program in kdebindings/qtc/clib/ supposed to work ?
> >> Looking at the code, I assume it's supposed to bring up a window,
> >> and such, but it doesn't do so for me.  It just starts, gives an
> >> error about a slot not being defined, and then keeps running
> >> without any visible activity.  I have attached to it a couple of
> >> times with gdb, and apparently it's stuck in a qt_QWidget_show
> >> call, but I can't find the real cause.  Anyway, I can give you more
> >> useful debug stuff if necessary, but first tell me if it's supposed
> >> to not do this...
> >
> > I would still like to kill the QtC/KDE C bindings ASAP. The Smoke
> > library supercedes that.
>
> If the test app isn't working, I also don't think there's much use in
> keeping them.  What other libraries are still using the C bindings as
> a backend ?
Possible some Basic implementation I found on Sourceforge once, I'm not sure. 
Maybe it would be a good idea to search around first. 

> Would it be possible to build new, better C bindings automatically
> with kalyptus ?
Yes it wouldn't be very difficult to generate ones which didn't need manual 
edits. Ashley has suggested a library api called 'Mirror' for languages which 
are too static to use Smoke. I've personally got no ethusiasm for C bindings 
at all though. No one actually wants to do GUI programming in C, they are 
only for implementing bindings for other languages. And Smoke does that so 
much better that I can't see the point.

-- Richard



More information about the Kde-bindings mailing list