• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Cross-platform toolkit with a Cocoa backend
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cross-platform toolkit with a Cocoa backend


  • Subject: Re: Cross-platform toolkit with a Cocoa backend
  • From: Alastair Houghton <email@hidden>
  • Date: Fri, 6 Jul 2007 17:54:50 +0100

On 6 Jul 2007, at 17:23, Felipe Monteiro de Carvalho wrote:

I was thinking if there are people here that working implementing a
Cocoa version of a cross-platform toolkit.

Cocoa used to be cross-platform, and probably still is inside Apple, judging by the fact that they have Safari running on Windows now.


There are a couple of third-party attempts to implement a Cocoa API on Windows as well; GNUStep has been working in this direction (though they only care about OpenStep APIs, I think), and there's Cocotron as well. Neither of them are a complete solution, and AFAIK GNUStep apps don't have the UI that Windows users would expect. I haven't used either of them extensively myself, so I can't really say more than that.

How can this be done? Should one try to generate .nib files on the
fly, based on the calls to the framework, or just try to work without
them? Or, of in another way, how?

You don't need to use nib files. In fact, nib files are just archives of objects that you could have created and wired-up yourself.


I know this is a very generic question, but Cocoa is very different
from other GUI libraries,

I think that's something of a generalisation. Windows programs generally work the same way (that is, your UI is defined by using a resource editor, which saves resource files, which are similar in purpose [though not design] to nib files). Carbon programs do too, I believe. So do programs written for some older systems (GEM, for example). In all of those cases, however, it's possible to construct UI at runtime rather than loading it if you want.


Perhaps the biggest difference between these systems and the ones that historically have tended to use code to define their UIs is that the latter generally make use of automatic layout (and I don't just mean springs and struts; I mean layout managers).

Kind regards,

Alastair.

--
http://alastairs-place.net


_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Cross-platform toolkit with a Cocoa backend (From: "Felipe Monteiro de Carvalho" <email@hidden>)

  • Prev by Date: Re: NSSavePanel and allowing unknown extensions
  • Next by Date: Core Data thread safety question
  • Previous by thread: Re: Cross-platform toolkit with a Cocoa backend
  • Next by thread: Re: Cross-platform toolkit with a Cocoa backend
  • Index(es):
    • Date
    • Thread