Changes between Version 4 and Version 5 of CORE_MVC_BASE_R1
- Timestamp:
- 01/23/09 12:38:58 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
CORE_MVC_BASE_R1
v4 v5 10 10 * Review the [wiki:CORE_MVC_BASE] wiki page and fix to correspond to the current source code. 11 11 * provide the name of the module and a link to the source code of the library part of the MVC. 12 * explain why other part is not possible to put in the library part (Logics and View are tightly connected with one another and separating them will cause dependency troubles).12 * explain why other part is not possible to put in the library part (Logics and Views are tightly connected with one another and separating them will cause dependency troubles). 13 13 * For every functionality in the model, provide corresponding methods to control from the Logics. '''Some''' of them include the following: 14 14 * frame bounds things - margins, paddings etc. … … 21 21 == Task result == 22 22 * Source code. 23 * Integration tests - create models, dummy views to keep the reference to the models and the real logicsmethods to test upon changing things from the view and into the model.23 * Integration tests - create models, dummy views to keep the reference to the models and access the real logics and use their methods to test upon changing things from the view and into the model. 24 24 25 25 == Implementation idea == 26 26 * review the model part and think of all current possible functionalities that are not changed through the logic. 27 * create methods in the Logics => !FrameLogic, !BookLogic and !AppLogic where needed . DO NOT implement the methods - only declarations.27 * create methods in the Logics => !FrameLogic, !BookLogic and !AppLogic where needed, that change the necessary things in the model. DO NOT implement the methods - only declarations. 28 28 * write unit tests for the scenarios. 29 29 * implement the methods in the Logics and test.