• 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: Where are the boundaries of Cocoa and how are the boundaries perceived ?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where are the boundaries of Cocoa and how are the boundaries perceived ?


  • Subject: Re: Where are the boundaries of Cocoa and how are the boundaries perceived ?
  • From: Bill Cheeseman <email@hidden>
  • Date: Mon, 01 Oct 2007 18:13:33 -0600
  • Thread-topic: Where are the boundaries of Cocoa and how are the boundaries perceived ?

on 2007-10-01 4:47 PM, John Stiles at email@hidden wrote:

> If it's an SPI, does it need classification? Developers aren't
> supposed to use undocumented functions in the system since they could
> change at any time and then your app will break.

The OSAKit.framework headers are located in /System/Library/Frameworks. As I
understand the way things work, that means it's public API and we're free to
use it. Nothing in the headers suggests otherwise.

If that isn't enough, there is an OSAPalette,palette file for Interface
Builder located in /Developer/Extras/Palettes which you can add to your IB
palette. It includes two views and two objects for OSAKit.framework.

When I refer to OSAKit.framework as "undocumented," I mean that Apple hasn't
published the formal developer documentation we are used to seeing for most
AppKit and Foundation frameworks. Fortunately, the NSAppleScript
documentation applies to those OSAKit methods that have the same names, and
almost all of the OSAKit methods that don't have NSAppleScript analogs are
named according to standard Cocoa AppKit conventions and should be very easy
to figure out.

In fact, OSAScriptView and OSAScriptController and their methods so closely
conform to AppKit conventions (complete with IBAction methods and IBOutlet
instance variables) that they make it virtually impossible not to count them
as part of "Cocoa" in spirit and intent even though they aren't included in
the Cocoa frameworks.

--

Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
www.quecheesoftware.com

PreFab Software - www.prefabsoftware.com


_______________________________________________

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

  • Follow-Ups:
    • Re: Where are the boundaries of Cocoa and how are the boundaries perceived ?
      • From: Scott Anguish <email@hidden>
References: 
 >Re: Where are the boundaries of Cocoa and how are the boundaries perceived ? (From: John Stiles <email@hidden>)

  • Prev by Date: Fw: Problems with authorization (error -60002, errAuthorizationInvalidRef)
  • Next by Date: Re: Popup vs pull down menu item missing
  • Previous by thread: Re: Where are the boundaries of Cocoa and how are the boundaries perceived ?
  • Next by thread: Re: Where are the boundaries of Cocoa and how are the boundaries perceived ?
  • Index(es):
    • Date
    • Thread