Difference between revisions of "Mac OS X Porting - AppleScript Support"
m (→Extending Support) |
m (→Basic Support) |
||
| Line 11: | Line 11: | ||
2. Create a "sdef" scripting definitions file and put it in the bundle | 2. Create a "sdef" scripting definitions file and put it in the bundle | ||
<br> | <br> | ||
| − | 3. Design scriptable "helper" classes that implement the object hierarchy | + | 3. Design scriptable "helper" classes that implement the object hierarchy. [http://developer.apple.com/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/SApps_design_apps/chapter_3_section_3.html] |
| − | + | ||
== Extending Support == | == Extending Support == | ||
Revision as of 01:21, 19 June 2008
Feature Justification
AppleScript support is basic to a Mac OS X application. Supporting Applescript will have the additional benefit of allowing scripting using JavaScript, Ruby, Python, and Objective-C via the AppleScript Scripting Bridge [1]
Basic Support
In order to add Applescript support to OOo the following basic steps need to be accomplished.
1. Turn on scripting support - see Apple Documentation http://developer.apple.com/documentation/Cocoa/Conceptual/ScriptableCocoaApplications/SApps_implement/chapter_4_section_7.html#//apple_ref/doc/uid/20000037-1081046]
2. Create a "sdef" scripting definitions file and put it in the bundle
3. Design scriptable "helper" classes that implement the object hierarchy. [2]
Extending Support
Phase 1 - Define suites (object model) for OOo
Phase 2 - Implement a subset of the most useful objects
Phase 3 - Verify support for Standard and Text Suites
Phase 4 - Make the OOo uno model AppleScript-able
--Msicotte 20:41, 12 June 2008 (CEST)
