[Mono-devel-list] Gtk# vs. gtkmm (Gtk- - )
jonpryor at vt.edu
Tue Oct 7 08:09:05 EDT 2003
I would argue that Gtk# is still in its infancy.
That doesn't mean you shouldn't use it. It just means that if you *do*
use it, you should expect to (a) find bugs, and (b) PLEASE report those
bugs in bugzilla.
The documentation can always use improvement, but it's fairly
straightforward to map the GTK+ C documentation to Gtk# classes/members,
so you can always read the GTK+ docs if you need to.
As for which to use...
With Gtk#, you stay in C#, which should simplify communication between
your frontend and your backend. You also simplify the building
requirements and (somewhat) minimize the runtime requirements for your
app (you wouldn't need the gtkmm libraries in addition to GTK+ libs and
You also get the coolness that is Glade# plus
"Glade.XML.Autoconnect(this)", which makes it trivial to map Glade
functions to class methods.
Plus, Garbage Collection. Though gtkmm shouldn't have memory issues, if
they used the "resource acquisition is initialization" pattern properly.
With gtkmm, you get a more mature wrapper, which likely has fewer bugs.
This could save development time, but it'll complicate frontend/backend
code interaction. I don't know if it'll *greatly* complicate things --
it depends on how you implement it -- but it certainly won't be as easy
as staying within C#.
On Tue, 2003-10-07 at 01:08, Joe Scaduto wrote:
> Hey I am a newbie to Mono. I am currently working on a project which
> uses C# and I would like to create a frontend in either gtkmm (C++
> wrapper for Gtk+) or Gtk#. However, I do not have experience in
> either. I was wonder if anyone has any information concerning the
> implications in implementing in Gtk# rather than gtkmm. I found good
> documentation for gtkmm but not for Gtk#...is it still in its infancy?
> I would appreciate any input.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
More information about the Mono-devel-list