This is a tracking issue for the ongoing overhaul of the main conversations view and related pages. Related MRs: !110, !129 To do first: - [x] implement showing attachments in a simple fashion to be on par with the old implementation (done in !110) - [x] open a tracking issue for all these tasks (#256) - [x] replace `ContactModel` with Sailfish contacts (!110) Message view: - [x] use docked chat input field (!110) - [x] hide input field while scrolling etc. (!110) - [ ] only allow quickly scrolling to the bottom instead of both directions (this only makes sense when the model supports lazy loading, #105) - [ ] improve overall performance; scrolling should go smooth - [ ] emoji selector for emoji reactions Message view sections: - [x] basic section based on timestamp (!110) - [x] *[section]* date (above the first message of a day) (!110) - [ ] sticky section (has to be better than in jolla-messages in SFOS 4) - [x] ~~the model needs a new role named `section` containing an ISO formatted date string with the *day* of each message (e.g. `2021-02-22`)~~ QML automatically already sections the messages by day Special/service messages: - [x] service message, optionally with icon (!110) - [x] service message with link to docs / details (!110) - [ ] *[fake message]* "XX unread messages" above the first (oldest) unread message - [x] *[message]* "missed call" etc. (!110) - [x] *[message]* "fingerprint changed" (!110) - [x] *[message]* "secure session reset" (!110) - [x] *[message]* "xx joined the group" (!110) - [x] *[message]* "xx left the group" (!110) - [x] ... (extend this list when service messages are implemented in the model) Message delegate: - [x] plain text (!110) - [x] linked text: e.g. phone numbers, urls, etc. (is this possible while still enforcing plain text?) (!110) - [-] ~~@-mentions~~ (has to be implemented in a custom text parser) - [ ] emoji reactions (<- custom emoji selector) (menu item prepared in !129) (!468) - [x] `body_ranges` i.e. formatted text; bold, italic, strikethrough, monospace, spoilers - [x] color emojis (setting for system style or custom style; see below) (!110) - [x] timestamp (!110) - [x] sent/received/read markers (!110) - [x] clickable links (!110) - [ ] link previews, maybe OpenGraph - [x] *[group]* sender name / nickname / number (!110) - [-] ~~*[group]* other sender's profile pictures~~ (needs a lot of limited screen space) - [x] *[group]* clickable sender name (opens contact page) (!110) - [x] attachments -> see below (!110) - [x] shorten long messages, "read more..." (!110) - [x] debug info (message id) (!110) - [x] quoted message (!110) - [x] jump to quoted message on click (!110) *bugs:* - [ ] some places rely on identifying contacts based on phone numbers; we shouldn't do that - [x] check if SFOS 4 has "image://theme/icon-s-blocked" - 3.4 doesn't, so we use our own icon for `failed` messages - [ ] if all states are implemented and used, then we should change the default state to 'failed'; until then the default has to be 'queued' to prevent a new message's icon to jump from 'failed' to 'received' -> Message actions (context menu? custom mechanic?) - [x] reply to message (-> custom mechanic) (!110) - [x] UI for: forward message (!129) - [ ] backend for: forward message - [x] delete message (!129) - [x] copy message (!129) - [x] select message(s) (!129) - [x] clear selection (!129) - [x] basic UI for: show message info (-> if only one message is selected) - [x] message info page -> see below - [x] resend failed message (-> only if it failed, not if it is queued) (!129) - [x] react (emoji) ~~(-> custom mechanic?)~~ (context menu item in !129) [emoji selector and delegate tracked above] - [-] ~~open attachment externally~~ - not possible for multiple attachments, has to be handled in the message delegate - [x] export attachment - also possible for multiple* attachments -> Message info (separate page) (#428) : - [x] message - [x] sent timestamp - [x] received timestamp - [x] read timestamp(s) (available? -> need(s) to be exposed) - [ ] sent from / to - [x] groups and 1:1... - [x] debug info (message id) -> Attachment delegates: - [x] -> single (!110) - [x] -> multiple (cf. #51, #11) (!110) - [x] image (!110) - [x] video (note: not fully functional, may be related to #158) (!110) - [x] gif (!110) - [x] audio (!110) - [ ] sticker (what mime type? custom/variable size?) - [x] single emoji -> should be bigger, heart can be pounding, etc. (!110) - [x] document (!110) - [x] contact / vcf (!110) - [x] -> separate contact preview page (!110) - [ ] -> separate attachments page for many attachments - [ ] location (show a map etc.) - [x] voice note *bugs:* - [x] distinguish between voice notes and attached audio files - [x] play audio inline (probably blocked by #255, #245) - [ ] show contact name from file; this requires parsing the file - [ ] handle missing files and failed thumbnails - [ ] show thumbnails for video files (#255) - [ ] adapt attachment to screen orientation, i.e. make/keep them smaller in horizontal mode - [ ] show retry/resend icon - [ ] show attachment upload progress - [ ] show list of all attachments for >5 images or >2 documents - [ ] show image details (metadata, file path, ...) etc., and actions, on an attached page > from https://gitlab.com/whisperfish/whisperfish/-/merge_requests/175#note_565323253: > More plausible would be something like the gallery overlay in Jolla's gallery app: swipe left and right to go through images, swipe up and down to close the overlay, tap an icon (yeh I know) to get a details page. - [ ] allow users to disable auto-playing gifs (#264, #261) -> separate contact preview page: - [x] show vcf file contents using system pages (!110) - [x] save to address book (!110) - [x] directly share to other apps (UI is ready but crashes) (!110) - [x] investigate why sharing a VCF file crashes Whisperfish (it doesn't anymore) -> separate image/video (media) view pages: - [ ] show some info on an attached page - [x] save to somewhere - [ ] share with other apps - [ ] delete locally - [ ] forward to contact(s) - [ ] simple video controls - [ ] don't auto play (#255, #264) - [ ] maybe use a popup instead of a separate page? - [ ] investigate: is it possible to use the system gallery page? (we're out of Harbour anyways...) Input bar: - [ ] emoji selector next to input field (~~or use emoji keyboard -- but I would like to support different emoji sets~~) - [ ] gif selector (giphy?) - [ ] stickers selector - [x] attachment selector (!110) - [x] select multiple attachments at once (use `MultiContentPickerDialog`) (!110) - [ ] select and send a contact - [x] open camera directly (#7 ?) - [x] record voice note directly (!520 / !521) - [x] *[current bug]* fix spacing between input field and latest message (!110) - [x] show preview of replied message (!110) - [x] jump to quoted message on click (!110) - [x] only visible when needed (cf. `ListView::headerPositioning`, `ListView.PullBackHeader`) (!110) *bugs:* - [x] preview quoted attachments (show a small thumbnail of the first attachment) (!110) - [ ] adapt maximum height based on screen size Page header: - [x] profile picture (!110) - [x] saved contact name OR nickname OR phone number (whichever is available) (!110) - [ ] start video call -> on attached page - [ ] start voice call -> on attached page - [ ] search ## For 1:1 chats (Attached pages are also subject of !105 and #215.) Attached page: - [x] enable self-destroying messages (for ... time) (!524) - [ ] list of all media contents (attachments) -> new page - [ ] conversation settings - [x] show current time for self-destroying messages (!524) - [ ] search - [x] reset secure session (requires debug mode) - [x] mute (in SessionDelegate) - [x] add to contacts (!141 ...) ## For groups Attached page: - [x] leave this group (!110) - [x] create invitation link (!110) - [x] add member (!110) - [x] show profile pictures (!110) - [x] direct message to member (!110) - [x] add unknown member to contacts (!110) - [x] link unknown member to existing contact (!110) - [x] directly verify fingerprint (!110) - [x] show member's contact page (!110) - [x] admin: remove member from group (!110) - [x] group name (!110) - [x] description (!110) - [x] group avatar (!110) - [x] wallpaper / background (!110) - [x] mute (in SessionDelegate) - [ ] search members - [ ] list of all media contents (attachments) -> new page - [ ] customize notifications (@-mentions, sound, vibration) - [ ] enable self-destroying messages (for ... time) (!524) - [ ] admin: who can add members? - [ ] admin: who can change group details? (description etc.) - [ ] admin: enable group links? - [ ] search *bugs:* - [ ] clean up code after #223 - [x] use message id instead of index, requires a new model method (!416) ## Emojis Parsing and inserting emojis is currently done in Javascript hased on [twemoji](https://github.com/twitter/twemoji). This is slow and cumbersome and should optimally be done in rust using a custom parser for `LinkedText` (see below). The current system supports different emoji styles which have to be installed to `~/.local/share/sailor-emoji/` by the user. Supported styles: - Sailfish's system emojis - OpenMoji (https://openmoji.org/) - Twitter emojis (https://github.com/twitter/twemoji) - emojis downloaded from Emojipedia (currently [WhatsApp](https://emojipedia.org/whatsapp/) and [Apple](https://emojipedia.org/apple/) (Signal for Android), others?) *bugs:* - [ ] If we decide to "officially" support Openmoji emoji art, we should tell them [on Github](https://github.com/hfg-gmuend/openmoji/issues/125). There appear to be some bugs with a few graphics that maybe could be ironed out, too (it they're not caused by Qt). - [ ] make emoji styles fully configurable (the current implementation requires styles to be registered in `qml/js/emoji.js`) - [ ] We should provide a way for users to download emoji sets to WF's directory in $HOME/.local/share (in-app for open sets, and a guide for proprietary sets). - [ ] We need an entry in the settings page to configure the emoji style - [ ] We need to be able to auto-detect installed emoji sets first - [ ] handle missing icons/characters instead of showing an empty space (should be done in the custom parser) - [x] Add support for [Apple emojis](https://emojipedia.org/apple/) that Signal uses (!276) - [x] investigate the [emoji keyboard](https://openrepos.net/content/ade/emoji-keyboard) ([sources](https://github.com/a-dekker/the-emoji-keyboard)) - [x] move emojis to a shared path (`sailor-emoji`) (!110) **2021-02-28 update:** I wrote a patch (https://openrepos.net/content/ichthyosaurus/patch-stock-emoji-keyboard-colors) for full emoji support in the stock emoji keyboard. It has a settings page and I'm planning to document its `dconf` configuration keys to make them "standardized". Apps like Whisperfish can then simply read the `dconf` key (using `Nemo.Configuration`, `ConfigurationValue`) and decide which style to use. More in #250. - do we still need an entry in the settings page of Whisperfish? (we can't require users to install a patch...) - we don't have to provide emoji sets through Whisperfish, we only point to the documentation ## Rust tasks - [ ] Custom text parser: escape rich text, detect and linkify urls and phone numbers, include emojis as `<img>` elements, convert Markdown-like markup to rich text, @-mentions (like `LinkedText` and the private `LinkParser` but customized) - [ ] check for missing emoji icons when parsing, only include existing icons and keep the system font for the rest - [ ] make emoji style configurable (requires a new setting) - [x] implement emoji reactions (#99) - [ ] implement service messages (instead of saving/showing them as empty messages); the service message type should be exposed as an `enum` - [ ] treat attachments of type `text/x-signal-plain` as very long messages, i.e. don't save them as attachments but save and expose the message text plus the attachment contents as message to the UI - [ ] implement replies / quoted messages (must be a `QObject` with these properties: message, source, outgoing (outbound), message id, (index) - [x] actually show profile pictures (requires #192, #154, #204) - [x] implement message sections (date, see above) - [ ] implement fake service message for the unread boundary, i.e. right above the oldest unread message - [ ] for quoted messages: we need a method to get an `index` for a message `id` (e.g. `MessageModel.indexFromId(mId)`) - [ ] send on click or send on press-and-hold (UI is there, requires #189 and setting `send_on_click`) - [ ] implement multiple attachments in the model; ideally we have two lists (attachments with thumbnails and attachments with details, i.e. image/video and everything else); the UI expects a list of objects like: `[{ data: modelData.attachment, type: modelData.mimeType }]` - [ ] implement shared locations - [ ] implement receiving shared contacts - [ ] implement sharing contacts (works from People app already) - [ ] actually use 'queued' state for messages in `MessageModel` (#183, #105) - [ ] implement 'failed' state for messages in `MessageModel` (#183, #105) - [ ] expose read state of a message per peer (e.g. in groups; #238) - [ ] ... ## Considerations 1. The page header should be sticky so the user always sees who's on the other side. 2. A `PullDownMenu` is not useful even with a sticky page header. The user would have to reach to the top of the page to open it. We should use the attached page (currently `Group.qml` and (?)) instead. 3. A `PushUpMenu` may be useful. Maybe even as emoji selector...? [-> Or advise users to use the emoji keyboard for this -- @ Nathan] 4. It is possible to attach another page to the attached page. (Yes. @direc85) This could be useful: first swipe from the conversations view -> contact details and settings; second swipe -> fingerprint verification 5. We should try to stick to the swipe mechanics - this is what sets Sailfish apart (even though Jolla appears to slowly move away). 6. We should implement "tutorial" hints using `InteractionHint` to help users discover all features 7. ...