Open GoogleCodeExporter opened 9 years ago
I am currently not analyzing any threading from the device but let Gmail figure
that
out by person_id, i.e. sender/recipient of the message. To break that apart by
relatedness in time would require quite a lot of work (to develop and for the
device).
What could be done fairly "easily" is clumping together messages within fixed
date
buckets, but still separated by sender/recipient. For example all messages
from/to
Alice from 8am-10am would be in one clump, from 10am-12pm in another. Even if
you
received messages at 9:59am and 10:01am from Alice.
Original comment by chstu...@gmail.com
on 26 Jan 2009 at 6:14
Original comment by chstu...@gmail.com
on 26 Jan 2009 at 6:18
After I posted this, I thought about the implementation. It would definitely
require
a bit of background processing, e.g., a database in the background mapping each
SMS
to a "grouping key." That would just be too much work. Besides, I don't even
think
the G1 can handle something like that without coming to a crawl. Oh well. We
should
urge Google to change the messaging module from the ground up to accommodate
this.
Original comment by aris.lan...@gmail.com
on 26 Jan 2009 at 6:37
I know NOTHING of the technical issues, but I'd *love* a simple date bucket per
day.
Original comment by erik.jac...@gmail.com
on 27 Nov 2009 at 8:22
I think this would be possible if the date was put in the subject. Since this
would be
same for one day, the messages for that day would be threaded, and the next day
would
start another thread.
If this could work, I think it should be an option to choose in the app rather
than
being the rule for everyone.
Just my thoughts :)
Original comment by ben.mcwh...@gmail.com
on 3 Feb 2010 at 3:35
Original issue reported on code.google.com by
aris.lan...@gmail.com
on 26 Jan 2009 at 5:45