Originally posted by BlackStar
View Post
Announcement
Collapse
No announcement yet.
Mono 2.8 Is Out With C# 4.0, Better Performance
Collapse
X
-
Originally posted by BlackStar View PostIn short, some UI features seem to be significantly easier to implement in Mono/GTK# compared to C/GTK+. Ergo, the former seems to be a more productive environment for UIs.
Also, it's a bit unfair to compare the current GTK+ to the one 13 years ago. If Gimp was maiden today it wouldn't needed so much time to implement this feature.
Comment
-
Well BlackStar does raise some valid concerns. But GIMP, just like Photoshop on the Mac, shouldn't require a single windows. Adobes explenation for single window on Win32 was that the Windows WM sucked, so they had no choice but to make it a single window.
Comment
-
Well BlackStar does raise some valid concerns. But GIMP, just like Photoshop on the Mac, shouldn't require a single windows. Adobes explenation for single window on Win32 was that the Windows WM sucked major balls, so they had no choice but to make it a single window.
Comment
-
Originally posted by Apopas View PostI didn't disagree but that's why I made the example for QT/KDE.
Also, it's a bit unfair to compare the current GTK+ to the one 13 years ago. If Gimp was maiden today it wouldn't needed so much time to implement this feature.
Obviously, Pinta is a much smaller and leaner project with faster turnaround times which explains a large part of the difference. But still, 1 month vs 1 year is quite significant.
I agree that Qt is much more productive than GTK+, however, if a bit more arcane to setup and use. More productive than GTK#? Honestly, no idea.
I know however, that I won't touch C++ unless I am being paid to do so (as I was in my last job). It's a powerful tool, but unlike Python or C# it's not fun to use - and I want my hobbyist programming to be fun, not onerous.
@kraftman: why don't you spend a couple of years becoming familiar with a few different programming languages, first? One day you'll be looking back to those posts of yours, feeling ashamed. Just sayin'.
Comment
-
Originally posted by V!NCENT View PostWell BlackStar does raise some valid concerns. But GIMP, just like Photoshop on the Mac, shouldn't require a single windows. Adobes explenation for single window on Win32 was that the Windows WM sucked major balls, so they had no choice but to make it a single window.
The response has been overwhelmingly positive.
Edit: Windows WM is painful.
Comment
-
Originally posted by BlackStar View PostI agree. Then again, this feature was implemented in v2.7.1, presumably using GTK+ 2.18 (September 2009 release) which is quite modern. I haven't checked but Pinta is likely using either GTK# 2.18 or 2.20 which shouldn't be all that different. The main difference is that Pinta uses C# which is much more suitable for UIs (lambdas, events, garbage collection, modern module system).
Obviously, Pinta is a much smaller and leaner project with faster turnaround times which explains a large part of the difference. But still, 1 month vs 1 year is quite significant.
@kraftman: why don't you spend a couple of years becoming familiar with a few different programming languages, first? One day you'll be looking back to those posts of yours, feeling ashamed. Just sayin'.
Comment
-
Originally posted by V!NCENT View PostGIMP, just like Photoshop on the Mac, shouldn't require a single windows. Adobes explenation for single window on Win32 was that the Windows WM sucked major balls, so they had no choice but to make it a single window.
Comment
Comment