Le samedi 18 mars 2023 à 16:44 -0500, Karlin High a écrit : > Or, maybe it would be better to have all this handled within > Frescobaldi instead? > > Have Frescobaldi look up the latest version of LilyPond, and if it > doesn't exist on the user's computer, offer to download and install > it? It's been mentioned within that project: > > <[https://github.com/frescobaldi/frescobaldi/issues/1429](https://github.com/frescobaldi/frescobaldi/issues/1429)> > > <[https://github.com/frescobaldi/frescobaldi/issues/313](https://github.com/frescobaldi/frescobaldi/issues/313)>
Yes, in my ideal world, the onboarding process would look like: download the Frescobaldi installer, have Frescobaldi detect that you are running it for the first time and propose you to install LilyPond, click "OK", and voilà, you're up and running. Producing installers that "feel the way users of $PLATFORM expect an installer to look like" would reintroduce platform-specific considerations and complexity into LilyPond's binary generation system that we were pretty happy to get rid of.
signature.asc
Description: This is a digitally signed message part
