Re: Grand Advanced Stylesheet Project (GASP)

[Urs Liska]

Am 19.01.2015 um 04:41 schrieb Kieren MacMillan:
> Hi Urs (et al.),
>
> > Maybe having it as a semi-official library would be more manageable?
> Sure… whatever works best!

I think it would be easier to develop such a thing as a library, as a 
work in progress. When including it into LilyPond it the stakes are 
quite high, and this might be a reason for never getting to that point ...
Having it separately from LilyPond source code will also make it easier 
to welcome contributors. With a fork/pull request based tool like Github 
contributors don't even need to be granted push access to the 
repository, so actually anybody can suggest additions. I'd see the 
attitude towards reviewing contributions stricter than with openLilyLib 
which is basically something where about anything can be added to, but 
definitely mroe easy-going than the LilyPond review process.

All this makes me suggest keeping it separately.

> > A suggestion regarding the interface: how about
> >     \include "stylesheets/choral/octavo.ily”
> Okay.
>
> > There could be a hierarchy of different building blocks, and the actual include 
> > file would pick from them what it needs and optionally add more items to the 
> > stylesheet.
> Hmmm… I’d need to see it in action to see if that could really Do The Right 
> Thing™. Let’s say we want the following choral stylesheets: octavo, letter in 
> portrait orientation, and letter in landscape orientation. What’s the 
> hierarchy, and how does the stylesheet put it all together? Then, when I want 
> to make a stylesheet that mimics (e.g.) Barenreiter's octavo choral scores, how 
> does that work?
>
> Obviously, this is related to my (our) Henle-Beethoven stylesheet discussions 
> from last year. We’d want the library to include piano solo stylesheets for 
> letter in both portrait and landscape orientations, and concert (9x12) in both 
> orientations. Then if we wanted to extend to a Henle house style, and narrow 
> that to “Henle piano folios ca. 1950” (with Abraham’s awesome new font, of 
> course!), how does that work?

Yes, this is related, and I'm sorry that we didn't continue to discuss 
it then.
Well, I don't have "the" solution to pull out of my hat either.
What I'm thinking about is a two-part hierarchy: one directory with 
building blocks and one with to-be-included style sheets.
The building blocks are organized by type:

/bb/
- paper/
  - a4.ily
  - letter.ily
  - concert.ily
  - landscape.ily
  - ...
- score/
  - piano.ily
  - orchestra.ily
  - voice-piano.ily
  - ...
- publisher/
  - henle.ily
  - barenreiter.ily
  - openlilylib-modern.ily
  - openlilylib-classical.ily
  - ...
/stylesheets/
  - piano/
    - a4/
      - henle.ily
  - ...

A concrete stylesheet like /stylesheets/piano/a4/henle.ily will include 
anything from the  building blocks and add any necessary additional 
tweaks. The actual hierarchy of the stylesheets directory structure is 
something that should be discussed in advance, and for that I think we 
should collect ideas what *kinds* of stylesheets we'd expect to 
want/have and what combinations should be possible (note: not all 
"fields" of the "matrix" have to be implemented).

Just my ideas.
Urs


> Looking forward to making this a reality!
>
> Thanks,
> Kieren.
> _______________________
>
> Kieren MacMillan, composer
> www:  <http://www.kierenmacmillan.info>
> email:  address@hidden