Changes between Version 2 and Version 3 of UNPLANNED_APP_CLIENT_RESOURCES_R0

Timestamp:

09/16/09 17:07:02 (16 years ago)

Author:

tsachev

Comment:

--

UNPLANNED_APP_CLIENT_RESOURCES_R0

@@ -8 +8 @@
 == Overview ==
  * The goal is to move as close as possible for one week, to what we wont for the user to be able to do with server resources inside the application. Please view the analysis in [wiki:GROUP_APP_SERVER_RESOURCE_ACCESS_R0] to achieve more global vision for this task.
- * There should be palette (server palette) that will allow the user to chose (add, remove, edit the current url etc.) a server and then connect to it.
+ * There should be palette (server palette) that will allow the user to chose (add, remove, edit the current account) a server account and then connect to it.
   * Show status (connected, disconnected, connecting etc.) of a server
  * Also a list of available resources for the selected server should present.
@@ -15 +15 @@
 == Task requirements ==
  * Create prototype of server palette
-  * (OPTIONAL) provide manipulation over the server list
+  * Provide manipulation over the list with server accounts
    * To add, remove or edit the available servers.
-   * No user name and password will be preserve at this point
+   * User names and passwords
+   * Persist the server accounts in some configuration file
   * Make available connection to the server
    * Only as anonymous user at this point (until there is some security for the server)
   * After the user is connected show a list of available resources
-   * At this revision no sub resources will be shown. Only a few books.
+   * At this revision no sub resources will be shown. Only a first level resources.
    * No meta data will be shown, only the name of the resource(book)(for now)
    * No filters at this revision
@@ -28 +29 @@
     * Remove resource
     * Rename resource
-  * Provide some way for server synchronization
-   * Some kind of basic online collaboration should be available
+  * Provide some aspects of the server synchronization
+   * Some handling and notification should be considered if connection to server is closed, drop or some other similar situation occurs.
 
 == Task result ==
@@ -42 +43 @@
 == How to demo ==
  * Start the application
- * Go to resource palette and conect to the server
+ * Go to resource palette and connect to the server
  * Focus(Show) the list of available resources on the server and open one
  * Edit and save the resource on the server via the app (add frame or page or something)
-
+ * Disconnect from server and show that user cannot manipulate and view this resource anymore.
+ * Show adding of new server, deleting of one and editing.
+ * Show that accounts are available after restarting the application.
 = Design =
 ^(Describe your design here.)^