AquaMail Forum

English - Android => Development builds => Topic started by: Kostya Vasilyev on June 05, 2017, 05:16:10 pm

Title: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 05, 2017, 05:16:10 pm
https://www.aqua-mail.com/download/AquaMail-market-1.11.0-425-dev-f0e85aeba320.apk

https://www.aqua-mail.com/download/AquaMail-market-1.11.0-426-dev-93f4a93eca15.apk

---

+ Text to speech improvements, please post feedback here:

https://www.aqua-mail.com/forum/index.php?topic=5776.0

+ Merged fix for "some messages not reflowing" from 1.10

---

+ Улучшения / исправления в голосовых уведомлениях, тема для обратной связи:

https://www.aqua-mail.com/forum/index.php?topic=5776.0

+ Исправление из 1.10 "отсутствие переноса текста в некоторых сообщениях"
Title: Re: Version 1.11.0-425-dev - "work in progress", not in Google Play
Post by: nadir husain on June 05, 2017, 05:25:02 pm
@Kostya - you,sir are a rock star!!
Title: Re: Version 1.11.0-425-dev - "work in progress", not in Google Play
Post by: com5585 on June 05, 2017, 06:01:52 pm
При попытке входа в пункт меню "Уведомления о сообщениях" постоянно происходит сбой программы. Moto Z, сток 7.0.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 05, 2017, 09:34:56 pm
Re: При попытке входа в пункт меню "Уведомления о сообщениях" постоянно происходит сбой программы. Moto Z, сток 7.0.

Спасибо за лог. Исправлено (я надеюсь) в сборке 426.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: com5585 on June 05, 2017, 09:58:31 pm
Re: При попытке входа в пункт меню "Уведомления о сообщениях" постоянно происходит сбой программы. Moto Z, сток 7.0.

Спасибо за лог. Исправлено (я надеюсь) в сборке 426.

Сборка 426, всё работает. Спасибо за fix!☺️
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Fcasoli on June 05, 2017, 11:04:10 pm
Hi, not now but it is long time I noted this behavior.

I have the option to adapt the message text but when I zoom in the text is not adapted to the screen width and I must move right and left to read.

What reason of that, have I lost some settings?

