Cobra Tutorial

[pchapin]

I'm thinking of trying to write a tutorial on Cobra. This is a rather presumptuous thing for me to do since I don't really know the language right now. Of course, I would use writing a tutorial as a mechanism for learning the language (in fact, that, together with potentially contributing something useful to the Cobra community, are my main motivations for doing it). What this means is that it will be a while before the document would be worth talking about. However, on the assumption that it might grow up some day into something suitable for public consumption I'm wondering in what format the document should be written (or if it even matters). I could, of course, produce a PDF in a number of different ways, but would straight HTML be better? Is there some other format that I should think about using?

To offer some reassurance that I'm not a complete hack, let me say that I do work in education and have a lot of experience writing materials like this. See for example http://vortex.cis.vtc.edu/pcc/prog/BOK/C. (I notice that my office machine appears to be down right now. Hrumph. I'll have to fix that tomorrow).

[jonathandavid]

IMO a tutorial would be a very welcome contribution.

[Charles]

A more complete tutorial would be welcome. I strongly suggest the wiki at http://cobra-language.com/trac/cobra/wiki with page names like TutorialIntro, TutorialFoo, TutorialBar, etc. There would be a TutorialIndex listing the pages in order. At the bottom of each page would be 3 navigation links:

Next: TutorialFoo
Previous: TutorialBar
Index: TutorialIndex

By putting this on the wiki, more than one person can contribute and minor corrections can easily be made at any time.

I'd also recommend that people evaluate their own writing skills and contribute to the tutorial if they have good writing skills or limit themselves to feedback if they do not.

[pchapin]

A more complete tutorial would be welcome. I strongly suggest the wiki at http://cobra-language.com/trac/cobra/wiki with page names like TutorialIntro, TutorialFoo, TutorialBar, etc.

Okay, that sounds like a good idea. Thanks for the suggestion!