Changes between Version 5 and Version 6 of GROUP_READER_R0

Timestamp:

05/08/09 19:19:11 (16 years ago)

Author:

pav

Comment:

--

GROUP_READER_R0

@@ -42 +42 @@
 
 = Design =
-Connected with the design of the reader:
- * Undo/Redo will be available.
-Separation of the modules will be:
+For the implementation first separation of the modules has to be created and it includes the following things:
  * main.app.commons module with commons application things - think as there is no application without them.
- * main.app.reader - ReaderBookDocumentWindow, ReaderBookDesktopWindow, ReaderArea will be in this module.
+ * main.app.reader - ReaderBookDocumentWindow, ReaderBookDesktopWindow, ReaderAppDocumentsDesktop classes have to be in this module. 
+  * It must have ReaderModule class which will register all of the extension/extension points needed for showing the functionality of the requirements(in the analysis section). 
   * When separating the classes parts of the BookLogic(userActs method) have to be implemented with the new LogicR3. There has to be three events for closing, selecting and deselecting the book window. !UserWindowAction can be used as events that has to be handled.
+  * org.sophie2.reader - it must contain FakeReaderMain class which will start ReaderModule instead of MainAppModule. Do not forget to add the bundle activator in pom.xml file.
+  * reader fake and true launch configuration - it is the same as author but using org.sophie2.reader module as attribute.
+  * reader.bundles.config file with the modules needed for running the reader. It has to be located in src/main/resources as it is in the author module.
+The design is simple for now - the main idea of this revision is to run(fake or true running) different from author edition. The following steps has to be done:
+ * ReaderBookDocumentWindow/ReaderBookDocumentWindow will extend the corresponding windows that are already implemented but with overritten methods for preview mode, outline frames and outline connections. When app.author module is implemented there will be AuthorDocumentwindow which will extend BookDocumentWindow so that the BookDocumentWindow will be base class for the author and reader.
+ * ReaderAppDocumentsWindow has to be created so the created window will be reader one not author.
+ * When registering extensions in the reader do not add preview mode and outline frames panels. Use !AutoVisualProvider where possible instead of !SimpleVisualProvider
+About the things not cleared up in the task requirements:
+ * Undo/redo functionality should be available(when it is implemented)
+ * View menu can be implemented in the next revisions but for now there is no need for this.
  * If there is time main.app.author can be created - it will have the same structure as the reader module but with Author prefix before the classes.