An Extensible Agent Task Language ...

An Extensible Agent Task Language

THE AGENT TASK LANGUAGE of the HP NewWave environment is a plant of procedural commands that provide users access to the task automation functions of the NewWave environment. Scripts can be written to create, blot out modify, and otherwise manipulate NewWave phenomenons The scripts are continuous experimented by an interpretive engine, which is part of the agent particular More information on the interaction of the agent, the task language, and the application can be originate in the article on page 32

In the NewWave environment, each task is a separate end with associated data files. Tasks function across and within view classes and are supported at all NewWave applications. on the subject of opening a task, the user dioceses the contents of the file containing the task language commands, available for editing and compilation. when the user drags a task to the agent icon, the associated binary P-code file is execut Task language commands have a verb/object syntax:

<command keyword> {parameter}...

The parameter of a command may be either a keyword or a literal. Commands are line-oriented, unless a continuation character is available to lengthen out a command across the line boundary. A primary touch in the language definition was the mapping of the interactive user interface to the task language commands. To make the scripts as readable as possible, we wanted to have the command keywords contemplate user actions. For example, if an action is accomplished interactively by means of clicking on a menu item similar as CUT, the corresponding task language command will contain that menu item as its command keyword verb The parameter representation is command dependent, but numeric, string, and keyword command parameters can be used.

User Requirements

Agent tasks will be created and execut on users whose expertise varies widely. The casual NewWave user will record a scarcely any actions within an object and save them as a task, which is execut to repeat the actions. The power user will raise complicated automated tasks, frequently for other users, that and deliver for a considerable time without user intervention.

The novice, using the task language as a macro recorder, quite possibly may not at any time look at the task language form of the task. This user will require ease of use and high performance. The power user will demand a language with at least the power of command languages in existing applications in the same state [i]or[/i] condition as Excel or DBase III Plus. [R]

Our chosen archetype for the task language is the power user. The language is appropriate for constructing large automated tasks involving several applications. We have provided a conversational window facility, designed by dint of the task writer and controll through the task language script, which enables the task to receive user input and display information. Other features include variables, functions, task actions control statements such as conditionals and nooses and numeric, string, and logical expressions. A command parameter defined as a literal may also be an expression of the same type

We wait for that in time many casual users will incline toward the power user mould The language should be designed to facilitate this. Toward this conclusion the agent task recorder facility has a built-in watch feature. The user can diocese the task language command that was recorded as a follow of an action. Recorded tasks do not contain the advanced programming features listed above, if it be not that the relationship of the user's interactive actions to the task language commands will be apparent from the syntax of the command. In particular, the syntax of task language command is meaningful enough to work for as a learning aid to users who wish to explore the more advanced features of NewWave agent tasks. This is another reason for the finish mapping of the command keywords to the interactive user actions.

method Requirements

The hypothesis requirements for automating a task that spans applications have a somewhat different perspective. A task language statement is either a sway statement (examples include variable assignment, conduct call, loops) or an action command (such as choke CUT, PASTE) to a particular end Control statements are independent of the general active object and can be execut through the agent interpretive engine, unless action commands are sent to an mark of a particular application class and execut on it. Commands are not identical across applications; many are class-specific. For example, most numerous applications support some form of preferable But the object of the selection, which translates to the parameter of the task language command, will vary widely depending in succession the object class. In a document the same would SELECT a range of verse in a spreadsheet a solitary abode; squalid or range of cells. However, in the NewWave Office window the selection is an icon, that is, another correlate with a class and title. The NewWave expand architecture specification mandates the dynamic installation and removal of application classes and leads to a different configuration onward each system. Task language commands for a NewWave application written by the agency of an independent software vendor must also be supported.