New Python/C# Bindings Expand KDE Languages 18
Dre writes: "Today marks a special coincidence. First,
Adam
Treat released the initial version of
Qt bindings for C#,
which consists of 476 Qt classes converted to C#.
The bindings work with the Mono
compiler, runtime environment and class libraries, enabling a fully Open Source implementation of C# for Qt. While not yet ready for
a real application, Adam has managed to write and execute a
Hello World! program
(screenshot).
KDE bindings are on the drawing board. Shortly thereafter,
Phil Thompson, Jim Bublitz and
theKompany.com
released KDE 2 and KDE
3 bindings for Python. Together with the Java, Objective C and C bindings in the
kdebindings
module, as well as the
Ruby
bindings, KDE is providing developers a broad gamut of application
development languages."
Perl (Score:2)
Re:Perl (Score:1)
kalyptus is in the KDE cvs under kdebindings/kalyptus.
The main technical obstacle to producing Perl bindings for Qt 3/KDE 3 is that they assume that the moc generated code works like Qt 2. Qt used to call slots via function pointers, but in Qt 3 it uses an integer offset into the slot table.
So the slot/signal handling needs to be redone to get the Perl bindings to work.
And Common Lisp for Qt/KDE should certainly be possible.
-- Richard
3rd post! (Score:1)
Why? (Score:2, Interesting)
Why?
Okay, okay. This has probably been covered in other Slashdot articles covering C#,
Alright, I'll spare you the rants and reasons on the subject - you've heard them all before - but my point is here is not necessarily my own beliefs and opinions on the C#/.NET situation. My point is that this is something that _most_ of us (in my experience) are rejecting outright. I think Miguel de Icaza is crazy for spouting pro-.NET rhetoric in the GNOME project when there's such a clear lack of support of most of his community, and this Qt thing just doubles that across both desktop environments.
Am I totally out of line here? Will anyone _actually_ use this? Is there really a population of hackers out there who will be writing X apps with C#? Personally, I'm highly dubious about the whole thing. If you agree with me, reply. If you don't, reply. But flames can be filed in
--Garthnak
Re:Why? (Score:2, Insightful)
So, choose our language, and get some support behind it. Witness the wonder that is KDevelop
But, yes, bollocks to C#
Dave
Re:Why? (Score:2, Insightful)
If I have to rewrite my 20,000 line application just so I can have a KDE-native version, then I'm probably not going to do it. However, if all I need to do is link in with a particular binding, and change some of the interface stuff, then things seem much more likely.
One should be looking at things from a "The Right Tool for the Right Job", and you can't answer that question with support for just one or two languages, or even 5. There are going to be applications that call for a particular set of languages and libraries. Its not your choice to decide what the 'right' language is, but instead the application developer.
Re:Why? (Score:1)
Since Visual Studio
In my opinion, it could only help the development of Qt based apps once C# developers realize they can easily develop in a syntax they're used to.
Work on this project needs to start now so that when that day comes, the C# developers will have the tools they need. It's a matter of anticipating the needs of future Microsoft-flavored programmers when they make the switch to a superior OS.
Let the flames begin,
Mike D
Re:Why? (Score:2)
1) because they can
2) because they felt like it
I'm so sick of these "why are we doing this! whine!" questions. Nobody is forcing you to use C#.
Languages are like hammers (Score:2, Insightful)
You pick the language you are familiar with or most importantly of all - the language that makes it easier for you to solve a problem (doesn't matter if it's scientifical app or GUI or
Languages are just like a regular tool, you pick the right one to do the job.
If you want to do some heavy crunching you pick a heavy hammer (fortran, C) and vice versa.
In this case they want people to use *their* favourite language to make GUI applications for KDE.
Uh... no. (Score:2)
Well, they didn't. Actually, a first beta was released, and even that is not yet mentioned on the linked page.
Which is a pity, because, having tried the alpha versions, programming with PyKDE is really, really nice. Unfortunatly it's quite a huge package, so unless Distributors ship it by default, you shouldn't expect users to be too happy it you tell them to compile it themselves.
Yea! (Score:3, Interesting)
Re:Yea! (Score:1)
They are working on an OS X/Darwin port too!
To back up my statement:
[Mono-list] (MacOSX) Requesting porting guide clarifications
http://lists.ximian.com/archives/
Re:Yea! (Score:2)
It's a trap! (Score:1)
is just asking for trouble from M$!
Fight the power!