Difference between revisions of "Development:Camino AppleScript Guide"

From Camino Wiki
Jump to navigation Jump to search
Line 25: Line 25:
 
*:  
 
*:  
 
*: If a user has “Links opened by other applications” checked (in the Tabs preference pane), it is possible to use <code>open location "about:blank"</code> to fake opening a new tab and then use <code>set URL of current tab of front browser window</code> to load the desired URL.
 
*: If a user has “Links opened by other applications” checked (in the Tabs preference pane), it is possible to use <code>open location "about:blank"</code> to fake opening a new tab and then use <code>set URL of current tab of front browser window</code> to load the desired URL.
* Certain items present in the Standard Suite will compile but are not implemented in Camino at this time.
+
* Certain items present in the Standard Suite will compile but are not implemented in Camino at this time ({{bug|394581}}).
 +
* <code>browser window 0</code> resolves to a browser window (browser window 1) but should not ({{Bug|395716}}).
 +
* It is currently not possible to close a tab via AppleScript ({{Bug|391683}}).
 +
<!-- {{Bug|391684}} – AppleScript: Closing browser window w/ multiple tabs prompts user
 +
probably belongs somewhere, but where? -->
  
 
==Migrating Scripts from Camino 1.5 to Camino 1.6==
 
==Migrating Scripts from Camino 1.5 to Camino 1.6==

Revision as of 00:31, 11 December 2007

DRAFT
This page is not complete.

The following page is a guide to the AppleScript features available in Camino 1.6.

Camino 1.6 features significant improvements in AppleScript support over previous versions of Camino. Some of these improvements required incompatible changes to commands and properties. Many scripts will continue to work correctly in Camino 1.6; however, scripts that use certain commands and properties, and text scripts (.applescript), will need changes in order to continue functioning.

New in Camino 1.6

  • Browser Windows and Tabs
    • Browser windows can now be referenced specifically. Previously, Camino only exposed windows in general, including the Preferences window and the Downloads window in the same collection as browser windows.
    • Browser windows contain tabs.
    • Tabs can be addressed individually, exposing the title and URL of each page the user has open.
  • Bookmarks
    • Bookmarks and bookmark folders can be read, added, and modified by AppleScripts. (But see the important note below.)

Anomalies in the Camino AppleScript Dictionary

  • Moving bookmarks and bookmark folders
    While code like
    tell application "Camino"
    move bookmark "Test" of bookmark bar collection to ¬
    bookmark folder "Test ƒ" of bookmark bar collection
    end tell
    will compile, it will produce undesired dataloss as a result.

    To move a bookmark into a folder, use the following syntax instead:
    tell application "Camino"
    move bookmark "Test" of bookmark bar collection to ¬
    end of bookmark items of bookmark folder "Test ƒ" of bookmark bar collection
    end tell
    See Bug 394821 for more information.
  • Making new tabs or browser windows
    Although the make command is present, it is currently not possible to make new tab or make new browser window. For technical information about the reasons for this, see this blog post.
     
    If a user has “Links opened by other applications” checked (in the Tabs preference pane), it is possible to use open location "about:blank" to fake opening a new tab and then use set URL of current tab of front browser window to load the desired URL.
  • Certain items present in the Standard Suite will compile but are not implemented in Camino at this time (Bug 394581).
  • browser window 0 resolves to a browser window (browser window 1) but should not (Bug 395716).
  • It is currently not possible to close a tab via AppleScript (Bug 391683).

Migrating Scripts from Camino 1.5 to Camino 1.6

  • The open URL and Get URL commands have been replaced by open location. Compiled scripts should handle this change automatically in most cases.
  • The window class now properly refers to all open windows (including the Downloads and Preferences windows). To target a browser window, use browser window instead.

Implementing Toolbar Script Items