Reorganise modules
At this moment, we're continuously adding modules. Some of them have got more tasks than they should have, e.g. ui modules which also include ui independent logic. It's not hard to split them off and it doesn't break much code, but it's good to have an overview of what changes are going to be done. Let's use the whiteboard for that purpose.
Blueprint information
- Status:
- Complete
- Approver:
- OpenTeacher Maintainers
- Priority:
- High
- Drafter:
- OpenTeacher Maintainers
- Direction:
- Approved
- Assignee:
- OpenTeacher Maintainers
- Definition:
- Approved
- Series goal:
- Accepted for 3.x
- Implementation:
-
Implemented
- Milestone target:
-
3.1
- Started by
- Marten de Vries
- Completed by
- Marten de Vries
Whiteboard
Adjust:
* the saving API: Pass the complete Lesson object (which has list, image etc. properties) instead of the list and resource objects. If possible, rename resources since it sounds a bit generic. -> Implemented (assignee: ~marten-de-vries)
* the same for the loading API -> Implemented (assignee: ~marten-de-vries)
Put into separate modules:
* html generators? (for saving and printing?) -> Implemented (assignee: ~marten-de-vries)
Put common code in a module:
* printer & saver -> Implemented (assignee: ~marten-de-vries)
* otwd, ottp, ottmd -> Implemented (assignee: ~marten-de-vries)
Split:
* wrtsApi
* Classes to interact with the API (maybe the woordjesleren.nl can have a similar interface, so the UI is reusable.)
* UI
* topo and media, like words <- Implemented (assignee: ~milan-boers)
* wordsTeacher and related classes, so it's easy and convenient to write the test client without any 'hacks'. <- Implemented
