Changes between Version 1 and Version 2 of APP_SIMPLE_DIALOGS_R0

Timestamp:

01/20/09 16:43:11 (16 years ago)

Author:

dido

Comment:

--

APP_SIMPLE_DIALOGS_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.)^
+There should be common way of creating dialogs. This class should provide the ability to create and close the dialog as well as to add, remove and interact with dialog childes.
 
 == Task requirements ==
-^(Necessary requirements that the task must fulfill.)^
+Following elements should present:
+ * OK and Cancel buttons - Cancel button is optional and redo the changes. Bought buttons close the dialog.
+ * message or error message - plane selectable but not editable text text. Also optional.
+There should be easy to use interface that populate the data inside the dialog, allows you to add and remove childes, and determines basic layout functionality. 
+You could add as a childes common input elements(input text fields, check boxes, combo boxes etc.) as well as custom elements.
 
 == 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.))^
-
+ * The result should be code
 == Implementation idea ==
 ^(It is advisable to include some rough implementations ideas.)^
@@ -24 +26 @@
 
 == How to demo ==
-^(In this section you must add instructions for the demo of the task.)^
+ * create a test environment and place a button that evoke an instance of simple dialog.
+ * see if you can operate with this dialog.
+ * add some childes in this instance.
 
 = Design =