From:

 Corange@PSC.STATE.FL.US

Subject:

 RE: window eyes support for HTML 5 canvas element

Date:

 Thu, May 28, 2009 1:58:30 pm

I think as more functionality becomes implemented via scripts, this will
become possible to do.

until then however, you have no idea how much work went into this fix
Aaron mentioned. it may be the result of months of development,
primarily aimed at other things. before they release a new reader, it
has to be tested, as a whole product. if it were modularized that could
be different, but except for changes to .set files, it's not.

they only have a few guys working on this, and taking time to test and
release a service pack takes time away from the main development effort.

this is another reason to hope for more functionality coming from
scripts; it allows us, the consumers, to actually help with development,
as well as modularizing the product.

Chip





------------------------------

Chip Orange
Database Administrator
Florida Public Service Commission

Chip.Orange@psc.state.fl.us
(850) 413-6314

(Any opinions expressed are solely those of the author and do not
necessarily reflect those of the Florida Public Service Commission.)

-----Original Message-----
From: Sam bushman [mailto:sam@libertyroundtable.com]

Sent: Thursday, May 28, 2009 1:45 PM
To: aaron@gwmicro.com; David

Cc: gw-info@gwmicro.com
Subject: Re: window eyes support for HTML 5 canvas element

Hi all,

I am heavily involed in the development of software programs so I do

understand the issues here.

I understand that gw did there very best to create a solution for the
browsing of the web (best info at the time) and the landscape

has changed so
fast out from under them that they need to re-think /

re-write a solution
going forward.

I respect that ... no problem.

However, I would hope we could get service packs ...

microsoft and most
companies do this all the time that would address some of

these tiny issues
that seem so large at the time.

Example:

Aaron says that 7.1 has the main problem I am having fixed.

So Aaron and others say don't press for the next version
until it's ready.

Fine, we agree again.
But, if they have this fixed couldn't I have had it with ease

for who knows
how long now if we had service packs for issues like this?

I realize that we can't do a service pack for every thing but, most

companies do issue service packs that bundle several fixes in
to one SP.

I do this for my own software as well.

They would say yes and we do to, just look at 7.01 ... Again we agree!

But, if we7.1 is taking longer and longer (again as it should
be to get it

right) what about 7.02 with several more things fixed?

thanks
Sam

----- Original Message -----

From: "Aaron Smith"
To: "David"

Cc: "Sam bushman" ;
Sent: Thursday, May 28, 2009 11:34 AM

Subject: Re: window eyes support for HTML 5 canvas element

> Ideally, yes. In reality, no. This type of functionality is

built into the
> core of browse mode, and is one of the main reasons why we

are gutting it,
> and starting from scratch.

>
> Aaron

>
> On 5/28/2009 1:28 PM, David wrote:

>> OK, I see your point. Then my next question is: Could we have
>> implemented a feature, that gave the user the chance to

Turn on/off this
>> recalculating of data? That if it is turned off, the user

will be put
>> back in palce, no matter how much the site has been

updated? And if it
>> is on, then, it goes on like you describe, recalculating

all the time.
>> ----- Original Message ----- From: "Aaron Smith"

>> To: "David"

>> Cc: "Sam bushman" ;

>> Sent: Thursday, May 28, 2009 7:10 PM
>> Subject: Re: window eyes support for HTML 5 canvas element

>>
>>

>>> On 5/28/2009 12:52 PM, David wrote:
>>>> Try for instance, go to EBay, then do a search for

whatever product,
>>>> and

>>>> scroll down the list. When you find one that you want -
let's say item

>>>> number 10 on the list - and then press enter, you are
taken to the ad

>>>> of
>>>> that product. So far, Yes, everything is perfect. BUT!

Now, try to
>>>> press

>>>> either the Backspace key, or the ALT-LEFT ARROW, to go
back to the

>>>> prior
>>>> page, and see what will happen.

>>>
>>> I'm not surprised by this, and, to be honest, it's

actually by design
>>> in the current implementation of browse mode. Here's what happens:

>>> when you visit a web page, Window-Eyes calculates a value based on
>>> data about the page (number of lines, cursor position, etc.), and

>>> stores that value in memory. If you navigate away from
that page, and

>>> then come back, Window-Eyes will again calculate the
required data,

>>> and if it matches what was stored in memory, you're
placed back on the

>>> line you were on when you left.
>>>

>>> If, however, the data differs at all, even the slightest
bit, you are

>>> placed back at the top of the page. We do this on
purpose; if the data

