Am Montag, 3. März 2008 schrieben Sie: > this is quite impressive. I wish such a tool already existed when I > started writing my opera :) > > May I suggest to add parts of it to the LSR, as "stylesheets" like Nicolas' > one? http://lsr.dsi.unimi.it/LSR/Item?id=368
Well, I don't like the idea of keeping whole packages in LSR, which is particularly meant for "Snippets". LSR is simply not suited as a package repository, where you need to keep track of versions, updates, good documentation, FAQ's, installation instructions, etc. Furthermore, I'm releasing the parts that I wrote under the GPL (mainly because I don't want to give up all rights (yet?)), so putting everything into the LSR is also not possible due to licensing issues. About putting parts into the LSR: The first 350 lines are the code for score/staff/group generation, so they really belong together and are the core of the package. They also require some score-settings (e.g. to display staff group brackets also for a single staff -- which is is already in LSR http://lsr.dsi.unimi.it/LSR/Item?id=201). I've already submitted the cue note functions to the LSR: http://lsr.dsi.unimi.it/LSR/Item?id=388 Similarly with the "sempre pp/ff" dynamic alignment: http://lsr.dsi.unimi.it/LSR/Item?id=393 Filtering articulations from Voice II: http://lsr.dsi.unimi.it/LSR/Item?id=372 Rest combination: http://lsr.dsi.unimi.it/LSR/Item?id=336 > I'm looking forward to have more snippets like this one (even if, like > in this very case, we have to keep the code commented out until the > LSR is upgraded). This way perhaps it's more visible, more useful -- > and quite an excellent demonstration of LilyPond potential power :) Again, I don't think the LSR should be a package repository (in particular, I don't think that Nicolas' package should be there, either). For the (still very small number of) packages it would be better to have a separate section on the homepage, which proper documentation. In particular, the LSR does allow for exactly one source file and one output file, so a demonstration of features or a tutorial ar not possible. Look at Nicolas' style sheet. I think it's really a shame that no example of the fantastic output is given, but instead only some lilypond code, which gives only an impression what you have to write, but not what the output will be (title page, toc, header style, etc). Cheers, Reinhold -- ------------------------------------------------------------------ Reinhold Kainhofer, Vienna University of Technology, Austria email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * K Desktop Environment, http://www.kde.org, KOrganizer maintainer * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/ _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
