Linked by Thom Holwerda on Mon 8th Feb 2010 13:23 UTC, submitted by kragil
Graphics, User Interfaces You may remember that back in November last year, I wrote about the lack of a decent Paint.NET-like application for Linux (or, more specifically, for Gtk+ distributions, since Qt has Krita). As it turns out, this compelled Novell employee Jonathan Pobst to code a Paint.NET clone in Gtk+ using Cairo. Version 0.1 is here, and it's remarkably advanced for something so young.
Thread beginning with comment 408324
To read all comments associated with this story, please click here.
Good but...
by ebasconp on Mon 8th Feb 2010 16:37 UTC
ebasconp
Member since:
2006-05-09

Though I am happy with the clone; I would have want it to be done using Qt.

Just a personal feeling! ;)

Reply Score: 2

RE: Good but...
by robojerk on Mon 8th Feb 2010 17:28 in reply to "Good but..."
robojerk Member since:
2006-01-10

Whatever happened to Qyoto (C# and .Net bindings for Qt)?

Reply Parent Score: 2

RE[2]: Good but...
by Beachchairs on Mon 8th Feb 2010 19:38 in reply to "RE: Good but..."
Beachchairs Member since:
2009-04-10

The full C# KDE library, and thusly some C# Qt library, is listed as fully supported and mature by www.kde.org

I _think_ it still uses Qyoto. I think C# just hasn't made the same splash on KDE/Qt as it has on Gnome.

Reply Parent Score: 3

RE[2]: Good but...
by lemur2 on Tue 9th Feb 2010 00:12 in reply to "RE: Good but..."
lemur2 Member since:
2007-02-17

Whatever happened to Qyoto (C# and .Net bindings for Qt)?


Why would anyone use C# for Qt, when there are perfectly good Qt bindings for Python, C, C++, Ruby and Java?

If you have Qt libraries installed, why would you bother also with Mono?

It isn't as though KDE needs anything like a Paint.NET clone, when it already has the more functional and far more mature Krita program.

KDE doesn't need Banshee ... it has Amarok.
KDE doesn't need FSpot ... it has digikam.
KDE deosn't need a Paint.NET clone ... it has Krita.
KDE deosn't need GNOME Do ... it has krunner.

In each case above, with the possible exception of the last, the native KDE application is better and more functional than the GNOME/Mono try-hard equivalent.

Hence, KDE doesn't need C# and Mono at all, there is no point.

Reply Parent Score: 2