Last modified 16 years ago
Last modified on 01/29/09 14:26:58
Analysis
Overview
This task is about all the common things of templates and templating. Generally we have templates for books, pages and frames and the model should be able to manage them.
Task requirements
- Common things about templates should be extracted in a class hierarchy.
- This includes base classes.
- Helper classes.
- Storage of templates.
- Template resources.
- A mechanism for template manipulation should be designed:
- creating templates.
- deleting templates.
- loading templates.
- storing templates.
- changing templates.
- Consider creating a TemplateManager if needed. This is somethings that is analogous to the BookResourceManager but is quite different on the other hand:
- It is global and is defined for every App (not Book as is the BookResourceManager).
- It should be able to manage all kinds of templates.
- Provide diagrams of the class hierarchy and utilities to manage templates.
- Since this is a one day effort task, a thorough design with diagrams should be enough to start with.
- If there is time left, implement what has been decided and write unit tests.
Task result
- wiki content.
- diagrams.
- (source code with integration tests if there is time to do it.)
Implementation idea
- Review the related tasks.
- Design the way templates are going to be managed by the model.
- Create diagrams and give explanations of the things that are decided.
- (Implement and test if there is time left.)
Related
- BOOK_TEMPLATES_BEHAVIOUR_R0
- BOOK_TEMPLATES_LISTING_R0
- PAGE_TEMPLATE_BEHAVIOUR_R0
- PAGE_TEMPLATES_LISTING_R0
- FRAME_TEMPLATES_R0
How to demo
- Show the wiki and explain in general the idea.
- (run unit tests if such have resulted).
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
(Write comments for this or later revisions here.)