[RWP] And the Reaper access wiki is live

[indigo]

That would be great of you Chris.
Most titles and content are self explanatory, either emails or snips 
from emails, as various problems came up.
I have notes with solutions to problems, and some with stated problems 
as yet unresolved, which I don't think hurts us to know about, since 
we'll be in the same boat when we get to that particular area of 
learning Reaper.
I  will begin gathering my notes together, zip them up and post them 
from SendSpace.
That way, they can be used raw, edited, ordered, thrown away, provide 
some belly laughs, whatever, and maybe even answer somebody's questions.
Thanks,
Indigo L

On 3/25/2012 8:41 AM, Chris Nestrud wrote:
> Getting content in the wiki is the important part. Others can organize
> or clean it up later.
>
> If you can zip up the files, I should be able to use your titles and
> convert them into PMWiki format. They can then be sent to Kerry who can
> drop them in the Wiki's location for data. They will then be on the wiki
> and should show up on the Site.AllRecentChanges page.
>
> If there really are hundreds of files, that would at least save you the
> trouble of repeatedly pasting little files in little edit boxes.
>
> Same goes for anyone else with a large number of text notes in separate
> files, provided they have titles or descriptive filenames.
>
> On 3/25/2012 7:22 AM, indigo wrote:
>> Kerry, I've been keeping my hundreds of notes and tips on running
>> ReaAccess as .txt text files, or .rtf files, with titles that mean
>> something to me, and hopefully others.
>> I'll try some basic getting started infos and learn how it goes with the
>> mark up language.
>> But, if I just don't have the time to post them in this exact markup
>> format, and still have time to make music, and take part in my family
>> life, I don't know what I'can do.
>> My tiny bit of energy is stretched very thin as it is.
>> I have been looking at Reaper and ReaAccess with Jaws, NVDA and
>> Window-Eyes, and I find there are places I don't comprehend how to get a
>> few of the basic things done in Jaws or NVDA.
>> For Example, When configuring one's midi interface, the word Enabled
>> must appear after the name of the midi interface.
>> Now I know very well how to get Enabled to appear while on Window-Eyes,
>> but I can't make out how it's done with Jaws or NVDA.
>> I'll put in my little procedure that works for Window-Eyes at that basic
>> configuration instance; and someone better at operating Jaws will need
>> to provide the details on how it's done in Jaws.
>> All you Jaws experts are running Reaper, so you must know how you got
>> your midi interface enabled, right?
>> Other than that single midi device configuration situation, I don't find
>> significant differences in what Jaws, Window-Eyes or NVDA sees, at least
>> with NVDA's tab key and arrows, though I can't get enough information
>> from NVDA because it doesn't have Jaws and Wineyes-style PC cursor
>> screen information available at the number pad.
>> And yet, Patrick Perdue uses NVDA exclusively in Reaper, and we have
>> System Access users as well.
>> So, I guess I'm saying that I had no idea wiki entries would be so
>> exacting, but I'll try, but if I can't get my entries in the wiki as
>> neat and in the exact format required, and expressed for all
>> screenreaders, and still manage to find time to make some music, play
>> with my dog, and the rest of life, I may need to zip up all my notes on
>> running Reaper and send them to someone who has more wiki talents to
>> post them than I do
>> Or, I'll post them zipped on SendSpace, and insert a link in our wiki,
>> or or in pages on a friend's FaceBook, for anyone to use them as they
>> please.
>> Indigo L
>>
>>
>>
>> On 3/25/2012 6:20 AM, Kerry Hoath wrote:
>>> This is a note to say that the Reaper access wiki is live and ready for
>>> people to start editing.
>>>
>>>
>>> It can be found at
>>> http://www.cucat.org/reacwiki
>>> The edit password is reaper in lowercase and just as soon as I figure
>>> out how to create a page with this information I'll link to the
>>> passwored page.
>>>
>>> Editing is relatively easy, here is a really quick summary but you
>>> really should read the basic editing guide.
>>>
>>> Lines that start with spaces like this are pre-formatted text and will
>>> not be wrapped.
>>> Note you'll need to read by character or set punctuation to most/all to
>>> see the following:
>>> !heading this is a level 1
>>> !!this is a level 2
>>> !!!this is a level 3
>>>
>>> * this is the first item in an unordered list
>>> * this is the second item.
>>>
>>> # this is item 1 in a numbered list
>>> # This is item 2 in a numbered list.
>>>
>>> double backslash \\ will insert a line break.
>>> A bare URL like
>>> http://www.reaccess.com/ will link off to another website.
>>>
>>> [[http://www.reaccess.com/|reaccess homepage]]
>>> puts the link in and changes the link text.
>>>
>>> To create a new page put something in like
>>> [[Getting started with Reaper]]
>>> a questionmark will show up next to the link after save, hit enter to
>>> create the new page.
>>>
>>> Please put your names on edits or I'll have to make author names
>>> manditory.
>>>
>>> I hope we all find this resource useful. If this really takes off I'm
>>> happy to either buy a domain or change pointers to the wiki or tar it up
>>> for someone else to host.
>>>
>>> I want to add links to Cavi's reaper presentations if people think that
>>> belongs on the wiki, CAVI did 3 presentations on how to get started with
>>> Reaper 3.77 and reaccess.
>>>
>>> regards, Kerry.
>>>
>>> _______________________________________________
>>> 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
>