Final Thoughts
This chapter has taken you through a journey of exploration—exploring classes, methods, instances, and script suites. Here are just a few thoughts to take away with you:
- Use the standard core suite.
There is absolutely no reason I can think of why you shouldn’t use the standard AppleScript core suite with any application—whether it’s initially scriptable or not.
- Demand only the best!
Building scriptSuite and scriptTerminology files is usually done as an afterthought—by exhausted programmers who would rather be doing something else. Don’t let programmer apathy or fatigue stand between you and what you want to script. If a programmer left out a key attribute or command, get on their case. Send email and demand better AppleScript integration. Of course, after reading this chapter, you can always add missing AppleScript bits by yourself.
- Look beyond the core.
As you’ve seen, scriptSuite and scriptTerminology files create bridges between applications and scripting. Given the excellent documentation of Apple’s Cocoa API, you really should be able to expand the core suite to include a lot more classes. This is left, of course, as an exercise for further exploration.
Get Modding Mac OS X now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