Starting view
(https://uploads.tapatalk-cdn.com/20170605/cf08cd5a1829c81967d1cfdf53cf2b48.jpg)

Zooming without automatic adapter to screen width

(https://uploads.tapatalk-cdn.com/20170605/7e674a10eb34d2322cbfb3f2f4038698.jpg)
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 06, 2017, 12:00:30 am
Re: I have the option to adapt the message text but when I zoom in the text is not adapted to the screen width and I must move right and left to read.

This was a change we intentionally made in 1.9 (released about a month ago).

There were a few discussions here about it - including the reason why.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Fcasoli on June 06, 2017, 12:12:59 am
Re: I have the option to adapt the message text but when I zoom in the text is not adapted to the screen width and I must move right and left to read.

This was a change we intentionally made in 1.9 (released about a month ago).

There were a few discussions here about it - including the reason why.
Awesome, it is the option required in a lot of email clients, by tons of users, very nice to know is a decision and not a bug, could be nice to have the possibility to select to have or not...

Thanks
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Philip on June 06, 2017, 12:36:09 am
Awesome, it is the option required in a lot of email clients, by tons of users, very nice to know is a decision and not a bug, could be nice to have the possibility to select to have or not...
Yes. Very many users (myself included) were very unhappy that this feature had been removed (and also that the removal had been deliberately excluded from the Release Notes - leading to support requests like yours). Search for "reflow on resize" or "reflow on zoom in" if you want to see the previous discussion.

Given that the code already exists, I am (slightly) hopeful that it might be restored - even as an option - in a future version of AquaMail.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Fcasoli on June 06, 2017, 12:50:45 am
Awesome, it is the option required in a lot of email clients, by tons of users, very nice to know is a decision and not a bug, could be nice to have the possibility to select to have or not...
Yes. Very many users (myself included) were very unhappy that this feature had been removed (and also that the removal had been deliberately excluded from the Release Notes - leading to support requests like yours). Search for "reflow on resize" or "reflow on zoom in" if you want to see the previous discussion.

Given that the code already exists, I am (slightly) hopeful that it might be restored - even as an option - in a future version of AquaMail.
In Aquamail there are a lot of options, one more is not a problem, in my opinion
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: StR on June 06, 2017, 03:28:16 am
Awesome, it is the option required in a lot of email clients, by tons of users, very nice to know is a decision and not a bug, could be nice to have the possibility to select to have or not...

MobiSystems was "monitoring" the issue (still is? or was that a euphemism for ...?):
https://www.aqua-mail.com/forum/index.php?topic=5658.msg34379#msg34379

I am not holding my breath here... I've explained (https://www.aqua-mail.com/forum/index.php?topic=5658.msg34517#msg34517) why the current status quo would fill OK for MobiSystem support:
Quote
Well, actually, I think I know the reason, and understand MobiSystem's hesitation to re-enable it: it might be hard to explain to many "unsuspecting" users that if they experience the jump, they need to disable reflow, and vice versa. And if it is not re-enabled, the new users will not know that they could've had something better. So, there might be less headache to deal with if MobiSystems withstand this initial wave of complaints.
However, a carefully worded option item can work; setting its default value to the "new" behavior: no reflow/reduced jump [with a warning: "changing this may create focus jumping when you are zooming"] would reduce potential for the complaints from the users.

And one can tell that the flow of complaints here has already settled down: users who are unhappy about the change gave up and  either have found a way to live with it or moved to a different app. That was predictable from the beginning.

For me, personally (and I consider myself an Aquamail evangelist of a sort), this is probably the biggest grunge in the MobiSystems era of Aquamail so far. And it's probably not be even the lack/presence of this important feature itself (there have been several ones that I've been unhappy about), but rather the seemingly hypocritical way of how it was handled.

But alas, I said, I am done wasting my time on this issue. It was only the fact that I saw yet another long-term Aquamail user who was adversely affected by this change, that got me to rehash my bitterness about this issue.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 06, 2017, 09:23:03 pm
Quote
For me, personally (and I consider myself an Aquamail evangelist of a sort), this is probably the biggest grunge in the MobiSystems era of Aquamail so far. And it's probably not be even the lack/presence of this important feature itself (there have been several ones that I've been unhappy about), but rather the seemingly hypocritical way of how it was handled.

I've made changes prior to "the mobisystems era" that were like that -- and sometimes provided a setting to make the change more "palatable" but sometimes didn't.

And so it is just a matter of being practical, and not in itself new with MS.

Not to mention that "other apps" also get updates which are not liked by every user and every time.

But yes, at this time, the complaints have died down, and there were not many to being with (far fewer than, say, requests for a "pure black window background in the dark theme" in 1.9).

And so - we're not seeing a reason right now to resurrect the wrapping.

Related to that, version 1.10 had an unintentional regression (in auto-fit, text reflow) which I did fix and post a couple of days ago - even though this is in "the mobisystems era" (and on a Sunday no less).
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Geezer on June 06, 2017, 10:52:24 pm
What the heck, why not drag out this reflow topic a little further.  But forgive me if I'm simply rehashing it in doing so.

For me the message text window is no different than, say, a PDF reader.  Whether on the desktop or a mobile device, if you resize the window the text reflows.  In the case of AM, you may want to increase the font size to see it more clearly (in poor light, for example) or you may want to reduce the size to place more text on the screen.  In either case you expect (and want) the text to reflow so you can continue reading.

Like many others, I have a difficult time understanding why the new operation simply "zooms in place".  Perhaps it makes sense if there is an image that you want to view more closely and you don't want to chase it down the screen as it scrolls out of view.  (Actually, I wish I could find a list of benefits to this change in this forum somewhere).

