Re: Changing stem stencil

[Urs Liska]

Am 28.02.2014 18:56, schrieb Peter Bjuhr:
> On 2014-02-28 18:36, Urs Liska wrote:
> > Now that I've seen this works:
> > It would be extremely cool if you could write a blog post about how
> > one can create custom stuff using Bravura like this. I think there are
> > some possible uses for that (e.g. clusters). Noeck's posts clearly
> > point in that direction already, but if we had another post showing
> > how you can actually _do_ it ...
>
> Yes, that's a good idea. I think this has potential! I'll be happy to
> write a post about it!

That'd be great. Just come back to us when you're likely to get started. 
I think this actually has _two_ sides: accessing SMuFL glyphs on the one 
hand (as a practical way to extend Lily's own capabilities) and the 
process of replacing a stencil. I think it would be really good to have 
more tutorial like material about stuff like this to encourage people to 
experiment in these directions.

> > And you should consider making this a snippet for our repo.
>
> I got an idea to turn this into a more generic function for changing the
> staff stencil, with the glyph to be used as an argument.
>
> Another question is where would I put the snippet?

I think it should be in the notation-snippets folder. Please have a look 
and see how it relates to the existing overriding-stencils snippet.

> Is it ok if a snippet
> is dependent of another snippet in the library or should all smufl stuff
> be in the same folder?

It's OK to have such dependencies - as long as they're documented.
The repo/library is designed to be "includable". That means it is 
intended to be in LilyPond's include path (as I wrote in my earlier 
post). So basically when adding something to the library you can assume 
that the whole library is available. You can include another file either 
relatively from your snippet file or - and I'd prefer that - with its 
complete path from the library root (which makes your snippet more 
robust in case it should be moved to another directory).
You should clearly state this dependency, something like this: "I assume 
that the snippet is included as part of the library. If not you have to 
get file X and ensure that the following \include points to the right 
place."

Urs

> > Best
> > Urs
>
> Best
> Peter
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user


--
Urs Liska
www.openlilylib.org