Hi! On Mon, May 28, 2007 at 02:59:30PM +0200, Tim Janik wrote: > the idea/need for a comprehensive manual or tutorial for beast > has been brought up a few of times recently: > http://mail.gnome.org/archives/beast/2007-May/msg00000.html > http://mail.gnome.org/archives/beast/2007-May/msg00003.html > > unfortunately i am fairly busy with other projects (rapicorn, > glib/gtk+ which also have resource shortages), so i probably > won't have the time to write a full manual any time soon. > > thus, i'd like to suggest to start this as a community effort, > e.g. people from the beast mailing list could speak up if they > have interest/resources to help with tutorial creation. > > a..c) [...]
d) I'd like to add that there is also the "Glossary" in the Wiki already: http://beast.gtk.org/wiki:BeastGlossary It right now only explains two terms, as derived from IRC questions: http://beast.gtk.org/wiki:InstrumentOutput http://beast.gtk.org/wiki:PostProcessor However, it may be a good idea for those that are working on the manual to try to capture more of the BEAST terminology there. By choosing suitable Wiki words for each term relevant in thinking about BEAST, we could create a useful resource. Of course, where it is not clear what is to say about something, core developers like me can provide info or edit as needed. There is of course a technical problem with terms that don't become wiki words easily, like Track, Part, Song and so on, but I think it is worth the extra markup required to make glossary entries for them, too. See http://beast.gtk.org/wiki:ExtendedWikiMarkup (i.e. they should be written as [Track] in the wiki). Cu... Stefan -- Stefan Westerfeld, Hamburg/Germany, http://space.twc.de/~stefan _______________________________________________ beast mailing list [email protected] http://mail.gnome.org/mailman/listinfo/beast
