* simplify contact list
this also disables "fast scrolling" for the contact list;
the "fast scrolling" code is too much bound to the bubbles and a-z
to be preserved without much effort.
however, "fast scrolling" seems to be much less important
with a list sorted by "last seen".
there is also the rough idea to raise minimal-origin of contact list,
this would make the list much smaller
(<https://github.com/deltachat/deltachat-core-rust/pull/2411>),
otoh, not sure if #2411 is a thing for list sorted by "last seen".
also the other lists (chatlist, archive, blocked) may become quite huge as well
and do never have "fast scrolling".
in case it is really needed again,
however, we should go for the implementation available in RecyclerView since some time:
<https://stackoverflow.com/questions/45370246/how-to-use-fastscrollenabled-in-recyclerview>
* less padding as the A-Z decorations do not longer need space
* remove unused contact_selection_recyclerview_header
* add 'Add to Home Screen' menus for webxdc apps
* make adding shortcut basically work
* avoid starting webxdc from foreign accounts
* recreate back stack, if possible
according to
https://developer.android.com/training/notify-user/navigation :
"When you start an activity from a notification,
you must preserve the user's expected navigation experience.
Tapping Back should take the user
back through the app's normal work flow to the Home screen [...]"
same seems to be true for shortcuts using the same class for constructing
the back stack.
the back stack is reconstructed for API 26 (Oreo, 2017) or newer,
for oder API `requestPinShortcut()`
only uses the top-level activity for the shortcut.
working around that is probably possible, but would be quite some effort in an
already complicated area and would result in bugs that are not so easy to see.
also, on these old androids, users are probably used to the no-back-stack
behaviour.
* show a warning if app was deleted
* add 'Add to Home Screen' also to gallery
beside chat- and webxdc-activity,
this is the third place where the webxdc is listed.
as adding may result in dialogs from the launcher,
we allow the option only for a single selected webxdc,
as otherwise a series of dialogs would pop up.
* show 'Done' toast short, this is what we are doing at all the other places when showing 'Done'
- "Files" is broader than "Docs"
(documents are just one type of files,
files can also be executables and whatnot)
- at other places in the app, we also speak of "Files"
("sending files" etc.)
- Delta Chat iOS also uses the term "Files"
* bump version to 1.31.0
* update changelog for 1.31.0 (add core88 features)
* update changelog for 1.31.0 (android features)
* remove outdated device message, the final 1.32 will probably get a fresh one
`videochat_instance_explain_2`+`videochat_instance_example`
is mostly the same as `videochat_instance_explain`
but offers nicer layout on desktop.
to make things easier for translators,
we aim to remove `videochat_instance_explain`.
for webxdc, the system-back-button should do the same
as the back-button in the title bar - just close the webxdc.
without this commit, it loads the previous page, which is often unexpected -
eg. many games use reload() for simplicity,
so you would have press one time 'back' for each round :)
even if there may be situations where this may be useful,
we do not want to encourage webxdc to rely on the system-back-button -
eg. desktop or ios currently just do not have this button.
technically, this pr changes the default -
so, for all classes derived from WebViewActivity, the system-back-button will
now behave as the title-bar-back-button.
for the local-help, this behavior is changed explictly -
i think, for HTML-mails, the 'just close' approach is also better.
show the chat name in front of the webxdc name to
- prevent phishing (the window will not show just the name of your bank)
- give the user an idea about where the webxdc sends messages to
(important eg. when using the same webxdc from different chats)
the UI does not check before selection if a message can be resent,
this is subject to change and not worth the effort.
instead, just an error is shown.
for the ID_NEVER_SHOW_AS_ACTION_* - this is a bit ugly,
however, the few alternatives i tried were even more uglier,
Java and Array-primitives are just not great.
as it is not changed often, it is probably not worth the effort to dive deeper.
* Fix off-by-one-error
* Wait longer with refreshing shortcuts to make sure that it doesn't affect the start of the activity
* Don't unnecessarily clear "screenshot security" flag
If this setting is off, the flag will never be added, so no need to
remove it.
bjoern