Is Qyoto a viable platform?

Question

I don't ever really hear about Qyoto. My question is, is it still around and good to use? Would it be smart to use on one of my projects, or should I stick to gtk# or qt in another language? Are there any projects currently using Qyoto?

Answer 1

I write a small cross platform app in .Net. I originally wrote it on Windows with a WinForms UI. When I ported it to mono I found that the UI really suffered on Linux. In an effort to get a better Linux UI I rewrote the UI in GTK#. It is nice to have the designer, but GTK# is a terrible UI framework when coming from WinForms (never mind WPF). The fact that it is based off of a C framework really shows through. Many things show their procedural roots and it just doesn't feel very .Net centric. None of the controls understand the .Net Framework components. So, for example, you cannot bind a DataTable to a GTK grid control. Also, the documentation is very poor.

Since I use KDE on Linux I've been looking into Qyoto for a long time. Recently I got my application loading a Qt UI. I designed it with Qt Designer and convert the .ui file to C# with the uics tool. This extra step is a pain to someone who's used to Visual Studio. Additionally, Qyoto doesn't really integrate with .Net either. For example, the QT signal/slot mechanism is separate from the .Net event/eventhandler system. Again, the bolts and wires show through.

These and several other factors have forced me to move off of .Net for Linux GUI development. Again, since I use KDE, I will be sticking with Qt. My decision now is between Python and C++. Python is great for RAD, but I'm really looking for a great IDE and that is pushing me toward C++ (Qt Creator).

Answer 2

Last I checked, Qyoto was not stable on Windows. I'm currently using another .NET binding for Qt - qt4dotnet. Works fine but it you can't use Qt Designer with it and the API uses Java conventions because it's based on Qt Jambi. Also there is no integration between .NET events and Qt signals in qt4dotnet.