Re: OLL/snippets renaming (Re: Broken (?) snippets in openlilylib/snippets)

[Urs Liska]

Hi Paul,

thanks for your thoughts and suggestion.


Am 12.07.2017 um 18:04 schrieb Paul:
> On 07/11/2017 10:35 AM, Urs Liska wrote:
>
>> I would like to rename some directories and move some snippets. In
>> particular the "notation-snippets" and the "input-shorthands" seem
>> somewhat blurred to me. And, with the nicer syntax of \loadModule I
>> would prefer shorter and less redundant names.
>>
>>    \loadModule snippets.lyrics.align-on-vowels
>>
>> is more convenient and expressive than
>>
>>    \loadModule snippets.notation-snippets.align-lyrics-on-vowels
>>
>> etc.
>>
>> The question is:
>>
>> How many people are actually using the snippets repository, and how much
>> inconvenience would that be for these people. I *can* take some care
>> about "deprecating" and redirecting includes, but doing this generally
>> would actually make the whole thing totally convoluted. So actually I'd
>> prefer a clean cut and starting over with a new and cleaner structure.
>>
>> Opinions? Objections?
>
> No objections here.  Seems like a job for some kind of versioning or
> renaming of the snippets collection as a whole?  ("snippets2"?) Then
> you could preserve backwards compatibility and get your clean break.
>
> Or... this may not be helpful... but would it work to just move the
> contents of snippets out into their own modules, deprecating the
> "snippets" grouping, but leaving it in place, as is, for now for
> backwards compatibility?  So then you'd have, say:
>
> \loadModule lyrics.align-on-vowels
>
> Not sure what the larger repercussions of this would be, as I haven't
> kept up with how things are organized.  Feel free to disregard.

I mostly adopted your idea, which sounds - mostly - great to me.

I have made a copy of the snippets repository with the name oll-misc.
This pretty much reflects what this repository is actually about in my
opinion - and it moves away from confusingly duplicating with the LSR.

In this new repository I have all the liberty to throw out stuff that
has long been reimplemented elsewhere (in openLilyLib and also in
LilyPond itself), reorganize and rename items to my liking and also move
things out of the repo into other packages.
I'm very sorry that I don't have the time to bring everything in a clean
shape at the same time but at least it'll be a clean and hopefully final
structure.

The "cost" of that solution is that the snippets repository will
probably be even more exposed to bitrot as it already is now ...
I'll add a big deprecation warning to the README, though, encouraging
anyone not to continue using openlilylib/snippets.

Best
Urs

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

-- 
address@hidden
https://openlilylib.org
http://lilypondblog.org