There are already Qt libraries for Mono - they're called Qyoto [1], and
they're maintained by the KDE team. They're basically a thin wrapper
around Qt using some automated tools. That means that they're far more
object-oriented friendly than GTK# *except* when it comes to connecting
methods to events ("signals" in the Qt world), which require the use of
a string for the signal name, causing errors in connecting events to not
emerge until you actually run the code.
Anyway, that's how it used to be when I last tried Qt a few years ago.
It also seemed less stable than GTK# (it crashed out for reasons I
couldn't understand), and I needed a script to manually run the Qt .ui
files through a compiler to genereate the .cs files. Great
possibilities, but it just didn't have the interest to get it all ironed
out and working.
I think the biggest reason for the low take-up of Qt support is that
Mono started as a Gnome-based thing and so focused on GTK. KDE were
already using Qt/C++ and didn't seem to take up C# as much.
[1] http://techbase.kde.org/Development/Languages/Qyoto
On 10/08/12 12:43, philippe.monteil wrote:
http://blog.qt.nokia.com/
Given the multiplateform nature of Qt and Mono, I would really like to see a
strong connection between the two...
--
View this message in context:
http://mono.1490590.n4.nabble.com/Qt-acquired-by-Digia-tp4650866.html
Sent from the Mono - General mailing list archive at Nabble.com.
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
_______________________________________________
Mono-list maillist - [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list
