... | @@ -79,25 +79,36 @@ This mixture of roles of the `ConversationTextview` complicates replacing the pr |
... | @@ -79,25 +79,36 @@ This mixture of roles of the `ConversationTextview` complicates replacing the pr |
|
a. Add new setup to this document
|
|
a. Add new setup to this document
|
|
a. Agree on changed separation of concerns with @lovetox (and others?)
|
|
a. Agree on changed separation of concerns with @lovetox (and others?)
|
|
2. Gradually implement the new separation
|
|
2. Gradually implement the new separation
|
|
3.
|
|
3. Based on separated concerns, design a ConversationListBoxview and ListBoxrow
|
|
|
|
4. Implement minimal Listboxrow and ConversationListBoxview
|
|
|
|
5. Synchronize APIs between ConversationListBoxview and ConversationTexview
|
|
|
|
6. Based on some developer setting make listboxview and textview selectable
|
|
|
|
7. Work on primary ListBoxrow until it's on-par with the current textview approach
|
|
|
|
8. (merge the on-par replacement to master?)
|
|
|
|
9. Develop specialized ListBoxrows for status messages, subject lines, etc., etc.
|
|
|
|
|
|
|
|
|
|
## Requirements for a new design
|
|
## Requirements for a new design
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### High level functional requirements
|
|
### High level functional requirements
|
|
|
|
|
|
|
|
* Allow for progressive introduction of improved presentation of various types of "messages" (rows)
|
|
|
|
* Allow swapping in/out of the current Textview based on developer need (and allow experimentation with other presentations in the future)
|
|
|
|
* Be on-par presentation-wise with the existing view (before being merged to master)
|
|
|
|
|
|
### Technical design
|
|
### Technical design
|
|
|
|
|
|
|
|
* Separate the concerns (at least) to be able to swap various presentation experiments quickly and easily
|
|
|
|
* presentation
|
|
|
|
* managing the presented content & reacting to (user) input
|
|
|
|
* Building presentation logic which maps various types of messages to their respective ListBoxrow classes to allow differences per message(type)
|
|
|
|
|
|
### Concluding
|
|
### Concluding
|
|
|
|
|
|
|
|
(to be done)
|
|
|
|
|
|
|
|
|
|
|
|
### Addendum
|
|
|
|
|
|
In a chat with @lovetox, the following requirements were mentioned as well:
|
|
In a chat with @lovetox, the following requirements were mentioned as well:
|
|
|
|
|
... | @@ -108,4 +119,7 @@ In a chat with @lovetox, the following requirements were mentioned as well: |
... | @@ -108,4 +119,7 @@ In a chat with @lovetox, the following requirements were mentioned as well: |
|
[04:47:25 PM] lovetox: the message row object should be based on some generic object, we will probably
|
|
[04:47:25 PM] lovetox: the message row object should be based on some generic object, we will probably
|
|
need many row objects that slightly differ
|
|
need many row objects that slightly differ
|
|
[04:47:43 PM] lovetox: like some kind of status messages, error messages, info messages, etc
|
|
[04:47:43 PM] lovetox: like some kind of status messages, error messages, info messages, etc
|
|
|
|
[04:49:23 PM] wurstsalat: File transfers, image previews :)
|
|
```
|
|
```
|
|
|
|
|
|
|
|
|