>>> differs, that means the page has changed and, because we
don't want

>>> you to miss any potentially important information, we put
you back at

>>> the top. In the past, this was the accepted, nay desired,
behavior for

>>> pretty much any page.
>>>

>>> But times have changed. You see, browse mode didn't break; the web
>>> just got busier.

>>>
>>> As today's web pages become more dynamic and fluid, the

values of the
>>> data calculated for a given page often don't match the

values stored
>>> for the same page. Even a single ad changing on a page

can make this
>>> happen. Say you have an ad for apples when you leave the page, but

>>> when you go back, the same ad is for oranges. Even if the
rest of the

>>> content of the page is exactly the same, that's enough to make the
>>> values of the data different.

>>>
>>> The page could change even before you leave it. Sometimes

there are
>>> dynamic areas that update with latest news, latest wheels

and deals,
>>> updating weather information, etc., that would cause the

value of the
>>> page to be different were you to leave it then come back again.

>>>
>>> What you are experiencing is an ever changing web landscape that

>>> browse mode is not designed for. Browse mode hasn't
gotten worse, and

>>> it didn't break. Instead, web pages have begun to change
more often

>>> than in the past. And this feature of browse mode, created in an
>>> attempt to provide the most relevant content with every

visit to the
>>> page, has unfortunately become an aggravating hassle.

>>>
>>> Aaron

>>>
>>> --

>>> To insure that you receive proper support, please include all past
>>> correspondence (where applicable), and any relevant information

>>> pertinent to your situation when submitting a problem
report to the GW

>>> Micro Technical Support Team.
>>>

>>> Aaron Smith
>>> GW Micro

>>> Phone: 260/489-3671
>>> Fax: 260/489-2608

>>> WWW: http://www.gwmicro.com
>>> FTP: ftp://ftp.gwmicro.com

>>> Technical Support & Web Development
>>>

>>> If you reply to this message it will be delivered to the original
>>> sender only. If your reply would benefit others on the list and

>>> your message is related to GW Micro, then please consider sending
>>> your message to gw-info@gwmicro.com so the entire list

will receive it.
>>>

>>> All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo,

>>> and can be searched through and sorted using the search
>>> form at the bottom of the page.

>>> If you wish to unsubscribe from this list, send a message to
>>> listserv@gwmicro.com and include leave gw-info in the body of the

>>> message.
>>>

>>
>> If you reply to this message it will be delivered to the original

>> sender only. If your reply would benefit others on the list and
>> your message is related to GW Micro, then please consider sending

>> your message to gw-info@gwmicro.com so the entire list
will receive it.

>>
>> All GW-Info messages are archived at

http://www.gwmicro.com/gwinfo, and
>> can be searched through and sorted using the search

>> form at the bottom of the page.
>> If you wish to unsubscribe from this list, send a message to

>> listserv@gwmicro.com and include leave gw-info in the body of the
>> message.

>>
>

> --
> To insure that you receive proper support, please include all past

> correspondence (where applicable), and any relevant information
> pertinent to your situation when submitting a problem

report to the GW
> Micro Technical Support Team.

>
> Aaron Smith

> GW Micro
> Phone: 260/489-3671

> Fax: 260/489-2608
> WWW: http://www.gwmicro.com

> FTP: ftp://ftp.gwmicro.com
> Technical Support & Web Development

>
> If you reply to this message it will be delivered to the original

> sender only. If your reply would benefit others on the list and
> your message is related to GW Micro, then please consider sending

> your message to gw-info@gwmicro.com so the entire list will
receive it.

>
> All GW-Info messages are archived at

http://www.gwmicro.com/gwinfo, and
> can be searched through and sorted using the search

> form at the bottom of the page.
> If you wish to unsubscribe from this list, send a message to

> listserv@gwmicro.com and include leave gw-info in the body
of the message.

>

If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and

your message is related to GW Micro, then please consider sending
your message to gw-info@gwmicro.com so the entire list will

receive it.

All GW-Info messages are archived at
http://www.gwmicro.com/gwinfo, and can be searched through

and sorted using the search
form at the bottom of the page.

If you wish to unsubscribe from this list, send a message to

listserv@gwmicro.com and include leave gw-info in the body
of the message.

If you reply to this message it will be delivered to the original
sender only. If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to gw-info@gwmicro.com so the entire list will receive it.

All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search
form at the bottom of the page.

If you wish to unsubscribe from this list, send a message to
listserv@gwmicro.com and include leave gw-info in the body
of the message.