lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Openlilylib


From: Simon Albrecht
Subject: Re: Openlilylib
Date: Fri, 27 May 2022 12:26:47 +0200

Hi Andrew,

sorry that your investments into Dorico didn’t work out! It’s great to have you back in the Pond :)

I have been thinking that it would be nice to invest more time into Lily myself, but I don’t yet know whether/how/when I can make that happen.

Best, Simon

On 27/05/2022 10:24, Andrew Bernard wrote:
Hello All,

Having had to abandon the Openlilylib (OLL) work I took over from Urs Liska, for various reasons, in the meantime I went over to Dorico instead of Lilypond for my work. Having spent a lot of money on Dorico (AUD$800+) and given it my best shot for more than year, it really falls short for the modernist work that I do, dogmatically follows the Gould rule book and does not let you override most of that (it's what software people call an opinionated program), crashes often with the latest release and they cant solve it and just remain silent, and worse, the forum which I initially thought helpful is turning out to be quite toxic and I get a lot of personal abuse. along with deprecating comments about the music I work on. Consequently I have binned Dorico as of yesterday and I am coming back to lilypond.

The upshot of that is that I suppose I should revive the OLL work. I'll recreate the dedicated server I set up, recreate the Discourse forum for discussion, and work on the git repository, then people can collaboratively work together again and I can take pull requests and so on.

I stalled initially a couple of years ago when I decided to totally refactor the OLL github repostory, but now I think if we open it up again as is and I work on that on the background which would be useful.

I'll pay for the server resources out of my own pocket, but provide a Paypal link for donations for running costs (server, domain name, etc).

Andrew






reply via email to

[Prev in Thread] Current Thread [Next in Thread]