• 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: Cocoa/Windows parallel dvlpmt
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa/Windows parallel dvlpmt


  • Subject: Re: Cocoa/Windows parallel dvlpmt
  • From: Lotsa Cabo <email@hidden>
  • Date: Sun, 1 Feb 2004 08:45:51 -0500

Phillip,

GREAT mindset! I agree with you 110%.

Too many people these days are stuck in the mud believing that "true" cross-platform development means writing their app in such a way that they can simply compile and launch on another platform; for example, using Java for everything from UI to business to data. And, while this may theoretically be possible, the end result is usually not something that feels as if it was made for the target platform.

I'm still in "discovery mode" trying seek out the perfect mix of technologies for my app so that it can be ported to each platform -- Mac, Linux, and Windows. I've been leaning towards Objective-C, but was told (on another thread) that it's not very easy to port to Windows because of licensing. Any information you know of pertaining to cross-platform ObjC++ stuff would be great.

R/S
Ryan





On Feb 1, 2004, at 8:03 AM, Phillip Mills wrote:

On Saturday, January 31, 2004, at 02:05 PM, Erez Anzel wrote:

I have been happily developing in Cocoa using XCode 1.1. But I have to port to Windows, very quickly. I want to keep my duplication of effort to a minimum, so that I can maintain and enhance both products efficiently.

I've done this kind of thing -- with Linux tossed into the mix as well -- and it made me a great fan of Objective C++.

My strategy was to use "pure" C++ for everything that was not GUI and have it compile with as few platform dependencies as possible on all three targets...lots of STL. I also assumed that the only part of the GUI that would be portable was the functional design. I think that by acknowledging that up front, I saved myself a lot of pain during GUI implementation.

To link the pieces together, my C++ code acted as a library that could be called by any interface (including a console one that I wrote for testing). I also defined abstract classes for my C++ library that defined a "virtual" GUI...call-back functions that the core code needed for display purposes. Those classes then had their implementations provided by the real, platform-specific interfaces...either directly on Windows and Linux, or by thin C++ objects within Cocoa/Objective C++ classes.

........................
Phillip Mills
Multi-platform software development
(416) 224-0714
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Cocoa/Windows parallel dvlpmt
      • From: Phillip Mills <email@hidden>
    • Re: Cocoa/Windows parallel dvlpmt
      • From: Andy Satori <email@hidden>
References: 
 >Re: Cocoa/Windows parallel dvlpmt (From: Phillip Mills <email@hidden>)

  • Prev by Date: Re: Cocoa/Windows parallel dvlpmt
  • Next by Date: NSHomeDirectory() leak?
  • Previous by thread: Re: Cocoa/Windows parallel dvlpmt
  • Next by thread: Re: Cocoa/Windows parallel dvlpmt
  • Index(es):
    • Date
    • Thread