How is it you are not going to get screwed to the wall for making this? Shane
On Wed, Nov 5, 2014 at 5:19 PM, Mark Veltzer <[email protected]> wrote: > The idea is that the end user who builds the book can select transposition > (say to trumpet), which tunes to put into the book, turn lyrics on and off, > turn rehersal markings on and off, tunes have several versions (of which you > can select one), uniformity of presentation (which is taken away from the > individual tunes and centralized), font, indexes of various kinds (I already > have index by poet and by composer) and more. > > I still need to develop a GUI for this but you are supposed to be able to do > this without editing any lilypond and using a simple GUI. > > In addition I can render any tune individually (ofcourse). > > This is all possible with just working with one big (28,000 line) file. Or > just lilypond snipplets and includes, with no templating. It's just harder. > Much harder. > > I could have done this with guile I expect but I find the language not > appealing. Python is much more to my taste. > > Cheers, > Mark > > On Thu, Nov 6, 2014 at 12:05 AM, Federico Bruni <[email protected]> wrote: >> >> Il giorno mer 5 nov 2014 alle 20:39, Mark Veltzer <[email protected]> >> ha scritto: >> >> you can now see the results of the project on: >> >> http://veltzer.github.io/openbook >> >> >> Thanks for the link. >> >> Honestly, it's not what I was expecting. It's basically a PDF embedded in >> a simple HTML page. The PDF may be created much more easily using only ly >> files. Why using the mako template then? >> What I'm missing? >> > > > _______________________________________________ > lilypond-user mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-user > _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
