tag:blogger.com,1999:blog-11264158.post-1146440765691369412006-04-30T15:48:00.000-07:002006-04-30T16:46:05.706-07:00So, how is KDE4 going to understand its own API? It's now May of '06, and the most promising projects I was keeping an eye on haven't been publishing much.<br /><br /><h3>Java Bindings</h3><br /><br />aseigo <a href="http://aseigo.blogspot.com/2005/10/troll-tech-dev-days-05-in-san-jose.html">leaked </a> word of Trolltech working on Java bindings for Qt &mdash; based off the KDevelop parser, IIRC. It was supposed to be available in Q1 '06, but nary a whisper of it now. It wasn't ever really official, but I was looking forward to everyone having something standard to <span style="text-decoration: line-through">steal</span> base KDE bindings on. I hope it's not dead (or castrated like QSA).<br /><br /><h3>KJSEmbed</h3><br /><br />The presumed <i>standard</i> language binding. Is it intended to be a full Qt binding? Or something more practical, for use in KDE applets and such? I have no clue what state it's in right now. I'll cross my fingers.<br /><br /><h3>The Introspection Problem</h3><br /><br />It is <i>really hard</i> to get a detailed API listing for Qt (let alone KDE) to use in a program. This has serious consequences for KDE, the best known of which is difficulty with language bindings. The lack of an API listing leads to <a href="http://www.trolltech.com/products/qsa/index.html" title="QSA">half-measures</a> and <a href="http://www.riverbankcomputing.co.uk/pyqt/" title="PyQt">ugly workarounds</a>. <a href="http://www.kdedevelopers.org/blog/89">Richard</a> is successful with his cluster of language bindings because he knows how to tickle the data out of Kalyptus. I just wish it was easier.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/11264158-114644076569136941?l=jahqueel.blogspot.com'/></div>Ashnoreply@blogger.com2