[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

Subject: Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
From: "R. Scott Thompson" <email@hidden>
Date: Thu, 30 Sep 2004 13:26:01 -0500
Delivered-to: email@hidden
Delivered-to: email@hidden

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.

--
Macintosh Software Engineering Consulting Services
Visit my resume at <http://homepage.mac.com/easco/RSTResume.html>

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden

This email sent to email@hidden

Follow-Ups:
- Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
  - From: m <email@hidden>

References:
	>Cocoa Application Architecture - Think More About AppleEvents and OSA? (From: Simon Liu <email@hidden>)
	>Re: Cocoa Application Architecture - Think More About AppleEvents and OSA? (From: Dustin Voss <email@hidden>)

Prev by Date: Re: linking to private frameworks
Next by Date: Crash in NSImage -lockFocus
Previous by thread: Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
Next by thread: Re: Cocoa Application Architecture - Think More About AppleEvents and OSA?
Index(es):
- Date
- Thread

Home