Tsert::Script (patent
pending)
is the script used by Tsert::ITE.
It was released in 1999 (free
for use, but not to copy
or have work
be derived from it).
t-script
has an extended finite state machine as the signalling system, i.e. it
uses finite state machine constructs to expedite messages from and to
dynamic objects. By using these constructs, we felt no need to
duplicate Java
and
its object-oriented features, as other scripts, such as python,
php
and ruby,
have done.
t-script
allows dynamic objects, such as widgets,
channels,
functions,
and timers,
to inherit properties and methods from other objects, just by assigning
one object to another. These objects can then be augmented by
registering
additional methods and properties to them. They register
additional methods by using signals, and message reception and
transmission as triggers (e.g. onstate,
onsend,
onrecv,
ontimer,
etc.),
see example.
The web version
of our script will be different than the ITE version.
It
will not include the ITE testing
constructs, such as requirement,
purpose,
body,
etc.
There are two types of objects in t-script
:
Dynamic
objects:
- widgets
(to
display dialogs and windows),,
- functions
(to
execute methods),
- timers
(using
fixed and random delays),
- channel
(used to
send and receive messages),
- threads
(to
thread other dynamic objects).
Static Objects:
- var (a
polymorphic object for literal values such as string,
integer, float,
octal, hexa, etc. ),
- vector
(a
polymorphic array object which can contain any other objects),
- list
(a
polymorphic list object which can contain any other objects),
- state
(a reserved variable to trigger state changes, and their associated
registered methods).
The C++
Standard template library will be used for all collections.
The Tsert
Templating Engine
will be integrated into
the channel
object.
The channel will use the functionality of our templating
engine to transmit HTML,
XML,
etc., directly on a registered output port.
We saw no point in re-inventing the wheel by
developing our own
XML-based notation to build a GUI-based application. We decided to opt
instead for the HTML <SCRIPT>...</SCRIPT>
fragment. Our t-script
interpreter will simply read HTML <SCRIPT>...</SCRIPT> fragments.
Our SALT
protocol©® will be added to t-script©®.
A SALT
load is inserted into the HTML SCRIPT
tag consisting
of the signature of the script and its associated salted key;
allowing small tasks to be safely instantiated on your
desktop. The name to be used by our company to describe these
small tasks and applications, is Critter©®;
and our marketing
text will be:
Salted
critters
make good eating; and will not give your system
indigestion.
Back
to Top
