WireLess Mobile V1.x AOBE Applicative Transitions 

 

 

 

 

 

Relative documents :

 

·        WireLess Mobile 1.0 Channel Designer User's Manual

·        WireLess Mobile - Sample Channel Description


1          Introduction  3

2      Solution Architecture Design. 3

2.1        The Applicative Transitions Model 3

2.2        A complete example : the List Selector 4

2.3        Resources Storage. 6

2.4        Notation for Diagramming Applicative Transitions Systems 7

3      Standard Mechanisms Design. 9

3.1        Applicative transitions 9

3.1.1    The "call://" and "exec://" protocols. 9

3.1.2    The "retpage" and "go" arguments. 10

3.1.3    Examples. 10

3.1.4    Standard Applicative Transitions. 11

3.2        HTML pages generation. 12

3.2.1    HTML Templates. 12

3.2.2    HTML Templates Interpretation. 13

3.2.3    Templates Sections, CHtmlPageMaker and Applicative Transitions. 13

3.3        Database. 15

3.3.1    Schema. 15

3.3.2    The DB Query Processor 16

3.4        Gobal simplification. 17


1         Introduction

This document describes the AOBE Applicative Transitions technology and framework and its use to implement the Data base support in AOBE for PocketPC.

2         Solution Architecture Design

2.1      The Applicative Transitions Model

The Applicative Transitions Model is the heart of the solution :

 


2.2      A complete example : the List Selector

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-->