Thanks Erik
Having the model doing the drawing directly like that is something I hadn't
thought of. Definitely worth considering. I'll still have to observe changes in
related attributes to trigger UI updates, and I have many ancillary objects
that need to be involved in the process, so I may
Thanks Fritz - I had a look at the Sketch example, and see how it implements the
AppleScript. I see also that it uses the concept of a single canvas that has objects that
can draw on it. I think I'll have to do some testing with the other scenarios to see how
performance would go using views or
You have too many design options on the table. Try some of them in
mini-prototypes to see how well they work and then drop some of the ideas.
I have used Core Data to store Model data for 2D and 3D drawing/visualization
applications. My approach was to use the Core Data designer to specify cu
On 16 Aug 2010, at 8:18 PM, Kenneth Baxter wrote:
> If I was exposing all this to AppleScript, would I be able to leverage my
> view controllers etc, or would I have to use a different architecture?
I believe Apple's sample code for "Sketch-112" will put you a long way into
your quest. Search f
Hi, I am working on an application that uses core data at the back end, and the
NSPersistentDocument architecture at the front end. It is a graphics
application which essentially displays a tree of objects, destined for 105+
deployment. I also want the functionality available by AppleScript. I
