| 18 | | Implement prototype of comment frames that include following functionality. |
| | 18 | * Model |
| | 19 | * Create model for "comment stream" - the resource which lives on the server. |
| | 20 | * Create model for the frame content which refers the server resource. It must Hold enough information for referring a concrete stream, for changing it and for updating. |
| | 21 | * Persistence |
| | 22 | * The server stream must be persistable in order to be sent to the book |
| | 23 | * The frame content resource must be persistable in order to save the stream reference along with the book. |
| | 24 | * Manipulation |
| | 25 | * It must be decided who will have rights to do what |
| | 26 | * Decide how will a stream be created / destroyed - from client, from web UI ot both. |
| | 27 | * Decide about the relation between frame content resource and server stream - one to one or many to one. |
| | 28 | * Decide whether it will be possible to forbid comment rights on particular readers, e.g. whether the comment frame will use the base.security model. |
| | 29 | * Client <-> Server communication |
| | 30 | * The server web services must allow communication related to comment streams. |
| | 31 | * decide whether the facade will include comment manager. |
| | 32 | * View |
| | 33 | * The comment content must be able to auto-refresh itself. |
| | 34 | * The comment frame must be editable only in preview mode / reader mode. Comment frame interactions must be defined. |
| | 35 | * The location of the input form must be defined - whether it will appear as a dialog or inside the frame. |
| | 36 | * The comment frame must have scroll bar. |
| | 37 | * The text in comment frame must be properly formatted - indent, header style. Consider using the current hot text model. |
| | 38 | |
| | 39 | Implement prototype of comment frames that include the following functionality: |
