AquaMail Forum
English - Android => Development builds => Topic started by: Kostya Vasilyev on November 11, 2015, 08:33:09 pm
-
http://www.aqua-mail.com/download/AquaMail-market-1.6.0-14-dev1.7.apk
---
+ Добавил настройки внешнего вида сгруппированных сообщений.
+ Испровления ашибак.
---
+ Added settings -> conversations -> appearance customization.
+ Bug fixiz.
-
Kostya,
Very good decision to move the options for Conversation in a own Settings section.
Unfortunately I realized that the description of the "position counters" iin a message of a conversation is mixed up again with build 1.6.0-14-dev1.7/1.7.1
> see screenshot #2
-
Yes, I changed it.
I keep trying to find better wording, if you have suggestions, please share.
-
Yes, I changed it.
I keep trying to find better wording, if you have suggestions, please share.
Regarding the screenshots in my previous post the "Position counter" in a conservation (screenshot #2) is currently wrong (reversed):
MESSAGE 1/3 IN CONVERSATION 22/37
My suggestion (for #2) is as follows:
MESSAGE 21/37
MESSAGE 22/37 IN CONVERSATION 1/3
MESSAGE 23/37
The wording itself is perfect.
-
Hi Kostya, I like conversation mode, very useful and ergonomic to enter in detailed list.
In my short experience, I have 4 email in sequence but I find 2 groups, not one with counter 4.
Thanks
(http://images.tapatalk-cdn.com/15/11/11/c930080cf2030a380726e91a0792eb58.jpg)
Watches: G-Shock Rangeman GW-9400 Black, Olive, Camouflage, GW-M5610
-
It defeats the purpose: you don't know where you are within the conversation. There was a thread in these forums that inspired this.
-
http://www.aqua-mail.com/download/AquaMail-market-1.6.0-14-dev1.7.apk
---
+ Добавил настройки внешнего вида сгруппированных сообщений.
+ Испровления ашибак.
---
+ Added settings -> conversations -> appearance customization.
+ Bug fixiz.
Conversations now considers subject: new subject means new conversation.
Why?
This is not good.
Some Mail-Clients put a "RE" or "AW" or "Antwort" or whatever in front of the subject.
Now we always have a new conversation where why don't want to have one.
I'v attached a screenshot how it looks in mutt (the mother of all E-Mail clients!),
1 thread with 7 messages.
And a screenshot with AM, 1 message and 3 threads with 2 messages each.
-
This broke in dev1.6 and is still broken:
It seems that when you accept an email calendar invite on EWS exchange account, that invite does not move to the deleted folder as it once did. I think conversation view broke that.
Is there any way to fix it?
Thanks
-
It defeats the purpose: you don't know where you are within the conversation. There was a thread in these forums that inspired this.
So we can keep option 2, where the user knows exactly where he/she is within the convesation, or replace it by option 4 or 5, where:
- the user knows exactly where he/she is within the conversation
- outside a conversation (single message), the user knows exactly where he/she is within the global message list (by swiping, all those messages can be reached).
See my new slide
Hi Paris Geek,
I prefer #1 (as it was in dev1.4) or #4 (your new suggestion).
#2 (since dev1.6) is confusing me, since the position counter (e.g. "Message .. /37") changes everytime his own position when you swipe into /out of a conversation:
MESSAGE 20/37
MESSAGE 21/37
MESSAGE 1/3 IN CONVERSATION 22/37
MESSAGE 2/3 IN CONVERSATION 22/37
MESSAGE 3/3 IN CONVERSATION 22/37
MESSAGE 23/37
MESSAGE 24/37
#5 will also confusing me, since the counter of total messages changes in the same manner (.. /3 >.. /14)
#3 looks like #4, but the user couldn't see the total number of messages within the current conversation.
-
Conversations now considers subject: new subject means new conversation.
Why?
This is not good.
Some Mail-Clients put a "RE" or "AW" or "Antwort" or whatever in front of the subject.
Now we always have a new conversation where why don't want to have one.
I'v attached a screenshot how it lokls in mutt (the mother of all E-Mail clients!),
one thread wit 7 messages.
And a screenshot with AM, 1 message and 3 threads with 2 messages each.
@druckmusik:
Thanks for this great example.
That's another reason to leave the choice by the user:
(A) conversation by referenced messages (dev1.4)
or
(B) "breaking" conversation by subject (since )
@Kostya:
I would very much appreciate if you will think about such an option in Conversation settings 8)dev1.6
-
Actually it is
(A) conversation by referenced messages (dev1.4)
or
(B) "breaking" conversation by subject (since dev1.6)
I agree with you Mikeone, I've said since the beginning that a user choice here is needed. I thought that (B) could be by default, but after seeing the issues posted by @Fcalosi, @druckmusik, @str, etc. I would prefer (A) (dev 1.4) as the default. Only one user has reported an issue for dev1.4, compared to many issues reported by others for dev1.6 method.
Thanks for your reply Paris Geek.
Full compliance 8)
-
Re: Some Mail-Clients put a "RE" or "AW" or "Antwort" or whatever in front of the subject.
"Re:", "Aw:", "Fwd:", "Отв:", and also "Re[2]:", "Fwd[10]:" and their combinations are removed / ignored when comparing subjects.
"Antwort:" is just crazy :)
Re: attached a screenshot how it lokls in mutt
Umm... Yep, different subjects.
Re: It seems that when you accept an email calendar invite on EWS exchange account
Will take a look, thanks.
-
"Re:", "Aw:", "Fwd:", "Отв:", and also "Re[2]:", "Fwd[10]:" and their combinations are removed / ignored when comparing subjects.
"Antwort:" is just crazy :)
Antwort is "Re", correct?
Is there a similar "long version" for "Fwd"?
Please don't tell me there is, and it's something like "Weitergeleiteten: original subject" :)
PS - I added "Antwort" as a special case in subject cleanup code, if you clarify on "Fwd", I'll add that too.
-
"Re:", "Aw:", "Fwd:", "Отв:", and also "Re[2]:", "Fwd[10]:" and their combinations are removed / ignored when comparing subjects.
"Antwort:" is just crazy :)
Antwort is "Re", correct?
Is there a similar "long version" for "Fwd"?
Please don't tell me there is, and it's something like "Weitergeleiteten: original subject" :)
PS - I added "Antwort" as a special case in subject cleanup code, if you clarify on "Fwd", I'll add that too.
"Antwort" should be sufficient..
"Weitergeleitet" isn't usual.
Thanks Kostya
-
"Weitergeleitet" isn't usual.
I can exhale now :)
-
"Weitergeleitet" isn't usual.
I can exhale now :)
8)
The common abbreviation in German is "WG" (= "Fwd").
-
I just check for 2 or three characters followed by ":" or "[one or two digits]:".
There can be some false positives, but it would be crazy to try and have a dictionary with all languages (even ones which the app isn't localized into).
-
You are forgetting about people interacting across borders and languages.
How about things inserted by mailing lists, usually in square brakets and matching those messages with the Sent message that don't have these prefixes?
I
There can be some false positives, but it would be crazy to try and have a dictionary with all languages (even ones which the app isn't localized into).
-
Re: You are forgetting about people interacting across borders and languages
Am I?
I do it every day, sometimes even before breakfast.
Re: square brakets
Do you think anything between and including square brackets should be removed?
-
Re: You are forgetting about people interacting across borders and languages
Am I?
I do it every day, sometimes even before breakfast.
I didn't doubt that, I was only responding to the statement quoted.
Re: square brakets
Do you think anything between and including square brackets should be removed?
Not removed (for display purposes), but "yes", ignored for the analysis of "sameness".
Otherwise Messages in {Sent} wouldn't link to those received in response via the mailing list.
Just as an curious aside, the aforementioned RFC 5256 says:
Translations of the "re" or "fw"/"fwd" tokens are not specified for
removal in the base subject extraction process. An attempt to add
such translated tokens would result in a geometrically complex, and
ultimately unimplementable, task.
... I hope you are enjoying that process! :P
-
Nope, never heard of R: or I: -- I'm not Italian :)
Will do!
-
It defeats the purpose: you don't know where you are within the conversation. There was a thread in these forums that inspired this.
So we can keep option 2, where the user knows exactly where he/she is within the convesation, or replace it by option 4 or 5, where:
- the user knows exactly where he/she is within the conversation
- outside a conversation (single message), the user knows exactly where he/she is within the global message list (by swiping, all those messages can be reached).
See my new slide
It would make sense to have the logic as follows:
A: Message 2/3 in conversation (position: 2/6)
B: Message 4/6 or Message in position 4/6
where "position" is the position in the messages list with all conversations collapsed.
So, it is "#2" in your latest figure (-dev1.7)
I agree, that it is hard to choose clear wording here.
In any case, - the comma in #2 of your picture should be removed (and also in #5).
And it is definitely not "rank" in English. Row, Position are fine.
-
Re: comma
I know it is not in the app.
I was just pointing out why your description could be more confusing than necessary. ;)
-
I'm trying to avoid having to use words other than "message" and "conversation" (which are already in the app's vocabulary).
Those hints would properly need to be:
"Message list item X/Y (you know, the items in the message list you just came from, or would see if you used the Back button)"
"Oh, and item here may refer to a single message or a message group, expanded or not"
"The current message is grouped with some other message (not to be confused with "items" in the preceding paragraph"
"And within those grouped messages, this one is #Z / out of #Q total"
.... but that seems just a little too verbose :)