Hi Adam<br><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Michael - excellent suggestion. FLOSS Manuals seems to have a facility<br>
for including code easily. Has anyone tried putting ChucK code in to<br>
see if it barfs on it?<br></blockquote><div><br>I asked Adam at FLOSS Manuals whether there was a sandbox there. There is a partial one, a manual that can be used for testing things:<br><a href="http://www.flossmanuals.net/bin/view/Testing" target="_blank">http://www.flossmanuals.net/bin/view/Testing</a><br>
<br>Unfortunately you can't publish it, to test exactly how it will appear to the public, or to export it as a PDF. <br>I entered some ChucK code into a <pre> element. That seemed to work fine in the preview. Though probably needs more testing (for instance, do long lines inside a <pre> element automatically wrap in PDF export? my suspicion is that they might not).<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Tomasz - I was referring to sections as being farther up the layout<br>
tree than chapters. There are sections and subsections of chapters<br>
that seem to do quite well in FLOSS manuals. What I am looking for is<br>
a way to make a split in the manual between our tutorials and the<br>
reference section. It isn't a pressing issue.<br></blockquote><div><br>Right, I see. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
So, it looks like we have some CSS people who can look at the issues<br>
here. FLOSS manuals looks terrible. Fortunately we have full access to<br>
the CSS. I would love if someone were to spend some time with this<br>
during the Christmas break. I know that Ge spent some time tweaking<br>
the website layout. I wouldn't want to throw away too much of that<br>
work. The colours and general typesetting make reading the ChucK<br>
reference webpages very easy on the eyes.<br></blockquote><div><br>You mean <a href="http://chuck.cs.princeton.edu/">http://chuck.cs.princeton.edu/</a> right?<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The more I think about it the more I am strongly leaning towards FLOSS<br>
manuals. The group we have assembled will work most efficiently that<br>
way. If we migrate away from this after the sprint then that is ok,<br>
but I would like to get as many people involved as possible to start<br>
out.<br></blockquote><div><br>I agree. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Other collaboration possibilities: We use Wave or some sort of chat to<br>
talk to each other while we use some other method for building the<br>
docs. Right now they are in LaTeX and we could go with that system. I<br>
would be happy to accept changes and ideas all day and then just put<br>
them into the current system.<br></blockquote><div><br>Right. Though not a pressing concern at the momoent, in a wave chat with Kassen we both noticed unworkable lag when the number of 'blips' (messages) got large. So unless that gets a fix soon, a simpler chat system might be more appropriate, when we get to that stage.<br>
</div><div> <br>Tomasz<br></div></div>