Difference between revisions of "Rebuild of the Token/Loader System"
(Add Structure section (including block diagram) and start of activities section) |
Tom Parker (talk | contribs) m (→Design Documents) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
==Structure== | ==Structure== | ||
| − | [[Image:Overall_system_figure.png|Block diagram of proposed CDOM structure]] | + | [[Image:Overall_system_figure.png|frame|Block diagram of proposed CDOM structure]] |
| − | The focus of this effort is on implementing the 'Rules Persistence' and 'Rules Data Store' aspects of the CDOM architecture. This builds on the earlier tokenisation work and paves the way for future work on the 'Rules Editor' and the 'Editor UI'. | + | The focus of this effort is on implementing the 'Rules Persistence' and 'Rules Data Store' aspects of the CDOM architecture (pictured to the right). This builds on the earlier tokenisation work and paves the way for future work on the 'Rules Editor' and the 'Editor UI'. |
The '''Rules Persistence System''' is responsible for loading game system and component data from the persistence data file format (game mode, PCC and LST files) and saving it back into that data file format. It is aware of the internal storage of information within PCGen only to the point it is required to store that information for use by the core of PCGen. The Rules Persistence System is not capable of interpreting much in the way of meaning of the values it is storing. | The '''Rules Persistence System''' is responsible for loading game system and component data from the persistence data file format (game mode, PCC and LST files) and saving it back into that data file format. It is aware of the internal storage of information within PCGen only to the point it is required to store that information for use by the core of PCGen. The Rules Persistence System is not capable of interpreting much in the way of meaning of the values it is storing. | ||
| Line 13: | Line 13: | ||
==Design Documents== | ==Design Documents== | ||
| − | PCGen | + | PCGen 5.16 Architecture Overview documents |
* [http://www.geocities.com/thpr/Arch-5.16-0.60-0.0.pdf Architecture Overview Document] | * [http://www.geocities.com/thpr/Arch-5.16-0.60-0.0.pdf Architecture Overview Document] | ||
| Line 21: | Line 21: | ||
# Implementation of the Rules Data Store (much of which is a port from the CDOM branch) - ''Completed'' | # Implementation of the Rules Data Store (much of which is a port from the CDOM branch) - ''Completed'' | ||
| − | # Conversion of tokens to use the new Rules Persistence System. | + | # Conversion of tokens to use the new Rules Persistence System. - ''Completed for main tokens'' |
| − | |||
Latest revision as of 01:54, 3 April 2009
One of the major aims for 5.16 is to rebuild the token and loader system. This will allow for
- Vastly improved LST error reporting
- Improved testability of the tokens
- Each token will be responsible for its own output
Structure
The focus of this effort is on implementing the 'Rules Persistence' and 'Rules Data Store' aspects of the CDOM architecture (pictured to the right). This builds on the earlier tokenisation work and paves the way for future work on the 'Rules Editor' and the 'Editor UI'.
The Rules Persistence System is responsible for loading game system and component data from the persistence data file format (game mode, PCC and LST files) and saving it back into that data file format. It is aware of the internal storage of information within PCGen only to the point it is required to store that information for use by the core of PCGen. The Rules Persistence System is not capable of interpreting much in the way of meaning of the values it is storing.
Design Documents
PCGen 5.16 Architecture Overview documents
Activities
- Implementation of the Rules Data Store (much of which is a port from the CDOM branch) - Completed
- Conversion of tokens to use the new Rules Persistence System. - Completed for main tokens
