This
document describes the AOBE Applicative Transitions technology and framework
and its use to implement the Data base support in AOBE for PocketPC.
The
Applicative Transitions Model is the heart of the solution :
- “call://function” URLs start the transition. All
args and formdata inputs are collected into a list of named arguments and
passed to an internal function.
- If the “qry” arg is
present, the DBQueryProcessor is called. It replaces variables ($name$) by
values, performs the request and returns a recordset.
-
if the “tpl” arg
is present, an HtmlPageMaker object is initialized with the template file.
Its methods are called to generate the output HTML page. Each record from
the recordset is translated to a StringList before processing.
Here is how
the List Selector looks like :
It is
called from a link such as :
<a href="call://DisplayList@ qry=SelLst.qry&tpl=SelLst.tpl ">Mes listes</a>
Here is the
HTML code of this page :
<html><body><font face="verdana">
<font size="3"><p align="center"><b>Select Active List</b></p></font>
<hr width="75%">
<form method="POST" action="call://SetActLst?qry=ActLst.qry&tpl=ActLst.tpl">
<input type="radio" name="LSTNAM" value="Liste 1">Liste 1<br>
<input type="radio" name="LSTNAM" value="Liste 2">Liste 2<br>
<input type="radio" name="LSTNAM" value="Liste 3">Liste 3<br>
<center><input type="submit" name="BTN_ACT" value="Select">
</center>
</form>
<hr width="75%">
<a href="CIDHP.html"><font face="Verdana" size="1">Home</font></a>
</font></body></html>
When the
Select button is clicked -let's assume that the second radio button is checked-
this generates the following named arguments list:
|
Tpl
|
qry
|
LSTNAM
|
BTN_ACT
|
|
ActLst.tpl
|
ActLst.qry
|
Liste 2
|
Select
|
Then the
ActLst.qry DB query script file is loaded :
SELECT
Items.REF, Items.NAM
FROM
(ListItems RIGHT JOIN Lists ON ListItems.LSTnum=Lists.num)
LEFT JOIN Items ON
ListItems.ITMnum=Items.num
WHERE Lists.NAM='$LSTNAM$';
In this
situation, $LSTNAM$ is replaced by
"Liste 2" and the query will select its contents. The result is
a record set where each record has 2 components : the item's reference and the
item's name.
The final
page is generated using the following template :
<!--header-->
