[icon-discuss] Re: email suggestions
- From: "Derek Roberts" <bigd.vi.guy@xxxxxxxxx>
- To: <valiant8086@xxxxxxxxxxx>
- Date: Sun, 10 May 2009 20:23:48 -0400
Hi,
Just a comment. about the eloquence pausing in totally weird places, it's
because the part where it pauses is a newline.
HTH.
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
----- Original Message -----
From: Valiant8086
To: icon-discuss@xxxxxxxxxxxxx
Sent: Sunday, May 10, 2009 12:03 AM
Subject: [icon-discuss] email suggestions
I've been using the email a lot lately, and I have some things that I
think need to be impliminted, and I know most of these have been entioned
already.
1. show that unread messages are unred. It's not possible to know this
without already figuring it out for yourself right now.
2. Remove pauses in reading of subjects etc. Reading lots of emails takes
a while and any speech speed up we can get will help. One problem I have
with the braille plus is totally unrelated to just email but speech pauses
are too long. It seems to make it harder to speed eloquence up and still be
able to understand it too because with speech stopping sometimes in very
wierd places but always for too long I tend to get knocked out of the flow
of listening and all that, so eloquence has to be set to a slower speed,
about 90, than I can run jaws. My question can we take more than half the
length of the pauses on punctuation and between different strings sent to
eloquence out? I've been noticing that sometimes it pauses where there is
nothing that should cause it to pause, no punctuation what so ever, and it
really doesn't make sense for it to pause there in the sentence either, and
eloquence ran on other platforms, such as the pacmate and jaws and all
those, don't seem to pause until they hit punctuation.
3. support for grouping messages by conversation. This one speeds up the
reading of email so much it is amazing. It should be possible to open a list
of messages from one conversation by hitting right arrow. If it is a
conversation that I've arrowed down or up to, it should say collapsed and
then the headers that typically show.
"Collapse unread valiant8086 on braille plus messagesubject sampledate"
4. I think it would be nice if the braille plus didn't say "deleted" when
I delete a message, but it seems logical that it does say that. Having it
not say it speeds things up by about a second every time I delete a message,
when going through and deleting 300 messages this turns into a lot of
precious seconds *smile*.
5. I think maybe it shouldn't say "message" when I open a message. I just
pressed enter on it and I know it's going to be a message that appears.
6. I totally agree with it not reading outt the headers when I open a
message from the list, but it might be helpful to read the from and subject
headers when deleting an open message and being dumped into another message,
unless that message has the same subject as the last one then it's subject
could be skipped..
7. when transfering messages, the list should be updated while the
transfer is going on just like windows clients do. So when a new message is
downloaded, it appears in the list at the end, or inside a conversation and
it can be accessed right then and there while other messages are still being
downloaded. This solves two problems in one shot, the first problem is you
don't have to wait until transfer is complete, second is it gets rid of the
chance for losing messages if something goes wrong before the braille plus
gets the messages put into the list, giving a chance for messages to be
downloaded, deleted from the server but not added to the list and thus
completely lost, something that has been discussed on this list quite a bit.
8. When I replied to a message on a freelists mailing list earlier today
with my braille plus, the message that was my reply, when I downloaded it on
my netbook, registered as being in a different thread and it didn't get
grouped in a conversation with the orriginal message to which I replied when
using the braille plus. Basically, I think the braille plus is doing
something perhaps incorrectly with the headers or at least in a way that's
causing this to happen. I noticed this happening on other lists and now I
think I know
why my computer doesn't appear to be able to detect grouped conversations
properly. Having a fix of some sort so that the braille plus maintains
message headers or does what ever the same way other email clients do so
that they can be recognised by recipient email clients as being replies to
other messages etc
This all sounds like too much to ask for but they are all things that I
already have gotten used to on a regular computer so I thought maybe the
braille plus could look into similar functionality, especially since we're
about to lose the best and simplest email client on the windows platform
with the coming of windows 7. The braille plus's email client is pretty good
and I think it could be improved to pretty much be the best one in the
specifically blind accessible mobile PDA market.
Btw, I always said braille plus because that's what I have but I obviously
mean icon as well.
Other related posts:
