[RWP] Reaper feature Request forum .

Fri May 30 15:11:23 EDT 2014

Hi guys
What kind of demo is needed victor, can you explain more abit?
I think that making REAPER accessible in both platforms is a very hard 
thing to do, and by that i mean it consumes lots and lots of times which 
the developers won't  spend on.....
Am i wrong on this?

On 5/30/2014 11:31 PM, Scott Chesworth wrote:
> Vic,
>
> The journey on Windows might not be as long as it seems. Have you
> tried exploring the TCP with a mouse instead of relying solely on
> keyboard actions? An absolute ton of stuff is read out which didn't
> used to be the case. It makes me think that the majority of the grunt
> work for at least that area of UI has been done, but I don't know
> enough about it to know whether that's actually the case.
>
> Scott
>
> On 5/30/14, Victor Tsaran <vtsaran at gmail.com> wrote:
>> Hello all.
>> I concur with Scott. I believe Reaper developers have enough information to
>> make their software accessible. There are several issues:
>> 1. We need to separate Windows Reaper discussion from the Mac one.
>> 2. Rather than sending them the documentation on how to implement
>> accessibility, we need to record a video demo showcasing accessibility
>> problems with Reaper. This, of course, needs to be done with or without
>> ReAccess so as not to confuse them.
>> 3. After this we need to help them prioritize the must-have from
>> nice-to-have features. For someone who has little knowledge on accessibility
>> and the needs of screen reader users just the word itself can be very
>> daunting.
>>
>> We as a community have to decide whether we want to make the vanilla version
>> of Reaper accessible or use ReaAccess as a starting point for accessibility.
>> If we were to go the first route, it would be a lot of work, especially on
>> Windows. They have done some good work on the Mac already.
>>
>> On both operating systems we have the problem that the user is not aware of
>> the results of their actions, e.g. when you mute, solo, arm tracks or
>> perform any other activity.
>> I also feel that Reaper's default keyboard map is just not very friendly for
>> keyboard users.
>>
>> I would be interested to make a demo for Mac OS. Any volunteers for
>> Windows?
>>
>> Best,
>> Vic
>>
>> *** *** ***
>> Find me on Twitter http://www.twitter.com/vick08
>>
>>
>>> On May 30, 2014, at 4:05 AM, Scott Chesworth <scottchesworth at gmail.com>
>>> wrote:
>>>
>>> Vic has given them links to pretty much everything they need, other
>>> than a bit of time and focus obviously, because you can't link to
>>> those :)
>>>
>>> A few years ago when the last big piece of native accessibility
>>> movement occurred, the situation was similar. The actual code changes
>>> came all of a sudden over a period of a couple of days max following a
>>> long period of semi-engaged interest. That time, Justin was bouncing
>>> emails off of someone who has a good knowledge of Windows
>>> accessibility development as he tweaked. I know of a couple people who
>>> have the relevant knowledge who have been in sporadic email contact
>>> with him over the years, so it doesn't seem unreasonable to think
>>> we'll see a repeat of the pattern at some point. Last time around, it
>>> came just before a major version increment.
>>>
>>> I know it's frustrating to see all this interest and seemingly no
>>> movement, but speaking as someone who emails with plugin developers
>>> weekly if not more often, the facts that Cockos are A) having any
>>> public input into the discussion at all and B) made at least one
>>> conscious effort to improve accessibility in the past which was
>>> documented in the changelogs are both very positive compared to what I
>>> usually see.
>>>
>>> Scott
>>>
>>>> On 5/30/14, Hadi Rezaee <hadirezaei at gmx.com> wrote:
>>>> Hey scott,
>>>>  From what i see, REAPER developers won't move forward in accessibility
>>>> until someone from community steps up and actually tells them what is
>>>> needed to do.
>>>> And i believe there is literally noone technical about accessibility who
>>>> is enthusiastic enough to engage the developpers.
>>>>
>>>>
>>>>> On 5/30/2014 2:38 PM, Scott Chesworth wrote:
>>>>> There's already a FR for this with over a hundred votes, a discussion
>>>>> thread linked in the top post and Justin from Cockos semi-engaged in
>>>>> the discussion. Link:
>>>>> http://forum.cockos.com/project.php?issueid=3888
>>>>>
>>>>> Sorry to seem like I'm putting a downer on the effort, but you'd
>>>>> probably be better voting there and bumping the discussion thread with
>>>>> enthusiasm or helpful info rather than starting a fresh. The numbers
>>>>> and level of interest we're looking at are still fairly small fry, so
>>>>> it's important to keep them all in one place.
>>>>>
>>>>> I honestly think our turn will come around eventually with these
>>>>> chaps, they just haven't found the time to learn about how to
>>>>> implement what we're asking for yet. Keep the discussion active, keep
>>>>> it fresh in their minds, and they'll get to it eventually.
>>>>>
>>>>> Scott
>>>>>
>>>>>> On 5/30/14, sidney <sidnesizer at outlook.com> wrote:
>>>>>>      that works for me, jim.
>>>>>>
>>>>>> sidnesizer is available for all your audio production needs.   to make
>>>>>> this
>>>>>> possible, call me at 1876-931-1800, 281-2801, 533-6883, or from my
>>>>>> internet
>>>>>> phone call 786-342-2960.
>>>>>> you can also e-mail me by using:  sidnesizer at outlook.com,
>>>>>> sidnesizer at gmail.com or sidneythorpe59 at gmail.com;
>>>>>> or, if you prefer, use skype, with sidnesizer as my skype name.
>>>>>> we can talk.
>>>>>>
>>>>>>
>>>>>> From: Jim Noseworthy
>>>>>> Sent: Thursday, May 29, 2014 4:49 PM
>>>>>> To: rwp at reaaccess.com
>>>>>> Subject: [RWP] Reaper feature Request forum .
>>>>>>
>>>>>>
>>>>>> Hello Gang:
>>>>>>
>>>>>> I opened a thread in the Feature Request forum asking that a future
>>>>>> update
>>>>>> be dedicated to accessibility issues.
>>>>>>
>>>>>> What we will require, is someone who really understands the
>>>>>> accessibility
>>>>>> issues and can highlight, in a clear and concise manor, those issues
>>>>>> that
>>>>>> we
>>>>>> need to be addressed.
>>>>>>
>>>>>> How about it gang?
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --------------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> RWP mailing list
>>>>>> RWP at reaaccess.com
>>>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>>> _______________________________________________
>>>>> RWP mailing list
>>>>> RWP at reaaccess.com
>>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at reaaccess.com
>>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com