Regardless, it seems to me that the old behavior was what was expected a majority of the time and functioned correctly.  But that's just my opinion.  And as far as the complaints dying down (and I haven't checked Play Store reviews), the complainer would have to meet several criteria before it reaches this forum.  They would have to:

- Occasionally zoom message text and be sufficiently unhappy about the new behavior
- Want to continue using AM
- Be aware of the AM forum
- Subscribe to the forum
- Feel strongly enough to comment here

That would seem to filter out some number of "complainers".
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 06, 2017, 11:23:34 pm
Re: For me the message text window is no different than, say, a PDF reader.  Whether on the desktop or a mobile device, if you resize the window the text reflows.

I just tried a PDF file in a PDF reader (just happened to have one laying around) -- and it did not reflow.

This is the trouble with metaphors -- they break.

---

I am 1000% in support of reflow -- if it did not cause scroll jumps.

But it did, and we got complaints.

But it did, and my attempts at fixing it did not succeed (and btw, WebView version 58 and newer acts different from earlier versions, just to give you an idea of how hard this is).

So we had to pick a compromise - and we did.

And as I also wrote previously

- in 2017, a lot of messages are optimized for mobile and do not need any "fitting" or "scrolling". We also did some work on that in 1.10 and with good results.

- other messages can be auto-fitted, again no need to scroll.

- but yet others cannot be auto-fitted because they use a rigid markup structure based on tables. Wish there was a magic way to fix those too, but there just isn't (without severely breaking their layout).

Re: the complainer would have to meet several criteria before it reaches this forum

The forum, yes, requires registration to post.

But that's not the only option.

It's really easy to post a complaint in Google Play or to tap the "email support" link there.

So even though you're right that posting on this forum requires some effort which can be an obstacle -- this cannot be said about Play comments or emails to our support account.

Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Philip on June 07, 2017, 01:05:23 am
I just tried a PDF file in a PDF reader (just happened to have one laying around) -- and it did not reflow.
Then, with respect, I would suggest that you have used a bad PDF reader (or perhaps a non-standard PDF file). If you had used a good - or better still, an excellent - PDF reader, then it would have reflowed. It would be sad if you want to benchmark AquaMail against poor quality applications, rather than against best-in-class.

- in 2017, a lot of messages are optimized for mobile and do not need any "fitting" or "scrolling". We also did some work on that in 1.10 and with good results.

- other messages can be auto-fitted, again no need to scroll.

- but yet others cannot be auto-fitted because they use a rigid markup structure based on tables. Wish there was a magic way to fix those too, but there just isn't (without severely breaking their layout).
I don't know who is writing or receiving these "modern" emails, because it certainly isn't me.

And (for me) images and tables in an email are almost always an irrelevance - it's the text that I am interested in, and I want to be easily able to make it a size that I can read, without having to scroll horizontally.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 07, 2017, 01:19:06 am
Re: you have used a bad PDF reader

I used Google Chrome and the first PDF file I just happened to have around (an invoice).

But - the assertion was that with PDF's "Whether on the desktop or a mobile device, if you resize the window the text reflows" not "sometimes" or "often" or "depending on the PDF reader or the file".

I just checked this file in three (3) PDF viewers on my phone. Same thing, no reflow on zoom.

Re: I don't know who is writing or receiving these "modern" emails, because it certainly isn't me.

I receive "modern" emails all the time - notifications from Amazon, Google, PayPal, WordPress, etc.

And then plain text messages and most formatted messages are fine too.

---

But to come back full circle yet again - if it were possible to "reflow on zoom" *and* avoid scroll jumps, we would do it. But I couldn't make it work so we had to decide which way to compromise.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Geezer on June 07, 2017, 02:05:05 am
Kostya wrote:
I used Google Chrome and the first PDF file I just happened to have around (an invoice).


When I stated "...if you resize the window the text reflows" I meant pure text (words) that are not part of a table (e.g. an invoice) or other structured formatting.  I did not clarify that.  I can't conceive of a PDF viewer that does not reflow simple text.  However, perhaps plain text/words is too simple to use as an example of the wider formatting issues involved.

