On Thu, 2008-10-09 at 16:03 +0200, Murray Cumming wrote: > On Thu, 2008-10-09 at 15:04 +0200, Paul Davis wrote: > > On Thu, 2008-10-09 at 15:02 +0200, Murray Cumming wrote: > > > On Thu, 2008-10-09 at 05:54 -0700, Chris Share wrote: > > > [snip] > > > > first thing to realize: you *must* build gtk-osx from source, along with > > > > the whole GTK dependency stack. jhbuild makes this pretty easy, most of > > > > the time. > > > [snip] > > > > > > Why isn't the new "framework" good enough? > > > http://www.gtk-osx.org/ > > > > its OK for developers to use if they have no need to do deeper level > > debugging (i.e. modify the code). > > Well that's as true (not needed generally, I mean) for Linux and Windows > as for MacOS, I'd guess.
there are a lot more bits and pieces of gtk/osx that are not right yet than is the case under X11 or windows. as a result, if you're actually trying to get a reasonably complex app to work, you're likely to want to draw from svn much more often than with either of those other backends. with X11, its fine to just use the last released version - nothing critical is likely to be a problem there, and any new stuff is probably mostly minor. but consider that on gtk/osx, DnD within certain widgets (e.g. the treeview) is still totally broken. or that basic changes to the idle-update mechanism are still under discussion. or that the mechanism to make sure that shortcuts activate "top menu" items is still under development. these sorts of issues don't arise with other backends (win32 to a small degrees, but still) --p _______________________________________________ gtkmm-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gtkmm-list
