Re: application class thoughts

On Apr 5, 2010, at 10:24 AM, Cody Russell wrote:

> On Mon, 2010-04-05 at 10:15 -0700, John Ralls wrote:
>> Menubars are an interesting problem. The Gtk+ paradigm is that each
>> window has its own menubar, and there is no requirement that different
>> windows' menubars should have the same contents. OSX, on the other
>> hand, normally uses a single menubar for an application. Fortunately,
>> both Cocoa and Carbon allow this menu to be switched at will, so it's
>> easy to follow the Gtk+ paradigm with a focus signal handler. Carbon
>> has a problem with the App menu because there's only one, so one can't
>> just use the usual "emit the GtkMenuItem action signal" approach; the
>> GtkMenuItem goes away when the window is destroyed. Fortunately, Cocoa
>> has a separate App menu for each mainMenu, so that particular problem
>> goes away.
> But Carbon is deprecated anyway, right?  So if one were to try to design
> support for all this into gtk 3.0, would it hurt to just ignore Carbon
> and design for Cocoa?

You're correct. A Cocoa-based mac integration library will be available soon, and the older Carbon-based ige-mac-integration will be deprecated in Gtk-OSX. I hope large chunks of the new integration code will be able to migrate into Gtk+ 3. 

John Ralls

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]