Screen design and user interface

Before we delve into the details of how a Pascal program can be modified to make it controllable from a WWW client, let us look into what kind of control panel we can present the user with. All the components of the panel have to conform to the HTML syntax and be built with elements that can be displayed by a regular viewer that can handle forms. Now, even text-oriented viewers can handle forms reasonably well, e.g. the Lynx viewer. One can therefore base a WWW tool on the use of forms without reducing by much the generality of the tool.

One of the things we want the user to be able to do is to select, from the source code of an example program, the variables the contents of which should be displayed, and the instructions on which breakpoints should be set. This is best done with a multiple select widget like:

Select/deselect variables to display and place/remove breakpoints in the code with <Control>/Mouse_Button_1. Use the scrollbar to move in the code.

Using a multiple select widget, where only part of the code is showing, but all of it is available on the client side, has two main advantages:

For long programs, the user can see both the code and other components of the panel, for instance, the display of the contents of variables and maybe even the drawing of a complex data structure.
The user can look at the rest of the code, and even put breakpoints in it, without having to query the server for it. All the code is at hand, without taking all the screen space, thus saving user's time and network bandwidth.

Note: The Mosaic viewer does not take into account leading spaces for the contents of the multiple selection widget, even when the spaces are surrounded with <code> </code>. We therefore had to replace every two spaces with underscores to keep the indentation of the code as much as possible.

Visual representation of simple data types

Since we want to allow the user to redefine the value of any data object that is displayed, we have to use input type widgets. These widgets allow the user to see the values and change them without having to send a query to the server for each of them. Try clicking on them to see how they "behave". (Note: we are still experimenting with these representations, details may therefore change between what is shown here and the final version)

boolean and enumerated types are represented as single select widgets of size 1, like: Done Color
integer, character and string types are represented as text input widgets, like: CmptrVisite Name
set types of reasonably small size are represented as multiple select widgets, like: Palette
Pointer types are generally not represented as such. It is the pointed object that is displayed, preceded by the name of the pointer object and ^, unless the pointer is nil. Example:
Current: nil IntPtr^:

Visual representation of data structures

record types are represented as a sequence of their fields between square brackets, and are preceded by the name of the record object, e.g.:
Courant^:[.v:, .Next^:[.v:, .Next: nil]]
array types can potentially have numerous elements, which are not all necessarily of interest to the user. Display of array types is therefore done in two steps. First, when the user selects an array object, the indices of the array are displayed as a multiple select widget, with no preselected item:
NumDOrdre[] (click on the up and down arrows of the scrollbar)
The user can then select the indices for which the value should be displayed, and gets:
NumDOrdre[] NumDOrdre[1]:, NumDOrdre[2]:, NumDOrdre[3]:, NumDOrdre[4]:, NumDOrdre[5]:, NumDOrdre[6]:

Graphical representation of complex data structures

For complex data structures such as lists, trees or graphs, a bitmap image can be prepared, like:

to allow the user to point directly to an element of the structure that should be displayed.

A typical screen could look like this. (This is a fully functional demonstration. Try it.)

Preparing a program for WWW

This is a section of a local copy of the paper World-Wide algorithm animation by Bertrand Ibrahim.

Site Hosting: Bronco

_ const MaxNbSommets = 10;
_
_ type Lien = ^Sommet;
_ _ _ _Sommet = record
_ _ _ _ _ v: integer; _ {v=numéro du sommet}
_ _ _ _ _ Next: Lien; _ { _par hash-coding}
_ _ _ _ _ end; { Sommet }
_
_ var PremierVoisin:array[1..MaxNbSommets] of Lien;
_ _ _ CmptrVisite : 0..MaxNbSommets; {Nb. sommets déjà visités}
_ _ _ NumDOrdre : array[1..MaxNbSommets] of integer;
_ _ _ Nom : array[1..MaxNbSommets] of char; {noms des sommets}
_ _ _ Pile : array[1..MaxNbSommets] of 1..MaxNbSommets;
_ _ _ SommetDePile : integer;
_ _ _ NbSommets : 0..MaxNbSommets; {nombre de sommets}
_
_ function Visite(IndexSommet:integer) : integer;
_ {retourne le numéro d'ordre du sommet le
_ _plus ancien rencontré dans le cadre du
_ _parcours récursif des successeurs du
_ _sommet dont l'index est passé en param.}
_
_ var Courant: Lien;
_ _ _ Anciennete,LePlusAncien : integer;
_
_ begin { Visite }
_ _ CmptrVisite := CmptrVisite+1;
_ _ NumDOrdre[IndexSommet] := CmptrVisite;
_ _ LePlusAncien := CmptrVisite;
_ _ Pile [SommetDePile] := IndexSommet;
_ _ SommetDePile := SommetDePile+1;
_ _ Courant:= PremierVoisin[IndexSommet];
_
_ _ while Courant <> nil do begin
_
_ _ _ if NumDOrdre[Courant^.v]=0 then begin
_ _ _ _ Anciennete := Visite (Courant^.v);
_ _ _ _ if Anciennete < LePlusAncien then
_ _ _ _ _ LePlusAncien := Anciennete;
_ _ _ _ end { then }
_ _ _ else if NumDOrdre[Courant^.v] < LePlusAncien then
_ _ _ _ LePlusAncien:=NumDOrdre[Courant^.v];
_ _ _ Courant := Courant^.Next;
_ _ _ end; { while }
_
_ _ if LePlusAncien = NumDOrdre[IndexSommet] then begin
_
_ _ _ { on arrive ici s'il n'y a pas eu de
_ _ _ _ changement dans la boucle while, ou
_ _ _ _ si l'on est revenu du traitement
_ _ _ _ récursif des suivants vers le plus
_ _ _ _ ancien }
_
_ _ _ repeat
_ _ _ _ SommetDePile := SommetDePile-1;
_ _ _ _ write (Nom[Pile[SommetDePile]]);
_ _ _ _ NumDOrdre[Pile[SommetDePile]] :=NbSommets+1;
_ _ _ until Pile[SommetDePile]=IndexSommet;
_
_ _ _ writeln;
_ _ _ end; { if }
_
_ _ Visite := LePlusAncien;
_
_ end; { Visite }