Hi Aaron,

See answers below:

Sam, I really think you need a new hobby. <grin>

And just what do you think my hobby's are?

Honestly. I don't know how many times we have to say it over, and over, and over, and over, and over, but compared to the other issues on our plate, browse mode was not number one. Yes, not being able to access some sites is at the least annoying, and at the most, downright occupationally critical. The majority of Window-Eyes users fall somewhere in between.

I didn't ask you to say it again ... why do you think I am asking for that?

And, you might want to sit down for this one, believe it or not, users in the United States aren't the only people using Window-Eyes. I know, I know. It's hard for an American to imagine he or she isn't the top priority in the world. <grin>

Are you suggesting that browse mode is only an American issue?
I sure hope not!
Nor did I ever even suggest that American's are more important than another world wide users.


Window-Eyes users span the entire globe. We're in every hemisphere, and on every continent. And the needs of overseas users were not being met, so we needed to put them first for once, and work on enhancing Braille, localization, and a few other issues. That was a major undertaking.


I am not sure why you seem to think American and world wide users are at odds!
We all need access!

We also had to get 64-bit support out. That was far more of a must for people's jobs than browse mode.

We agree there and I pushed as much as others to get 64bit support.
You haven't heard any thing but, positive info from me on the latest we!

It wasn't just to shut Don H up.

I have said nothing about Don and I certainly didn't tell any one to shut up!

We also
had to make sure that support for Windows 7 was up to par with everything else, and that also included the 64-bit version of Windows 7.

I couldn't agree more and great job on that!

We enhanced our edit box support to provide 100% text accuracy, but in the beginnings, that brought out a lot of regressions that we had to go through.

I think using direct info not an msaa buffer is great progress and I support you guys in this!

There were scripting issues that were slated for 7.0, but
didn't make it. We couldn't keep pushing those back, because scripting needs to stay competitive.

I agree scripting needs to stay competitive but, so does browse mode don't you think so?

Did you know that we had almost 30 private betas trying to work this stuff out before we could get something to the public? No, of course you don't,

No I didn't know about the 30 beta's and I am not even sure what that has to do with this discussion.

because you're too busy coming up with conspiracy theories as to
why things weren't resolved as you thought they should have been.

What are you talking about?\
conspiracy theories!
WordWeb Pro
1. A secret agreement between two or more people to perform an unlawful act
2. A plot to carry out some harmful or illegal act (especially a political plot) 3. A group of conspirators banded together to achieve some harmful or illegal purpose

Where did I even suggest anything like the above?

That > sounds more harsh than I intend it to sound; I'm mostly being facetious.


You can sound as harsh as you like but, I actually was defending you guys this time even though you may not have realized it as you jump to an unnecessary defence.

But I want to make my point clear: when we sit down and work out the roadmap for the next version of Window-Eyes, we don't ask our lawyers what they think. We don't have shareholders to consult. We don't have a bottom line that needs to be met. We do what we feel needs to be done for the majority of our (worldwide) users.

The above is just not true.
If you don't have a bottom line ... you will go out of business!
Second ... then if you don't need to consult the lawyers ... tell us the status / story of the law suit?
I don't think you are leveling with us here!
I wouldn't be so hard on you but, I was defending you and you maike me out to spending my time thinking up tails about you guys!

I know the idea of Window-Eyes development being shrouded in the secrecy of unknown legal proceedings and denials of being able to comment on what's going on is much more titillating. But it's also make believe.

You are not in legal battels over browse mode and placed markers?
Do we the users no about the legal proceedings? Or are they unknown ... witch you call make believe?
Are you in a law suit?
Are you able to comment on the proceedings with the jaws guys?

Secret development? I just have been asking about browse mode since before 6.0 and can't get any info but, to say ... post what ever the latest version is.

Call it what you will ... when there is a vacuum people wonder and do there best to guess!
Maybe if you answer the questions above ... we will not need to guess?
Sam


Aaron

