| |
| META TOPICPARENT |
name="APPXRuntimeSubroutineAPI" |
.CLIENT LOAD URL |
| | <url> is the URL or document to open, or the command to run on the user's PC. It can take several forms:
|
|
<
< |
- The name of a file accessible to the user's PC. In this case, the client will rely on the desktop O/S to determine the correct program to use. For Macintosh clients, you will need to set the client desktop preference for commandShell to the program 'open'. For Linux clients, you also need to set commandShell to some program that will examine the file type & call the appropriate program to open it.
|
>
> |
- The name of a file accessible to the user's PC. In this case, the client will rely on the desktop O/S to determine the correct program to use. For Macintosh clients, you will need to set the client desktop preference for commandShell to the program 'open'. For Linux clients, you also need to set commandShell to some program that will examine the file type & call the appropriate program to open it. Note that different desktop O/S'es handle embedded blanks differently. If your file name includes blanks, for most Windows desktops you should enclose the name in quotes, but for most Mac desktops you should NOT enclose it in quotes. Some experimentation may be required.
|
| |
- A program on the user's PC. For Windows and Linux desktops, prefix the program name with an '@', ie, @notepad
 or @gedit. You can pass additional arguments after the program name, ie, @notepad somefile.txt. For Macintosh clients, just pass the complete path to the program, ie, /Applications/Chess.app. Remember that file and program names on Linux and Macintosh desktops are case sensitive.
- A network path, such as \\<server_name\<share_name> for Windows desktops, or smb:////<server_name/<share_name> for Linux or Macintosh desktops.
- The constant '$beep:'. This will make the client play a 'beep' sound.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.