Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?

FROM : m
DATE : Thu Sep 30 21:20:46 2004

On Sep 30, 2004, at 11:26 AM, R. Scott Thompson wrote:

>>> 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.

>>
>> Yeah, this is a good way to handle things.

>
> Just to add a "me too", I tend to think of the scripting layer as
> another controller that attaches to the same model.  The "views" in
> this case are whomever may receive the results from handling a
> particular script command.


Don't know if it's been mentioned as an advantage yet, but doesn't
using AppleEvents internally as a layer between your Model and your
Views/Controllers make recordability of AppleEvents a no brainer?

I've been away from AppleEvents since back in the Mac OS9 days, so
forgive me if there are issues with recordability in Mac OS X. I did
notice that the Finder is not nearly as recordable as it was in Mac OS
9.

_murat