• 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 friendly Quicktime APIs?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa friendly Quicktime APIs?


  • Subject: Re: Cocoa friendly Quicktime APIs?
  • From: Ryan McGann <email@hidden>
  • Date: Fri, 7 Mar 2003 21:44:02 -0800

QT is a cross platform API (Mac and Windows)... Cocoa-izing it would have
serious implications for the Windows side, wouldn't you say? That's
probably a factor.

Sean,
I do not agree with you on this issue. The functions I am referring to all
contain Mac Carbon specific issues that would have to be different from
Windows no matter what. FSSpec is a Mac specific structure to describe file
location. Update events is a Mac specific method to refresh the screen. You
see the pattern? I do not think that Quicktime should be rewritten as
Objective-C, keeping it as C calls would be fine. We just need Cocoa flavored
calls (mostly dealing with User Interface and File management) for both
Carbon & Cocoa, instead of having it for Carbon only.
Actually, Apple ported many of the Mac-specific data structures you speak of to Windows for QuickTime.....FSSpecs, GrafPorts, etc. Many people actually rumored that QuickTime's port to Windows was Apple's attempt at porting the Mac OS to run on the x86 architecture.

But on the issue of Cocoa QuickTime APIs, there's NSMovieView. On top of that, use the QuickTime C APIs. People always seem to deem any non-Objective-C framework as being Carbon. Not so. And people are always asking Apple to write Cocoa (Objective C or otherwise) wrappers for every new framework they introduce. I'd _much_ rather see the Cocoa Frameworks team at Apple fix outstanding bugs and implement new features rather than spend their time writing wrappers around already compatible functions.

QuickTime, over time, will include more FSRef and CF-based functions, with perhaps some CoreGraphics functionality tied in. But I wouldn't expect anytime soon that Apple will start providing functions in the QuickTime framework that take NSURL's and display NSSavePanels. Especially now that Apple has implemented the Carbon-from-Cocoa compatibility in OS X for Jaguar.

Ryan
_______________________________________________
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 friendly Quicktime APIs?
      • From: publiclook <email@hidden>
    • Re: Cocoa friendly Quicktime APIs?
      • From: Oleg Svirgstin <email@hidden>
  • Prev by Date: Pref panes and NSDocuments
  • Next by Date: Font Panel usage question
  • Previous by thread: Re: Cocoa friendly Quicktime APIs?
  • Next by thread: Re: Cocoa friendly Quicktime APIs?
  • Index(es):
    • Date
    • Thread