| 1 | | We need a well elaborated class hierarchy for our framework (main loop, event handler, factory, loading, resource handling, ...) to seriously start coding the new framework. As soon as possible! |
| | 1 | == Introduction == |
| | 2 | |
| | 3 | We need a well elaborated class hierarchy for our framework to seriously start coding the new framework. As soon as possible! |
| | 4 | |
| | 5 | == Goal == |
| | 6 | |
| | 7 | Following things are a must have: |
| | 8 | * main loop |
| | 9 | * event handler |
| | 10 | * factory |
| | 11 | * loading |
| | 12 | * resource handling |
| | 13 | |
| | 14 | == Implementation == |
| | 15 | |
| | 16 | This is a very important task. Before any coding create an UML diagram and let it be reviewed by the Orxonox veterans. You build the base, the foundation, of Orxonox so a lot of people will have ideas and distract you with them.[[br]] |
| | 17 | Implement multi threading (if possible adaptive to the available processor(s)). |
