Re: COM on mac
Re: COM on mac
- Subject: Re: COM on mac
- From: Andy Satori <email@hidden>
- Date: Mon, 13 Jan 2003 13:20:34 -0500
As a fellow Windows dev, that is/has transitioned to the Mac as my primary
machine, even though I continue to target primarily Windows at a work, I
think the best way to get a grip on this in the Mac world is to spend some
time with AppleScript and it's Dictionaries of other applictations. I'm
still not clear on the method of communication, (unlike Windows and COM
which is really a bunch of well hidden DDE conversations, cringe), it
appears that everything rides on the Apple Events foundation for the same
kind of interprocess communications. AppleScript just happens to be the
easiest way to get a handle on it, much like VB is a way to get familiar
with the COM interface before trying to implement them in C++, which is
still brutal.
I'm sure that someone can provide a real world example, but the principle
appears very similar, but without the ability to import a Type Library that
exposes and entire object hierarchy of functionality ala Word. At the same
time, you can achieve much of the same functionality via AppleScript. I
personally am pushing Entourage harder this way than I did Outlook via
JavaScript and the Windows Scripting Host and the COM interfaces.
That said, if someone else can provide a pointer to a real world example of
automating an external application from Cocoa, I'd like to see it as well
:-).
Andy Satori
On 1/13/03 12:49 PM, "Gil Dror" <email@hidden> pounded the keyboard to
produce:
>
This is the first time I post in this mailing list, although, I have
>
been reading it for a while now.
>
>
I am a Windows developer who loves Mac's and is trying to start
>
programming for it using cocoa, I'm am trying to understand some
>
fundamental issues regarding Mac programming but with not much success.
>
One the more important issues is how to interact with other modules in
>
OS X. For-instance: in a Windows world, If I wanted to use some
>
functionality from Microsoft Word, then I would just create an instance
>
of Word and then use any of the exposed objects in the Word Interface.
>
The great thing is that I don't need to know where Word is on the
>
computer, it just has to be Installed and COM makes sure I get the
>
right one.
>
I am wondering what technique is equivalent to COM in mac. I have
>
looked through Apple's guides but it doesn't seem to talk about this
>
aspect of Mac programming, maybe the solution is very obvious to a mac
>
user but I can't seem to get the way programs interact with each other
>
in OS X.
>
>
okay, so I guess my questions boil down to this:
>
1. How do I expose a class for outside programs to access ? and then
>
how do I access the class from that program ?
>
2. I know that using DLL's is not a common practice for the Mac but
>
does that mean you have all the functionality in the Executable itself ?
>
>
Thanks,
>
Gil
>
_______________________________________________
>
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.
_______________________________________________
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.
| References: | |
| | >COM on mac (From: Gil Dror <email@hidden>) |