Difference between revisions of "GUI Capture (Developement)"
| Line 5: | Line 5: | ||
===Platform independence=== | ===Platform independence=== | ||
| − | For the output to remain platform independent from the input, the engine passes the events in a uniform format to the output which can use the ''process_xy_event'' features inherited from the CAPTURE_EVENT_VISITOR class to generate the output. | + | For the output to remain platform independent from the input, the engine passes the events in a uniform format to the output which can use the ''process_xy_event'' features inherited from the CAPTURE_EVENT_VISITOR class to generate the output. The input is generated by the engine implementation which is specific for the platform used. |
==Event Hierarchy== | ==Event Hierarchy== | ||
Revision as of 14:03, 31 October 2006
Overall structure
Platform independence
For the output to remain platform independent from the input, the engine passes the events in a uniform format to the output which can use the process_xy_event features inherited from the CAPTURE_EVENT_VISITOR class to generate the output. The input is generated by the engine implementation which is specific for the platform used.
Event Hierarchy
To allow different output formats, the events types are equiped with a process feature which implements the visitor pattern together with the CAPTURE_EVENT_VISITOR class.
