Linked by Thom Holwerda on Mon 8th Feb 2010 13:23 UTC, submitted by kragil
Thread beginning with comment 408787
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2007-02-17
There is a problem with C# ... part of the hooks that C# programs use are Microsoft's patented, closed technologies.
This makes C# and .NET unsuitable for use on a FOSS platform.
Happily, for KDE/Qt, from a users perspective, there is no need to install support for C# and .NET programs, because there are as yet no compelling applications.
As a programmer, you quite possibly find C# and .NET interesting to program, but you may find that your program will be very short on users amongst those that use a KDE/Qt desktop.
Relating all this back to the topic at hand, which is this: "Introducing Pinta, a Gtk+ Clone of Paint.NET". You will probably find that KDE users won't bother with Pinta, because it requires Mono (which isn't installed with KDE by default), and KDE already has Krita, which is more functional, way more stable and mature, and is better integrated into the KDE desktop.
http://en.wikipedia.org/wiki/Krita
http://www.krita.org/
http://www.krita.org/features
It will be a long, long while before Pinta ever reaches parity (in terms of both functionality and performance) with Krita on a KDE desktop, if indeed it ever does.
Edited 2010-02-11 02:12 UTC