• 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: itunes for windows HOWTO ???
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: itunes for windows HOWTO ???


  • Subject: Re: itunes for windows HOWTO ???
  • From: Troy Dawson <email@hidden>
  • Date: Mon, 10 Nov 2003 05:43:35 -0800

On Nov 10, 2003, at 4:55 AM, patrick timur wrote:

I have invested time in Cocoa development and really
like what I have seen so far. I am at a point where I
need to port a GUI based app to Windows. I would
rather not go down the Java or native route if a
better option was presented. A better option for my
situation would be a Cocoa development environment for
MS Windows. Should I just consider this as being a
somewhat far fetched dream?

anybody who knows ain't sayin', though this Cocoa on WinNT is long-known as the "Yellow Box".

I am interested to know
what method was used to port itunes over to MS
Windows?

from publically-available intrusive debugging tools, the following is known:

1) iTunes links to Winsock2, and basic Win32 dll's.
2) the UI is a single window, not the multitude of child controls (child windows) most Win32/MFC programs set up.

If I were looking at a cross-platform port, I would look to build the app with less hard coding and more soft scripting...
kind of what XAML for Longhorn is supposed to be. Doing it this way means your scripting engine can pass-thru into Cocoa wrappers on the Mac side, and on Windows you just need to reimplement the end actions of the scripting engine, either natively or like how iTunes did it (some sort of custom UI widget layer).

eg. instead of an explicit [[NSWindow alloc] initWithFrame: blah blah] hard-coded you'll have a UI definition file:

<? uidef file>
< window frame: blah blah> </window>

or whatever. Both the Mac and Windows apps then become identical script engines (one in Objective-C/Objective-C++, the other in C/C++/C#) and not code monsters.

The more pass-thru-into-Cocoa stuff you can eliminate (by creating a platform-neutral UI graphics engine etc) the easier the Win32 port will turn out to be.
_______________________________________________
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: itunes for windows HOWTO ???
      • From: Michael Rothwell <email@hidden>
References: 
 >itunes for windows HOWTO ??? (From: patrick timur <email@hidden>)

  • Prev by Date: Re: itunes for windows HOWTO ???
  • Next by Date: Re: itunes for windows HOWTO ???
  • Previous by thread: Re: itunes for windows HOWTO ???
  • Next by thread: Re: itunes for windows HOWTO ???
  • Index(es):
    • Date
    • Thread