|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
|I have a question about best practices to extend the document class using an sdef. My app has a custom document class that adds some properties and elements, as well as a contents element to the standard suite definition.|
Let me stress this is a question about *practice*, not about /theory/. I do know the theory, but practice ≠ theory in the world of AppleScript, unfortunately.
I have two Suites: NSCoreSuite and my app suite. Normally, the standard document class is defined in NSCoreSuite. Where should my custom document stuff go? I see4 possibilities:
1. standard document in NSCoreSuite, and a class-extension with the extra stuff in my app suite
2. standard document in NSCoreSuite, and custom stuff in another document class in my app suite
3. add the custom stuff to the document class element in NSCoreSuite
4. no standard document class, and everything in a class element in my app suite
As I said, I know the theoretical answer, which is 1. However this does not work in (Snow) Leopard (which I want to support, and Lion is academic), because in practice AppleScript (or is it Cocoa Scripting?) does not recognize a <contents> element in a class-extension.
I also remember from the ancient past that 2 does not work, because there is no working way to indicate inheritance of the conflicting class definitions.
That leaves me with the last two. So which one is the preferred one?
_______________________________________________ Do not post admin requests to the list. They will be ignored. Applescript-implementors mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.