Daniel Brockman <[EMAIL PROTECTED]> writes: > Then, in the Track Lines node, something like > > ``Depending on the type, a track line is a line with > either a `bongo-file-name' or a `bongo-action' property,'' > > and so on. Nodes like this could describe Bongo functions and > variables not normally interesting to users, and so the manual > would have an index that would be very useful to developers.
Okay. I think that might be useful, having the behind-the-scenes concepts explained, but I'm not so sure about including it in the manual. Do you think a text file or web page is enough for this? I'm guessing this will not be written in the near future; so perhaps instead, in the meantime, you can record small pieces that you want to write about in some file. >> Do you think it can be coordinated now, or will it take >> time to get going? > > I don't know what the holdup would be. I'm currently a bit > starved for time, so don't expect any grunt work contributions > from me at least until the end of the week. > > I don't see any problem with just grabbing a topic and > writing about it. I think Romain has some collaborative > manual writing experience so he might disagree. It wouldn't be fun if we duplicate efforts, so I think a writer should post a notice when work is in progress. Other than that, maybe having the outline in texinfo in a repo would help spark some creativity. _______________________________________________ bongo-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bongo-devel
