| 32 | | Be sure you understand MVC and Singleton. [[BR]] |
| 33 | | see http://en.wikipedia.org/wiki/Model-view-controller - MVC Pattern. [[BR]] |
| 34 | | see http://en.wikipedia.org/wiki/Singleton_pattern - Singleton Pattern. [[BR]] |
| 35 | | |
| 36 | | MVC is based upon the MVC pattern. Our Model consists of Apps with Books with Pages with Frames. Frames have variation like !TextFrames, !ImageFrames and !MediaFrames. Out View is the !AppView, !BookView, !PageView and !FrameView. !FrameViews are devided in three - !TextFrameView, !ImageFrameView, !MediaFrameView The Controller part is represented by the Logics. We have !AppLogic, !BookLogic, !PageLogic and !FrameLogic. While one can create instances of the model and view (Books, Pages, Frames, AppViews, BookViews, PageViews etc.), the Logics are singletons. |
| | 32 | * Be sure you understand MVC and Singleton. Since these will be the patterns used for the base design and implementation of the MVC. [[BR]] |
| | 33 | * see http://en.wikipedia.org/wiki/Model-view-controller - MVC Pattern. [[BR]] |
| | 34 | * see http://en.wikipedia.org/wiki/Singleton_pattern - Singleton Pattern. [[BR]] |
| | 35 | * Model and View - represented by App, Book, Page, Frame, TextFrame, ImageFrame, MediaFrame, AppView, BookView, PageView, FrameView, ImageFrameView, TextFrameView and MediaFrameView. |
| | 36 | * Logic - singleton (instantiated the first time it is called.) |
| | 37 | * This is sensible because: |
| | 38 | * We need to have multiple books with pages and frames as well as multiple views to display the model. |
| | 39 | * 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 implement it. |
| | 40 | * View will be automatically updated on model change. |
| | 41 | * View will commit data to model on user intervention by the corresponding logic. |
