| Lines 4-9 were replaced by lines 4-7 |
| - in SICS/SEA written in Tcl. Scuh a driver is a collection |
| - of configuration and action scripts. |
| - The action scripts are called from the ScriptContext system |
| - with in a certain context: a sics hipadaba node and a |
| - controller object. The access to the context is implemented |
| - with the {{sct}} command. |
| + in SICS/SEA written in Tcl. Such a driver is a collection |
| + of initialization and action scripts. The action scripts |
| + are called from the ScriptContext system within a certain |
| + context: a sics hipadaba node and a controller object. |
| Line 11 was replaced by line 9 |
| - !Initialization Script |
| + !Tutorial |
| Lines 13-14 were replaced by line 11 |
| - The scripts should be placed in a |
| - file with a path {{~/sea/tcl/drivers/<driver-name>.tcl}} |
| + * [A simple driver example] |
| At line 15 added 11 lines. |
| + !Reference |
| + |
| + * [initialization commands|StdSctInitCmds] |
| + * [standard action scripts] |
| + |
| + |
| + |
| + ---- |
| + |
| + to be done |
| + |
| Removed lines 20-39 |
| - The initialization script must have the name |
| - {{stdConfig::<driver-name>}}. |
| - |
| - The first command to be called is one of: |
| - {{{ |
| - controller <protocol> <protocol parameters...> |
| - controller std <send terminator> <timeout> <reply terminator> <separator> |
| - controller bin <crc-algorithm> <timeout> |
| - }}} |
| - |
| - Other protocols than std and bin might be programmed in the core SICS code, |
| - in fact there are already a couple of them programmed by Mark Koennecke. |
| - For some needs, it might be easier to enhance the std or bin protocol. |
| - |
| - |
| - return value is 1 when the controller was created, 0 when |
| - it existed already (the return value may be needed if several |
| - object share the same controller, and the initialization of |
| - the controller properties have to be done only once). |
| - |
LIN