| 1 |
Note events are instantiated (serialized) as XML messages and event processing is more or less synonymous to message routing,queuing, archiving and rendering
|
| 2 |
XML data structures could include general <micro> tags as well as more specific sub-tags for each application
|
| 3 |
The micro device display should be similar to display of applications such as memos and mail on existing Palm applications with hierarchical structure
|
| 4 |
So although we use a browser like language (specify messages in XML and render with a device dependent style), the rendering engine is extremely simple compared to a workstation browser
-
All Tango applications will be rendered by same engine on micro device
|
| 5 |
One can either view micro Tango as a standalone client or always invoke a full Tango client on a PC and view this as a proxy for micro device
|
| 6 |
We need to provide a general architecture (libraries) to aid the piping (a.k.a. generating appropriate filter and transmitting events through it to Micro Tango Agent) of events from Tango client to micro Tango agent. Note this piping is responsibility of those applications that can be rendered on a micro device
-
We should support Java and JavaScript applications piping from Tango
|
| 7 |
As a byproduct of this new system, we will get a whiteboard that serializes drawings to XML (presumably in official VML (vector graphics) dialect)
|
