Difference between revisions of "Mac OS X Porting - AppleScript Support"
(→Extending Support) |
m (→Extending Support) |
||
Line 15: | Line 15: | ||
== Extending Support == | == Extending Support == | ||
− | Phase 1 - Define suites (object model) for | + | Phase 1 - Define suites (object model) for OOo<br> |
Phase 2 - Implement a subset of the most useful objects<br> | Phase 2 - Implement a subset of the most useful objects<br> | ||
Phase 3 - Verify support for Standard and Text Suites<br> | Phase 3 - Verify support for Standard and Text Suites<br> |
Revision as of 01:20, 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 for the Standard and Text AppleScript suites. [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)