Changes between Version 2 and Version 3 of UNPLANNED_CORE_MVC_BASE_R0

Timestamp:

10/13/08 15:53:05 (17 years ago)

Author:

peko

Comment:

--

UNPLANNED_CORE_MVC_BASE_R0

@@ -2 +2 @@
 
 = Analysis =
-^(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)^
 
 == Overview ==
-^(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^
+ * The Model-View-Controller(MVC) pattern will be used in the development process of Sophie 2. All the necessary rules about MVC in the development process should be defined.
 
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+ * The document should provide:
+  * General rules about MVC.
+  * List of the base classes needed.(class diagrams can be made)
+  * Docs and tutorials about implementing MVC (especially in Sophie 2).
+  * Rules to check whether the code complies to the pattern.
 
-== Task result ==
-^(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))^
+== Task Result ==
+ * The result of this task should be a wiki page where all of the rules are written.
 
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
+ * Old wiki can be useful.
+  * [[http://asteasolutions.net/mediawiki/index.php/Sophie-JR-MVC-Pattern Sophie-JR-MVC-Pattern]]
+  * [[http://asteasolutions.net/mediawiki/index.php/Sophie-JR-MVC-Refactoring Sophie-JR-MVC-Refactoring]]
+  * [[http://asteasolutions.net/mediawiki/index.php/Sophie-JR-MVC-Design Sophie-JR-MVC-Design]]
+  * [[http://asteasolutions.net/mediawiki/index.php/Veda-Design-Refactor2#MVC Veda-Design-Refactor2#MVC]]
 
 == Related ==
-[wiki:CORE_MVC_BASE_R0]
+-
 
 == How to demo ==
-^(In this section you must add instructions for the demo of the task.)^
+ * Open the wiki page where the rules are written (it can be called "CORE_MVC_BASE" for example).
+ * Look if all of the analysis points are took into consideration.
+ * Make sure that nothing important is dropped.
 
 = Design =
+ * Be sure you understand MVC and Singleton. Since these will be the patterns  used for the base design and implementation of the MVC. [[BR]]
+  * see http://en.wikipedia.org/wiki/Model-view-controller - MVC Pattern. [[BR]]
+  * see http://en.wikipedia.org/wiki/Singleton_pattern - Singleton Pattern. [[BR]]
+ * Model and View - represented by App, Book, Page, Frame, !TextFrame, !ImageFrame, !MediaFrame, !AppView, !BookView, !PageView, !FrameView, !ImageFrameView, !TextFrameView and !MediaFrameView.
+ * Logic - singleton (instantiated the first time it is called.)
+ * This is sensible because:
+  * We need to have multiple books with pages and frames as well as multiple views to display the model.
+  * We need to control the model by the view. This means that the Controller must have only functions implemented and called. It SHOULD NOT HAVE STATE. That is why singleton pattern will be used to instantiate it.
+ * View will be automatically updated on model change.
+ * View will commit data to model on user intervention by the corresponding logic.
 
 = Implementation =
-^(Implementation results should be described and linked here (from the wiki or the repository)^
+The implementation is based upon the requirements. List of the base classes and their class diagrams are added. We don't need rules to implement the MVC since it is relatively simple at this point. Though rules about its usage will be provided.
+
+[wiki:MVC_STRUCTURE MVC]
 
 = Testing =