31
edits
Mac:AppleScript: Difference between revisions
Jump to navigation
Jump to search
→Current Plan
m (→Current Plan) |
|||
| Line 17: | Line 17: | ||
The bug for improved AppleScript support in Gecko is {{bug|61356}}. | The bug for improved AppleScript support in Gecko is {{bug|61356}}. | ||
The bug for improved Applescript support in Firefox is {{bug|61356}}. | |||
Other bugs for Applescript in include: {{nbug|125419}}, {{nbug|156078}} (Camino), {{nbug|237733}}. | Other bugs for Applescript in include: {{nbug|125419}}, {{nbug|156078}} (Camino), {{nbug|237733}}. | ||
| Line 24: | Line 25: | ||
e.g. if Firefox Sync would like to have an Applescript command "tell application "Firefox" to sync", it could register with the Applescript service to forward all "sync" Applescript requests to their Javascript code. | e.g. if Firefox Sync would like to have an Applescript command "tell application "Firefox" to sync", it could register with the Applescript service to forward all "sync" Applescript requests to their Javascript code. | ||
''' | The current plan is to create a solution tailored for Firefox, which could be replaced by a more generic solution (once one is found). | ||
'''Generic Solution Proposals''' | |||
*Proxy objects: similar to Tom Dyas' work in {{bug|516502}}, have an application create their own set of proxy Obj-C classes to respond to Applescript. | *Proxy objects: similar to Tom Dyas' work in {{bug|516502}}, have an application create their own set of proxy Obj-C classes to respond to Applescript. | ||
| Line 39: | Line 42: | ||
'''Scripting Hierarchy''' | '''Scripting Hierarchy''' | ||
Firefox | Firefox | ||
*application | *application | ||
**windows | **windows | ||
***tabs | ***tabs | ||
****index | ****index | ||
| Line 56: | Line 52: | ||
****source | ****source | ||
****doJavascript? | ****doJavascript? | ||