On 6/27/2009 12:53 PM, Sam bushman wrote:
I just had an important thought, ... browse mode / place markers are at
the heart of the problems with freedom ... !
Well browse mode is also the part gw has not been willing to work on!
I am only speaking for my self and not involved in any issues with any
law suits etc.
So I have the opinion that gw will not do much with browse mode ... 'til
they get clear of that stuff.
maybe I am wrong but, why lay your hand out to the opposition in the
middle of all that?
The best course of action would be to lay low ... finish that law suit
stuff with a strong hand ... then when clear ... have in the wings a
killer update that blows away the compitition?
Just a thought.

    Sam
    ----- Original Message -----
    *From:* Don H <mailto:[email protected]>
    *To:* gwmicro <mailto:[email protected]>
    *Sent:* Saturday, June 27, 2009 10:28 AM
    *Subject:* Re: Browse Mode - a suggestion/question

    Hopefully now with the release of 7.1 GW will be working full speed
    ahead to resolve browse mode issues. Don't think we will get a date
    out of GW for the release of version 8 but if I were a betting man I
    would say around the end of the year.

        ----- Original Message -----
        *From:* David <mailto:[email protected]>
        *To:* WE English mailing list <mailto:[email protected]>
        *Sent:* Saturday, June 27, 2009 11:19 AM
        *Subject:* Browse Mode - a suggestion/question

        For quite a while now, Browse mode, has basically stayed the
        same. For all of what I know, it might have been this way
        forever - I did get in touch with WE in version 6.0.
        To claim, there has been no updates to browse mode, would be
        totally out of range. It's enough to just mention the
        placemarker functions, implemented with WE7. Still these have
        been to some extend, what we could discribe as Minor updates or
        changes.
        For at least a year, GW staff has told us, there will be a major
        update, or even a rebuild of the whole, browse mode -
        sometime... NO! This is no complaining message, I just try to
        sum up, the facts, as far as my knowledge goes. And I do
        understand the reason for the REBUILD of the Browse Mode, and
        that there is nothing in stone yet. That is actually what all of
        this message is all about...
        The problem, as it is by date, and has been for all the past, is
        that Brose Mode is a part of the basic WE code. This means, that
        ONLY GW staff has access to it, and ONLY they can change it.
        They are few, and have limited resources. They also have to make
        priorities when comes to what features to update, and maintain.
        But the WEB, is a quite dynamic place. It changes often, and it
        does so, OVER NIGHT. Go to your favorite webpage today,
        everything is fine, open it tomorrow, and you are stuck - the
        webmaster had the joky idea in his head last night, to change
        one tiny piece of code, and you are helplessly left behind. You
        go to the WE mailing list, and sigh out your heart, and is told
        that somewhere down the line, someone down the staff, will do
        something down the code... And meanwhile? When we first were
        told that plans were for an update to Browse Mode, last year,
        the web had this and that, that was inaccessible. If we look one
        year, two years, or whatever ahead, to get the rebuild, the web
        will have changed dramtically, and the whole process will have
        to be repeated.
        OK, enough for the summing up. Here is my suggestion: Up till
        WE6.1, the WE code made up the whole WE software, and that was
        what you got, and what you had to stick to. From WE7, the
        software has become FAR more dynamic, by entering into the
        scripting world. This gives us big opportunites, when comes to
        keeping the software UP-TO-DATE, and running even under brand
        new circumstances.
        GW Staff:
        Why not simply remove the browse Mode from the basic code, and
        make it all into a script???
        Scripting the Browse Mode, would give several conveniences.
        First of all, not only GW staff would have access to it, meaning
        that if they don't have time to update, others might get the
        chance to jump in and give a hand. Secondly, the update would be
        far quicker and more easily done. Third, the users could benefit
        from the updates, even if they don't have the money to run and
        buy a newer version of WE, at least to some extend (most scripts
        can, for instance, be run as well under WE7, WE7.01, and WE7.1).
        Fourth, scripting would open up for features, that might not be
        possible, easily, to fit into the basic code.
        How well would this way of doing things work? Well, I did use
        another screen reader - back a few years ago - the German
        Blindows. They had done a similar solution, having no browse
        mode implemented in the screen reader itself, but bunddled it
        with a scripted software named WebFormator. The scripted browse
        mode, simply kicked in, whenever IE was opened, just like the
        Browse Mode of WE does. In practical, daily, use, the user might
        not even notice the difference. But when comes to the frequency,
        and time needed, to get out updates, everyone would benefit.
        ALLRIGHT, you all might state - and I guess this is the first
        reply we will get from staff members - but this will have to be
        in a later version of WE, sometime down the years.... !!! NO !!!
        Should be possible to get this done, already, with no new
        version of WE. A script could be out, that simply OVERRIDES the
        'built-in' Browse Mode, that is implemented in WE as per date.
        Later on, yes, go ahead and remove the built-in Browse Mode, but
        the script could be out far sooner than a new version of WE. A
        bit of a job to built such a script? OH, YES! But what a job to
        rebuilt the built-in code in WE? And when will next version of
        WE come out? Again, no complaint, but let's face the fact. Few
        things that the users put their screen reader on to accomplish,
        is any more dynamically, and rapidly changing, than namely the
        WEB. We've got scripts for far more stabile and non-dynamic
        tasks than that, already. As time goes by, more and more of the
        web will rapidly change. If GW have to rebuild their code for
        all of these changes, they will soon find they have to run a
        whole staff on just that one task. Putting it out as a script,
        will take away a good portion of that pressure, from their
        shoulders, as stated in the four points above.
        Well, what do you listers, think about this?

        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 [email protected] 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
        [email protected] 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 [email protected] 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
    [email protected] 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 [email protected] 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
[email protected] 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 [email protected] 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
[email protected] 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 [email protected] 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
[email protected] and include leave gw-info in the body of the message.

Reply via email to