[RWP] reaaccess could stand an update.

[Derek Lane]

is there a way to de-compile  a dll?  If so, a spinnoff could be developed, 
and I'm sure several of us would be willing to test.
----- Original Message ----- 
From: "Roy Shtupler" <shtupler at 013.net>
To: "Reapers Without Peepers" <rwp at reaaccess.com>
Sent: Friday, September 03, 2010 8:45 PM
Subject: Re: [RWP] reaaccess could stand an update.


> I'm a programmer , thus can look into the source code  it becomes 
> available.
> cheers
> Roy.when
> www.soundclick.com/tzackeek
> ----- Original Message ----- 
> From: "Derek Lane" <derek at pdaudio.net>
> To: "Reapers Without Peepers" <rwp at reaaccess.com>
> Sent: Saturday, September 04, 2010 12:10 AM
> Subject: Re: [RWP] reaaccess could stand an update.
>
>
>> Well, at least one thing is interesting in our exchanges, actually 2.
>> The first is that my arguments slightly change and develop along with 
>> reaper.  *smiles*
>> Finally, your valid point has more and more evidence to the continuing 
>> interest in reaper.
>> We'll keep this up as long as necessary I'm sure.
>> If this one developer has given up the project, it'd be nice to have the 
>> source available.
>> I don't know who on this list is a programmer, but given the work flow of 
>> most modern development tools, isn't all the work already done?
>> Wouldn't it be the case that the only major update necessary is to send 
>> more from the API to the code already in place which communicates with 
>> screen readers?
>> ----- Original Message ----- 
>> From: "Scott Chesworth" <scottchesworth at gmail.com>
>> To: "Reapers Without Peepers" <rwp at reaaccess.com>
>> Sent: Friday, September 03, 2010 2:51 PM
>> Subject: Re: [RWP] reaaccess could stand an update.
>>
>>
>>> Hey Derek,
>>>
>>> As always, very valid thoughts. As humble users, we're still stuck in
>>> this tricky situation where any and all future updates to the existing
>>> ReaAccess code depend on one developer. Hopefully Jinseng will chime
>>> in here if there's any news about progress.
>>>
>>> I know, everytime you post along these lines I reply along these
>>> lines. I'm sure we're equally as frustrated seeing a plugin with this
>>> much potential stagnating. I guess these replies are just one more
>>> electronic hand being raised in agreement.
>>>
>>> Scott
>>>
>>> On 9/3/10, Derek Lane <derek at pdaudio.net> wrote:
>>>> Hi everyone.
>>>> Though I still find reaper an amazingly useful daw, especially for my 
>>>> needs,
>>>> I think it important that the developers consider updating reaaccess to
>>>> utilize the additions made in the API.
>>>> The release notes for the latest version of reaper contain a section of
>>>> various automation, help, and other tidbits of information, now 
>>>> contained
>>>> within the API.
>>>> I think that the reaaccess plugin would do well to take advantage of 
>>>> these
>>>> improvements.
>>>> Also, would it be possible to develop a virtual control serfice which 
>>>> would
>>>> then give us access to any automatable parameter in any given plugin or
>>>> combination of plugins?
>>>> Just some thoughts.
>>>
>>> _______________________________________________
>>> 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
>