| 9 | | ^(Provide a brief overview of the whole task in its first revision. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)^ |
| | 9 | * 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. |
| | 10 | * 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. |
| | 11 | * Show status (connected, disconnected, connecting etc.) of a server |
| | 12 | * Also a list of available resources for the selected server should present. |
| | 13 | * It will be nice if we could manipulate this list (or tree, or whatever comes up) of resources in the same manner as we do inside resource palette |
| 12 | | ^(List the necessary requirements that the task must fulfill.)^ |
| | 16 | * Create prototype of server palette |
| | 17 | * (OPTIONAL) provide manipulation over the server list |
| | 18 | * To add, remove or edit the available servers. |
| | 19 | * No user name and password will be preserve at this point |
| | 20 | * Make available connection to the server |
| | 21 | * Only as anonymous user at this point (until there is some security for the server) |
| | 22 | * After the user is connected show a list of available resources |
| | 23 | * At this revision no sub resources will be shown. Only a few books. |
| | 24 | * No meta data will be shown, only the name of the resource(book)(for now) |
| | 25 | * No filters at this revision |
| | 26 | * The user won't be able(for now) to do the following |
| | 27 | * Add resource(book) |
| | 28 | * Remove resource |
| | 29 | * Rename resource |
| | 30 | * Provide some way for server synchronization |
| | 31 | * Some kind of basic online collaboration should be available |
