Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
- Subject: Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
- From: Ringo De Smet <email@hidden>
- Date: Thu, 30 Sep 2004 13:23:56 +0200
Simon,
On Thu, 30 Sep 2004 10:13:27 +0100, Simon Liu <email@hidden> wrote:
> "A deeper use of the OSA is to "factor" the user interface elements of
> the application from its core functionality. The user interface
> elements do not directly call the subroutines that do the work of the
> application. Rather they send AppleEvents back to the application,
> which receives these events, and then dispatches them to the
> appropriate internal routines."
Although not on the Mac, I (and the rest of the team I worked in) once
had the task of making a Java Swing application scriptable. Our
application was already very MVC. There was a minor set of MVC
violations we had to break, then we checked if the model that was
exposed was abstract and stable enough as a public API. We ended up
putting some things behind a facade with the view and controller
layers going through this facade. In the end, the scripting engine was
just a second user of the model, next to the UI. Personally, I would
do the same for an AppleScriptable application.
Ringo
_______________________________________________
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