Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!chewy@apple.com
From: chewy@apple.com (Paul Snively)
Newsgroups: comp.sys.mac.system
Subject: Re: System 7.0 era
Message-ID: <13414@goofy.Apple.COM>
Date: 9 May 91 01:16:22 GMT
References: <1991May6.143117.18679@magnus.acs.ohio-state.edu>
Sender: usenet@Apple.COM
Organization: Apple Computer, Inc.
Lines: 32

In article <1991May6.143117.18679@magnus.acs.ohio-state.edu>
bgrubb@magnus.acs.ohio-state.edu writes:
>The only problem I do see in the new type of programs that will be
>written for the mac is that since Apple did not standerdized how to
>IAC(aagh!) there could be major problems with software from different
>companies trying to communicate with each other.

Pardon me?

Maybe I missed something, but as one of the people at Apple who has
been working for over a year on AppleEvents, precisely in an attempt
to help formulate a set of standard AppleEvents and data types, I can
gleefully say that we very definitely _did_ standardize not only a
means of communication (the AppleEvent protocol) but some sets of
"verbs" (Required and Core AppleEvents) as well as some standard data
types.

To make matters even better, there is an Object Model that AppleEvents-aware
software should use to allow access to its data structures by AppleEvents. 
There's even a code library to support this Object Model.  It's available
(albeit in beta form) on AppleLink.

The bottom line is that we've worked _very hard_ to make it possible for a wide
variety of software to "all speak the same language" as they talk to each
other.

More details will, of course, be forthcoming at the Developers' Conference next
week!

Paul Snively
MacDTS
Apple Computer, Inc.