On Sun, Apr 28, 2024 at 4:15 AM Jean Abou Samra <j...@abou-samra.fr> wrote:
> Doing some system updates today, I see that frescobaldi is the only > program that requires PyQtWebEngine:5, which in turn requires > qtwebengine:5. Looking at the frescobaldi page, I see a somewhat concerning > note that the project is on the verge of being unmaintained, due to this > dependency on a deprecated version of qtwebengine. > > Is there any further information on this? I don't see any other IDE that > works as well as frescobaldi for editing lilypond files, and I'm a bit > worried that there hasn't been an update to the program in over a year. Any > news would be appreciated. > > > > You've basically nailed the problem. I was the last person to work on > making Frescobaldi actually work on macOS, and I gave up by lack of time > (NB: I don't own a macOS machine, which of course makes all testing very > difficult). Currently, there is close to no activity on the project. > > I doubt Linux distributions are going to remove Qt 5 really soon, and the > Flatpak package can always provide it, but like every toolkit that's > end-of-life, it's only going to be a source of trouble going forward. For > example, Frescobaldi has some problems on Wayland (which is increasingly > becoming the default on the Linux desktop, for good reason) that are caused > by Qt 5 bugs fixed in Qt 6. I don't recall that anybody even attempted the > Qt 6 migration. > > Yes, if the current state continues, Frescobaldi will ultimately die a > natural death. Sorry that I cannot exactly bring an optimistic message > here. > If there is busy work that needs to be done on the project, I can do that, but I also don't own a Mac. -- Knute Snortum
