Changes between Version 1 and Version 2 of BASE_HALOS_R0

Timestamp:

12/18/08 16:06:35 (16 years ago)

Author:

peko

Comment:

--

BASE_HALOS_R0

@@ -6 +6 @@
 
 = 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.)^
+ This task requires a base implementation of the Halos. The idea is to have a base hierarchy in a separate module that the actual implementation classes use.
 
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+ * Create a module org.sophie2.base.halos
+ * Extract the base hierarchy for Halos and put it in that module. (all halos are now in the org.sophie2.main.view module).
+ * Create a UML diagram for the base classes.
+ * Make the org.sophie2.view.main dependable on the org.sophie2.base.scene module.
+ * Review currently implemented classes of halo buttons, menus, huds.
+ * Provide a general explanation of how new halos should be implemented.
+  * How should one create a HUD.
+  * How should one create a Halo Button.
+  * How should one create a Halo Menu.
 
 == 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.))^
+ * wiki page.
+ * diagrams
+ * source code
+ * new module in sopehie2-platform.
 
 == Implementation idea ==
-^(It is advisable to include some rough implementations ideas.)^
+ * create the module.
+ * fix the halos.
+ * create other things described in Task Requirements section.
 
 == Related ==
-^(Here you can add related tasks that could be useful or helpful.)^
+ * a similar things is already done by BASE_LAYOYT
 
 == How to demo ==