This project comprises two distinguish models which one uses some basic concept of the other. The two models are:
Part 1:Time Record Modelling
Part 1: Definitive scripts are used here to represent relationship between an event or a file and a range of time that it happens. When users move or resize a line in a Record time scale, a range of time in an event or a file will change. In this model, definitive scripts also represent a state or mode of interaction e.g. new, delete, move, information, resize etc.
In other view, each button might be regarded as an agent which are connected to others in somehow. When users click on each agent, it can be regards to activate this agent to perform its task. For example, when users click on NEW button, this signals New agent to be active and to wait for users clicking on the Record time scale. After users click on the Record time scale and a colorful line appears on it, this agent becomes passive again.
Part 1: In this part, Yvonne illustrates very smart use of definitive scripts to capture relationships between a line on Record time scale and actual calculated time, an event or a file and a Record time scale. She uses DoNaLD to present a line on each Record time scale and SCOUT to represent all buttons, Record time scale and information box. In the model, there are 22 SCOUT windows in total to represent every things: buttons, Record time scale and so on. The contents of Info box changes according to the current click of an event or a file in the Record time scale.
Part 2: Interface Creation Modelling
Part 2: The use of definitive scripts in this part is very similar to previous part. Since this part can be viewed as an extension of part 1. Again definitive scripts are used here to define a state of the model as shown in Fig 2.1 and Fig 2.2. Fig 2.2 explains hidden scripts used for each text box. This includes the display of current values of some scripts. Each text box and pict box is movable at run-time.
Part2: In this part, Yvonne shows how to manipulate a series of SCOUT windows in this case it is restricted to 8 windows. Each window is defined in the same format i.e. w1, w2, w3 and so on. This includes its property such as position i.e. w1pos, w2pos, w3pos and so on or another example its string content i.e. w1str, w2str, w3str and so on. After defining these windows systematically, it is easier to control and manipulate each window. A common procedure like move(); fixtext(); and some others can be viewed as a sub-routine procedure.
NOTE: Bug!!! I found that when I tried to delete a pict window from the space, the window did not seem to be removed!!!
[YVO97] Yvonne L. Generic Application Modelling in Eden(GAME). Finalyear project 96-97. Department of Computer Science, University of Warwick, 97.