Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AppleScript-Cocoa Impedance Mismatch

On Nov 1, 2007, at 3:13 PM, Jim Correia wrote:
In the terminology if you have a media object, and a book object, the user should be able to access them specifically or generically (I realize this is the other question you asked) and as long as the objects specify them selves, use the class operator to determine what kind they are. In that case, having a type property of media which returns an enumerated value "book" is not necessary; and isn't the norm for how things work.

You're totally right, of course. Now that you have me thinking in AppleScript, I realize that the solution to the class versus type problem is to eliminate the type and not the class. That only leaves one problem: what's best practices for converting between AppleScript's model (type as class) and the actual implementation (type as property).

(OK, obviously the best thing would be to go type as class in the implementation, but at this point that is not an option.)

Cheers,
Mike Lee, Major-domo
Delicious Monster Software, LLC

 



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-implementors mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-implementors/email@hidden

This email sent to email@hidden
References: 
 >Re: AppleScript-Cocoa Impedance Mismatch (From: Major Domo <email@hidden>)
 >Re: AppleScript-Cocoa Impedance Mismatch (From: Jim Correia <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.