Star Can KDE Save a Dying Windows Platform?
Linked by Thom Holwerda on Sun 3rd Feb 2008 23:09 UTC, submitted by Moochman
KDE This article details the story of a KDE-loving software engineer who was forced to use Windows for his job. "His only hope was that he knew Qt was cross compatible with Windows Linux and Mac, and there was talk that someday, KDE was to be ported to Windows. So he waited. Well, KDE4 was announced and there was much joy. Betas were released and there was much bitching. KDE4.0.0 was released and there again was much joy (and still a little bitching). More importantly an actual honest to goodness Windows port is released. Here follows that engineer's report."
E-mail Print r 3   77 Comment(s) http://osne.ws/ev3
Thread beginning with comment 299262
To view parent comment, click here.
To read all comments associated with this story, please click here.
gustl
Member since:
2006-01-19

Question:

Would KDE in cross-Platform C# (=Mono) be easier to implement than in Qt and C++?

This is not trolling, I honestly have no Idea, as I never learned C#.

And by the way: Only answers from People who used BOTH languages for a time count in my book!

Reply Parent Bookmark Score: 2

google_ninja Member since:
2006-02-05

I have used .net, mono, and qt before, but I have never used the qt bindings for mono (http://cougarpc.net/qyoto/).

That being said, I would say it is probably easier using C++/Qt at this time simply due to the tools available. KDevelop and QtDesigner are full featured, mature apps. Monodevelop hasn't hit 1.0 yet. If you are a "real men code in vi" kind of guy though, I would give it a try. The Qt bindings are generated off of the Qt header files, so you use it in pretty much the same way. The big differences would be the managed aspects, different style of libraries, the loads of syntactical sugar in C#, and the whole managed aspect.

Reply Parent Bookmark Score: 2