[Mono-dev] C bindings VS C++ bindings (Gtk# vs. Kimono?)

"Andrés G. Aragoneses [ knocte ] "Andrés G. Aragoneses [ knocte ]
Mon Sep 24 05:14:42 EDT 2007


Mirco Bauer escribió:
> On Fri, 2007-09-21 at 16:49 +0200, "Andrés G. Aragoneses [ knocte ]"
> wrote:
>> Brandon Perry escribió:
>>> I much prefer the Qyoto/Kimono bindings for cross-platform because of
>>> it's elegance and it looks much better IMHO on Windows than Gtk#. I
>>> haven't run into /too many/ bugs (just a couple, they might have even
>>> been resolved by now) with the Qyoto/Kimono bindings. Those are really
>>> the only reasons why I prefer Qyoto/Kimono over Gtk#.
>> Thanks for your answer.
>>
>> Those bugs you found, have to be fixed upstream (Qt) or on the binding 
>> itself?
>>
>> BTW, what do you use for creating interfaces with Kimono? Do you use a 
>> general QT designer that generates XML that can be consumed by any 
>> binding? (If not, we have here an advantage for Gtk#: Stetic in MD.)
> 
> And don't forget glade, since glade3 it's fun to make GUIs :)
> 
> Our company develops business applications using C# / Gtk# / Glade# /
> gettext.
> GTK+/GTK# gives us a permissable license (LGPL), a _very_ stable ABI/API
> (didn't break since GTK+ 2.0, and today we are at 2.12) and workable
> release cycles.
> Gettext integrates very well on windows using Mono.Posix.dll, glade also
> supports I18N through gettext out of the box.

We've also researched about the best portable I18N method, and we have 
discarded Mono.Posix until bug 
https://bugzilla.novell.com/show_bug.cgi?id=MONO82850 is closed 
(actually not a bug, but a RFE).


> Theming is indeed a bit strange/ugly in GTK+, not well documented, but
> is very flexible.
> 
> Gtk# builds on windows lack behind Gtk# on linux, like there is no Gtk#
> 2.10 installer for windows yet. This is not really a GTK+ nor GTK#
> issue, but a porting/community issue. GTK# is an official GTK+ binding
> but there are no official windows ports/builds. Paco is doing them as
> good and often as he can (and they are _very_ good), but there is
> sometimes lag.

Perhaps it's a porting/community issue, but it's an issue that affects 
companies and thus it comprises the stability of the whole choice.


> In total I am very happy what GTK# gives us (the company) and it works
> very well.
> 
> I have no experience with QT neither Kimono.

Thanks for your answer.

Regards,

	[ knocte ]

-- 




More information about the Mono-devel-list mailing list