Developers guide

40
5.2 Architecture
The user interface has been isolated as much as possible from the JAS to ease its portability to
future versions of the JAS, or even other distributed control systems. Although many components
reference JAS interfaces and objects, most JAS routines are found in the JASComms class.
The diagram below shows the flow of data throughout the system.
JASComms
APTServer
Telemetry
Channels
Status Gui
Components
Bound Component Managers
Status Gui
Components
Status Gui
Components
Command Sender
Command
Channels
Control Gui
Components
Control Gui
Components
Cmd
Figure 5-2 Client GUI architecture
5.3 Process manager
This panel is a graphical representation of the JAS ProcessListener interface, displaying JAS
ProcessEvents as they arrive from a ClientProcessSpace. Each process is assigned a row in
the table displaying its status information, as shown in Figure 5-3.
Currently, only the privileged process space is used. System and general commands may also
be running within the JAS system in their respective process spaces.
Unfortunately this panel will only ever be able to show status information for commands sent by
the user whilst they have control. This is a limitation of the JAS architecture. It would be more
convenient to be able to show information on all commands running in the system at any one