AquaMail Forum
English - Android => Development builds => Topic started by: Kostya Vasilyev on July 20, 2014, 02:02:35 am
-
https://www.aqua-mail.com/download/AquaMail-market-1.4.1-46-beta3.apk
https://www.aqua-mail.com/download/AquaMail-market-1.4.1-46-beta3.1.apk
^^^ Updated translations: SK, IT
https://plus.google.com/communities/112921486711044378404
https://play.google.com/apps/testing/org.kman.AquaMail
---
+ Bug fixes in swiping
+ Merged fixes from 1.4.0.46
Published to Google Play as a Beta.
---
+ Исправления в новом коде, жесты в списке сообщений
+ Исправления из "основной" версии 1.4.0.46
Опубликована как Бета в Google Play.
-
Great work as always.
What ever happened to the auto light/dark theme? Really liked that.
-
I'm a Beta fan now!
How can I find the xmt file to translate to italian?
thanks
-
@Fcasoli - I've updated the Italian forum theme with text from the 1.4.1 beta:
http://www.aqua-mail.com/forum/index.php?topic=2216.msg10785#msg10785
In fact, I also updated German, Portuguese, Japanese, and Polish.
-
Testing the Tasker plugin. Limited testing, so far. If I match on sender, it works. If I match on subject, it works. If I match on both sender and subject it does not work. Intentional or oversight? Also, is there any form of wildcard support?
Thank you for supporting Tasker.
Scott
-
>> If I match on both sender and subject it does not work. Intentional or oversight?
Oversight, I'll take a look
>> Also, is there any form of wildcard support?
The from / to / cc fields are matched by substring (so that a trigger for "john@smith.com" matches "John Smith <john@smith.com>")
The default for subject is exact match, but you can do "sub*", "*sub" or "*sub*" where "*" indicate wildcards.
-
Italian is done.
http://www.aqua-mail.com/forum/index.php?topic=2216.msg10793#msg10793
ciao
-
WOW!
-
>> If I match on both sender and subject it does not work. Intentional or oversight?
Oversight, I'll take a look
>> Also, is there any form of wildcard support?
The from / to / cc fields are matched by substring (so that a trigger for "john@smith.com" matches "John Smith <john@smith.com>")
The default for subject is exact match, but you can do "sub*", "*sub" or "*sub*" where "*" indicate wildcards.
I tested again, this time it worked ok. Everything looked like it was matching the first time, but perhaps there was something else I didn't see. I'll continue trying different combinations. As for the matching, that sounds perfect. :-)
Scott
-
Waiting beta 4
-
The default for subject is exact match, but you can do "sub*", "*sub" or "*sub*" where "*" indicate wildcards.
Is this case sensitive? If so, consider treating this like Tasker. All lower case is a case insensitive match. At least one upper case is an exact match. Probably not super important, but would make it consistent within Tasker.
Scott
-
Scott - the matching is in my code, not Tasker's, and it uses a database library (SQLite) to do the actual work. Let's stay with how it is for now, and I can revisit if there are any actual issues.
-
Scott - the matching is in my code, not Tasker's, and it uses a database library (SQLite) to do the actual work. Let's stay with how it is for now, and I can revisit if there are any actual issues.
So, I understand this to mean it is case sensitive, correct? At least that is my experience with it so far. I do realize the matching is in your code. I never meant to imply anything else. It was only a suggestion. In my opinion, a case insensitive match would be a better choice. I'm only trying to understand the nuances of the pattern recognition, so that I can use it effectively.
Scott
-
Actually it should be case-insensitive, at least for US-ASCII (basic English) characters, and it was in my tests...
So please let me know if you're seeing it work otherwise.
One more thing:
The actual matching of messages to event triggers happens once per mail check, a folder or an account.
This means that if there are 10 new messages, and 5 of them match some trigger's conditions, only one event will be generated (for the newest message).
Pent and I discussed how to generate multiple events for this case, he has some ideas, but it has to go into Tasker itself, and he left it for post-4.4.
-
Actually it should be case-insensitive, at least for US-ASCII (basic English) characters, and it was in my tests...
So please let me know if you're seeing it work otherwise.
In fact, I am seeing it as case sensitive for subject matching, hence my inquiry. Other fields appear to be case insensitive, but I haven't tested those as much.
The actual matching of messages to event triggers happens once per mail check...
I suspected as much, good to know it may change in the future.
Scott
-
>> In fact, I am seeing it as case sensitive for subject matching, hence my inquiry
Are you matching against basic English characters -- or Western European chars with umlauts, grave accents, and all that?
In any case, I'll take a look tomorrow.
>> I suspected as much, good to know it may change in the future.
I can change the "batching" from entire account's mail check to per-folder, would that help?
Ultimately, waiting for Pent to implement his idea for the (new) Event API.
-
Are you matching against basic English characters -- or Western European chars with umlauts, grave accents, and all that?
US English
I can change the "batching" from entire account's mail check to per-folder, would that help?
No, not necessary. I currently use a pop account, not imap, so everything comes in to inbox regardless.
Thanks.
Scott
-
@Scott -- you were completely right about case sensitive Subject matching -- when going for exact match (no "*" wildcards).
I just fixed it, will be included in the next Beta update.
-
When I swipe to search, I get many different results, so my question. Is does it search by subject, sender, receiver or any of the above. What is the search criteria. Thanks
-
I just fixed it, will be included in the next Beta update.
Very good. Thanks.
Scott
-
Ok thanks. Dear. Paris, I think if contact appears any where in header (to, CC, from) it throw results. Thanks
-
Got it, thanks. Bro
-
Just got the beta...love the swiping.
One request... for those of us on POP, could you make one of the swipe choices "Delete immediately," so we could have, for example, swipe left to hide and swipe right to delete?
Thanks! <3AM
-
On search -- all search in Aqua right now is just text search. But the swipe action is wired to search by the sender's exact email.
On POP3 -- right now, the "delete" command in swiping follows the account's delete method (move to deleted / delete now / hide). I'm going to make it possible to optionally wire a swipe action to a specific delete method, not the account's setting.
-
So far completely enjoying the swiping.
Are you planning to implement "swipe to select" feature?
Thanks
-
On POP3 -- right now, the "delete" command in swiping follows the account's delete method (move to deleted / delete now / hide). I'm going to make it possible to optionally wire a swipe action to a specific delete method, not the account's setting.
Done in build 1.4.1-47-beta4:
Kostya you are lightning fast. 8)
My suggestion is an option for "move to folder..." at the settings menue swiping. Equal to "move to spam" but to have a choice to select a specific folder.
-
Hi, would you give more details of "select"?
Hi, I meant selecting (checking) of multiple messages. Currently you need to tap and hold on a message to "select" it.
I think using swipes for that going to provide really comfortable alternative.
-
@midd -- do you mean to connect a specific folder to the icon -- or prompt for a folder after the command is triggered (the way it works now for "move to" chosen from the action bar menu)?
-
Kostya, for my suggestion "move to folder..." for a single message or - as suggested by midd - for multiple messages I meant:
-- prompt for a folder after the command is triggered (the way it works now for "move to" chosen from the action bar menu), then move the message to the selected folder immediatly -- without "cancel" / "ok" buttons --.
-
Without the buttons? In the folder choice dialog?
But how would you open a nested folder then? Or switch from the "recent" folders to the complete folder hierarchy?
-
We won't have a genuine archive function for Gmail, since properly archiving a message there means removing all labels, and this may mean more than just the current folder's.
And Gmail is the mail service / app that made archiving popular, so I'd expect there would be expectations that archiving would work the same as in web mail / native app.
-
>> So you do not need a swipe to command to perform something already existing
But swiping is all about doing same exact things, just differently.
-
Without the buttons? In the folder choice dialog?
But how would you open a nested folder then? Or switch from the "recent" folders to the complete folder hierarchy?
I guess, we don't need the buttons even if there is a nested folder structure.
-- you could open a nested folder just tapping on it
-
@mikeone -- Are you saying that it's ok if a swipe triggered "move to folder" did not have complete access to all the account's folders?
Just the "recent folders" in a flat list?
So basically, a quick way to move a message for the most common case (to a folder that was already used recently) vs. the more elaborate, and complete, UI that's already there?
-
Download dont work...
-
@carsten - which link? how does it "not work" - a "404 not found" or something else?
Telepathy and telekinesis are NOT my middle names.
-
@mikeone -- Are you saying that it's ok if a swipe triggered "move to folder" did not have complete access to all the account's folders?
Just the "recent folders" in a flat list?
So basically, a quick way to move a message for the most common case (to a folder that was already used recently) vs. the more elaborate, and complete, UI that's already there?
Kostya, my thougts are:
If a swipe triggered "move to folder" you should see "all" folders (not even "recent folders") but no subfolders ("hide" subfolders - don't show the complete folder hierarchy in the first instance). Tap on one of these folders will immediatly move the message to this folder - without another tap on a "OK" button.
If the selected folder is a "parent folder" (Gmail: parent label) then a tap on it will open a list of their subfolders (Gmail: sub-labels) but not even "subsubfolders" ... Tap on a subfolder will move the message immediatly...otherwise if the tapped (sub)folder contains subsubfolders it will open a list of these subsubfolders ... and so on...
Hope I expressed it well - and the procedure will be usable ;-)
-- Btw: isn't that the way it works now for "move to" chosen from the action bar menu?
-
@carsten - which link? how does it "not work" - a "404 not found" or something else?
Telepathy and telekinesis are NOT my middle names.
Sorry Kostya ;)
Both links dont work!
(http://img.tapatalk.com/d/14/07/23/evydazar.jpg)
-
@carsten -- looks like Tapatalk doesn't understand https, only http
I thought using https was a good idea :)
Same link using http
http://www.aqua-mail.com/download/AquaMail-market-1.4.1-46-beta3.1.apk
I'll report the issue to Taptalk support
-
On search -- all search in Aqua right now is just text search. But the swipe action is wired to search by the sender's exact email.
On POP3 -- right now, the "delete" command in swiping follows the account's delete method (move to deleted / delete now / hide). I'm going to make it possible to optionally wire a swipe action to a specific delete method, not the account's setting.
Thanks!!!
Update: The new swipe options work perfectly! Love them - totally transforms the way I use AM. Thanks again.
-
Thank you @jimbk!
-
@mikeone -- Are you saying that it's ok if a swipe triggered "move to folder" did not have complete access to all the account's folders?
Just the "recent folders" in a flat list?
So basically, a quick way to move a message for the most common case (to a folder that was already used recently) vs. the more elaborate, and complete, UI that's already there?
Kostya, my thougts are:
If a swipe triggered "move to folder" you should see "all" folders (not even "recent folders") but no subfolders ("hide" subfolders - don't show the complete folder hierarchy in the first instance). Tap on one of these folders will immediatly move the message to this folder - without another tap on a "OK" button.
If the selected folder is a "parent folder" (Gmail: parent label) then a tap on it will open a list of their subfolders (Gmail: sub-labels) but not even "subsubfolders" ... Tap on a subfolder will move the message immediatly...otherwise if the tapped (sub)folder contains subsubfolders it will open a list of these subsubfolders ... and so on...
Hope I expressed it well - and the procedure will be usable ;-)
-- Btw: isn't that the way it works now for "move to" chosen from the action bar menu?
@Kostya
Have you already had the time to review the "move to folder" integration into the swipe feature?
..I know that you have lots of work right now... trust you have this issue in your mind :-)
-
Yes, "move to folder" seems like a good addition.
-
Yes, "move to folder" seems like a good addition.
Kostya,
Thank you for implementation in build 1.4.1-47-beta4.2
...at this time it works equal to the way "move to folder" chosen from the action bar menue.
8)
-
Sure :)
Thanks to Pyler's update checker, we now have "leaked AquaMail versions" :)
I wasn't sure that single-tap-without-confirmation is a good idea (too easy to hit by mistake), so I did this instead:
The "short" folder list in this dialog now remembers most recently chosen folder for each account, and sets it as the initial selection next time.
So once you've moved one message to a particular folder, the same folder will be selected next time, and just hitting OK should be easy enough.
-
>>> show to users on this forum how efficient (and useful) this function is
It is? I'm not a "power user" myself, so looking forward to it -- maybe I'll learn something :)
-
Sure :)
I wasn't sure that single-tap-without-confirmation is a good idea (too easy to hit by mistake), so I did this instead:
The "short" folder list in this dialog now remembers most recently chosen folder for each account, and sets it as the initial selection next time.
So once you've moved one message to a particular folder, the same folder will be selected next time, and just hitting OK should be easy enough.
Yes, I agree with your thoughts (...for the first instance :P)
Without any joke: it works perfectly fine...
-
+1
...for all your suggestions.
-
@Paris Geek -- yes, the "most recently used folder" is not persistent, in fact, it's lost every time the app's process is killed.
I just didn't bother since I didn't know how it would turn out (and be received). Now that it looks like it turned out fairly well, I'll make a note to properly persist the chosen folder.
About third icon - not difficult technically, but not sure how it'll work...
I can only use about half the screen width for total swipe distance (nav drawer on the left, plus some slack so that swiping doesn't turn into a chore)... this means about 160 dp, or 50 dp per icon.
I'll make a note to try it out and see if it can work.
-
@Kostja
Btw: could you please try to implement the feature "select (multiple) messages" before swiping:
...actual there is no possibility for swiping once you have selected one or multiple messages by tap on the contact image :( [unhappy face]
This has the advantage that a user can apply the execution of a command for several messages at the same time. A very powerful method in combination with successive swipe actions like:
- swipe: search by sender - select one/multiple messages (or even "all filtered" messages [another nice feature to implement 8) ] - swipe: move to folder ...or: delete ...or: mark as read ...or: ...
-
@mike - please see my answer here:
http://www.aqua-mail.com/forum/index.php?topic=2596.msg10964#msg10964
-
I quoted my request under
http://www.aqua-mail.com/forum/index.php?topic=2596.msg10959#msg10959
...to continue discussion at one place :-)