Regardless, I've read your explanation and I think I understand the issues.  Thanks for (once again) for responding.
Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: StR on June 07, 2017, 03:08:00 am
@Kostya:
I have this feature (most likely a weakness) that I always hope that people who I consider smart, are making a bad decision simply because of an imperfect communication; and if one can help them understanding the situation as others see it, these smart people would do "The Right Thing (tm)". While sometimes I've had success, I've also been proven wrong in some cases. But I keep trying unless I get convinced that it's totally hopeless.
Your today's responses gave me a hint that you might be just not hearing a couple of arguments behind the noise about non-essential here technical details (PDFs, HTMLs, other decisions, other apps, other companies, etc.)
Hence, I will try this one more time from a different perspective.

I am 1000% in support of reflow -- if it did not cause scroll jumps.

But it did, and we got complaints.

But it did, and my attempts at fixing it did not succeed (and btw, WebView version 58 and newer acts different from earlier versions, just to give you an idea of how hard this is).

So we had to pick a compromise - and we did.

Kostya, in all this saga, you've been saying that killing the reflow-after-zoom was necessary: it was an "either-or" choice.
You have never commented on why the 3rd option, the solution suggested by several long-term users would be a problem:
Make an option: "reflow after zoom": "disable"[DEFAULT, improves zooming experience]   /    "enable"(may cause problems with zooming on images).

Setting its default value to the "new" behavior: no reflow/reduced jump [with a warning: "changing this may create focus jumping when you are zooming"] would reduce potential for the complaints from the users who might try enabling it.
That would be a win-win situation for the both groups of users (and will not create much of a problem for the support).

Quote
And as I also wrote previously

- in 2017, a lot of messages are optimized for mobile and do not need any "fitting" or "scrolling". We also did some work on that in 1.10 and with good results.

- other messages can be auto-fitted, again no need to scroll.

- but yet others cannot be auto-fitted because they use a rigid markup structure based on tables. Wish there was a magic way to fix those too, but there just isn't (without severely breaking their layout).

Kostya, sorry, but you keep repeating these arguments about this and that type of messages, while they are mostly irrelevant to the main point (that you seem to be missing) of people who are asking for REflow-after-zoom: It is an accessibility issue, when people need to zoom on the text due to the vision limitation. (And, unfortunately, no, font increase is not an acceptable universal solution, as I explained before). And once you zoom, re-flow is essential for these people. Even if it was imperfect, it was important; it was something people have been relying on heavily.


The fact that these two simple arguments have been mostly ignored, while the decisions were made on the basis of "who was louder" is the most disappointing. And that's why I called (rather strongly, I admit) the way this issue was handled -- seemingly hypocritical: the essential usability needs of users have been ignored by hiding behind an argument of making it better for other users, while totally ignoring a possibility of making everybody happy (except those who want the old dark theme).

Title: Re: Version 1.11.0-426-dev - "work in progress", not in Google Play
Post by: Kostya Vasilyev on June 07, 2017, 04:08:45 pm
Quote
I have this feature (most likely a weakness) that I always hope that people who I consider smart, are making a bad decision simply because of an imperfect communication; and if one can help them understanding the situation as others see it, these smart people would do "The Right Thing (tm)".

I used to think like that too -- and one time it was in a situation that was a direct threat on my life.

Quote
Kostya, in all this saga, you've been saying that killing the reflow-after-zoom was necessary: it was an "either-or" choice.
You have never commented on why the 3rd option, the solution suggested by several long-term users would be a problem:
Make an option: "reflow after zoom": "disable"[DEFAULT, improves zooming experience]   /    "enable"(may cause problems with zooming on images).

Because "just make a setting" isn't always a good solution - every new setting (and at this point it would be "new", since it's already been removed) adds complexity to the code and also can be an issue for support (does the user have option X enabled or not).

It's like this:

(https://imgs.xkcd.com/comics/workflow.png)

And yes a "saga" it really does seem to be.