Re: Calling methods on other applications?
Re: Calling methods on other applications?
- Subject: Re: Calling methods on other applications?
- From: Olivier Lanctôt <email@hidden>
- Date: Sun, 3 Apr 2005 00:02:55 -0500
You use either fistributed objects or distributed notifications to
communicate with other apps.
Ideally you override a couple of method in the desired app using SIBML
(which is a neater way of dealing with InputManagers)
On Apr 2, 2005 6:49 PM, Finlay Dobbie <email@hidden> wrote:
> On Apr 3, 2005 12:40 AM, Ondra Cada <email@hidden> wrote:
> On 3.4.2005, at 1:19, Finlay Dobbie wrote:
>
> >
> > Actually with *native* applications (read it Cocoa) it *is* possible
> > (and comparatively easy) using a quite supported, though somewhat
> > hackish way. Nevertheless... read on.
>
> Carbon is native. Please stop spreading FUD. Also, it is not supported in
> Cocoa applications. It is an abuse of input managers, which are designed for
> managing input, not for randomly screwing with running applications.
>
> > Alas, a big number of important applications like Office or the Adobe
> > ones are not quite native; instead, they are based on a compatibility
> > layer which very unluckily overgrown its niche (read it Carbon) :(
>
> -1 Troll.
>
> -- Finlay
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Cocoa-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
>
--
Olivier
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden