3
edits
Education/Projects/JetpackForLearning/Profiles/Hoovernotes: Difference between revisions
Jump to navigation
Jump to search
Education/Projects/JetpackForLearning/Profiles/Hoovernotes (view source)
Revision as of 06:40, 1 February 2010
, 1 February 2010→The architecture and implementation
| Line 66: | Line 66: | ||
==The architecture and implementation== | ==The architecture and implementation== | ||
Basically, HooverNotes follows an MVC pattern. | |||
There are 3 classes: | |||
- HooverNotesView: Updates the slide bar. | |||
- HooverNotesController: Contains the main business logic. | |||
- HooverNotesStorage: Used for synchronizing the data maintained in the GUI with permanent storage. | |||
These 3 components interchange information about HooverSheet, HooverPage and HooverNote data objects (DOs). A HooverSheet contains a HooverPage which contains a HooverNote. Each of these objects is identified by randomly generatd GUIDs. | |||
When constructing the GUI, each of these DOs is represented by the following three DIV elements: | |||
- a container, representing the whole object | |||
- controls, containing the GUI controls such as buttons. | |||
==Not debugged, so no included== | ==Not debugged, so no included== | ||