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.
* add "developer mode" preference
* activate WebContentsDebugging also after restart
as the preference option is persisted,
we should call setWebContentsDebuggingEnabled() not only on flag changes.
* capitalize option name, shorter description
* prefer 'can' over 'may'; the latter is very formal
* add Prefs.isDeveloperModeEnabled()
Co-authored-by: B. Petersen <r10s@b44t.com>
* remove unused strings
there were some left over the time :)
- i used the 'Unused Resources' linter in Android Studio
to get delete candidates
- i removed all old 'Contact Request' strings
as we do not have this anymore in that form.
- i checked every string using ./scripts/grep-string.sh
that checks for usages on android, ios, node and desktop.
* remove chat_no_messages_hint
* improve wording of one-to-one-chat hint
at #2134 we shortend the hint shown for an empty group massively,
removing greylisting hints and the hint that the recipient can user other mua.
the result of that shortening is that the creation of a one-to-one chat
is now way too long :)
i suggest shorten the hint in a similar way,
not much would be left then, however, that is maybe not bad :)
* re-add the aspect that the recipient does not need Delta Chat
* pass qr-code strings to core (as qr code images are generated in core now)
* shorter wording of qr code hints
* quote group name as done in most other places
* add 'New Group or Subject' to contact profiles and allow group creation from there
* preselect contacts on group-creation from profile
* remove dead code
* also for existing group-creation, do not finish calling activity needlessly (this is pretty unexpected behavior)
* on editing groups, just use isProtected() from the chat to edit
* adapt 'profile' hint to reality
- the profile hint misses that also the signature
is sent out, together with name and image
- strike the part about that sent information cannot be retracted -
that is pretty clear,
and if we say that here, why not beside every message ;)
not sure where that comes from,
i checked similar settings in other messengers,
there is no comparable hint.
* remove unclear 'alongside' wording
* make new 'join group' strings translatable
* remove now superfluous group-join-progress-dialog
* remove thread-back-to-main roundtrip, joinSecurejoin() should return fast enough, not much different from any other chat creation
cyberta