<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I know that Ivan has seemingly given up, but does anyone know anyone that can contact him in any way? If he doesn't wish to continue the work, then he shouldn't have an objection to the code being made available.<div><br></div><div>I volunteer to put the source in to one of the open source project management communities like Source Forge. I'm also willing to contribute time to work out the window handle mismatches that block context menus in Reaper 4. I'll also be glad to work on getting the speech output support to connect to VoiceOver, so there can be a Mac version.</div><div><br></div><div>If the ReaAccess code is gone forever, though, then that is probably the end of Reaper access. Rewriting ReaAccess from scratch would be time-consuming just to reach parody with the old ReaAccess. That's a lot of work for nothing new. I also doubt that there is a lot of cash in it. Boring work that pays nothing is not likely to happen, sadly.</div><div><br></div><div>When I brought up the thread over a year ago about the Mac port, and requesting that Ivan release the source code if he wasn't planning to make ReaAccess a commercial product at some point, I recall that a certain someone called me a communist for arguing that important information be shared/backed up through being available to the community, rather than being held by a single person. I guess recent events have proved my point, though. I remember being a system admin back in college, and the administration foolishly trusted root access to a single person, rather than having procedures to regulate access. When that person died of a heart attack one night, taking his passwords and other important info with him, the administration had lots of opportunities in the following weeks and months to reflect on that lesson. It wasn't my last experience with people taking important shit to the grave. Death and hard drive crashes are similar. They often happen suddenly, when you least suspect, you're rarely prepared, and you always lose data. I hope Ivan just got bored, and isn't, in fact, dead. He seems to have disappeared, though, and disenchantment or busy work schedules aren't usually so abrupt and total of a communication loss.</div><div><br></div><div>Bryan</div><div><br></div><div><div><div>On Jan 11, 2012, at 9:43 PM, Dave wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div>
<font size="3">Hello,<br><br>
Guess that depends upon the number of Blind users that use Reaper at this
time. <br><br>
As usual, there are about 12 of us, and even if we numbered 112, that
number would hardly register when compared with the Sighted customer base
numbers. <br><br>
The Blind users groups, for just about any software, just do not have the
numbers needed to really grab the attention of what ever Developer, of
what ever software package. <br><br>
Seems like the Blind community has to find a yet to be discovered
program, that is very good, and has one starving Developer, that will do
almost anything to start getting a Cash Flow from his product.
<br><br>
Only then do we get Accessibility issues addressed. Then after the
guy does a few updates, that incorporate a few good changes for the
Screen Reader crowd, not enough buy his program, because so many screen
reader users are broke, or are looking for a Free update, or just
outright steal the software, no matter what taste it might leave in the
struggling Developers mouth. <br><br>
Not sure why Ivan, the guy that created Reaaccess, has chosen to
stop his own efforts. I was hopeful, but looks like
that hope has diminished along with the other previous projects to
give full access to a quality Recording program. <br><br>
If Mr. Ivan would have really given us a solid, Total access, I would
have paid him $200 for such an ability. $200 is about
my top end limit, unless I suddenly wake up with a lot more
extra cash in my pockets. <br><br>
I paid a lot of my own money for my computer, and for the Screen Reader
that allows me to have limited access to most programs. When
the Screen Reader software costs more than my computer, well, I
just don't care for it. Seems a bit odd, unless most sales are paid
for by the Government, which is sure to raise the pricing of most
anything. Perhaps it is just me that has the wrong idea
of what fair market pricing should be? <br><br>
Sorry, I am off on another rant. Sorry about the Reaper program not
getting any further access, at least it looks that way for the short
term, if I were optimistic. <br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br>
</font><blockquote type="cite" class="cite" cite="x-msg://341/"><font size="3">Hello,<br>
I guess we may have to put up with no further ReaAccess versions, at<br>
least this is what I learn from recent discussions on this list.<br>
I sent an email to Cockos a couple of months ago asking for their
plans<br>
on direct accessibility support. They indicated that they have<br>
screenreader support on their list but - like with so many SW projects
-<br>
this list may be long.<br>
Nevertheless, I think the only way to support accessibility in the
long<br>
run will be to integrate it directly into the Reaper code.<br>
On Windows systems there are many ways to do it, Microsoft UI
Automation<br>
beeing probably the most promissing at the moment.<br>
Exposing all UI elements to UIA would allow all modern screenreaders
to<br>
work without any extra plugins or auxiliary technology.<br>
Reaper already allows all important actions to be bound to key
strokes<br>
and so this should not create a problem.<br>
I wonder if a feature request signed by as many active visually
impaired<br>
Reaper users as possible could help in bringing this task a bit
closer<br>
to the top of Cockos's todo list.<br>
Their reply to my email left me with the impression that they were
not<br>
even aware of ReaAccess and what it does.<br>
On the other hand screenreader compatibility could help them boost
their<br>
sales, especially for public institutions who are bound to provide<br>
accessible solutions.<br><br>
What do you guys think?<br>
/Roland<br><br>
<br>
_______________________________________________<br>
RWP mailing list<br>
<a href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</a><br>
<a href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com" eudora="autourl">
http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</a></font>
</blockquote></div>
_______________________________________________<br>RWP mailing list<br><a href="mailto:RWP@reaaccess.com">RWP@reaaccess.com</a><br><a href="http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com">http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com</a><br></blockquote></div><br></div></body></html>