While I appreciate the videos, I would like to add my voice to the chorus -I rely on documentation in learning instruments and i find that , even for boutique intruments, , lack of or poor documentation can often harm the product well beyond the developers expectation. Other than a complete os I think that documentation that is adequate is the single most important thing to me and many others I know. If an outline can be produced, I am a drafter and can edit some narratives as time permits 9 after i get my machine of course) On Thu, May 5, 2011 at 9:41 AM, tmoravan <tmoravan@yahoo.com> wrote: > > > Colin - being a sw developer myself, I know that documentation is often the > last thing on the list and the most loathesome of tasks. > > I have a proposal - would it be possible to provide a general outline of a > document in some standard format (MS Word for example), along with pointers > to existing P3 docs (if applicable), and then have the community create the > user manual with you doing the proofing and corrections if we document a > feature incorrectly? > > Also - if there was an easy way to do screen captures on the Cirklon, that > would go a long way to making the doc more usable. > > The way I see it, people could sign up for a feature or menu and document > it extensively and then you could stitch the pieces together and we might > then have a useful document quicker than if the burden fell solely on you. > > Thoughts? > > > [Non-text portions of this message have been removed]
Message
Re: [analogue-sequencer] eventual Cirklon documentation
2011-05-05 by Mark Morton
Attachments
- No local attachments were found for this message.