On Thu, 2026-05-07 at 09:39 -0500, Jeremiah Benham wrote: > Richard, > Due to the large wait time for the windows version to load, should we > add a splash screen for win32 builds? I've an idea I had a look at doing this some years ago and that it wasn't quite straight forward (I think because we start the gtk_main() rather late in the day)
> I have keep trying to find ways > to speed things up I just downloaded https://github.com/jbenham2015/Denemo/actions/runs/25471582568/artifacts/6845552000 and ran it under wine, it didn't take too much time loading, but as before it had problems: not installing the fonts, not finding the keyboard and not being able to access the home directory (I/O error!). But on the plus side it loaded an example from the installed examples directory and typeset it with the default LilyPond and played it back by clicking on the first note of the piece in the Print View, which is very impressive. I'll see if I can get it tested with a real Windows o/s. > on my end but I think the process of it being such > a foreign system to win32. I don't know. I read that natively > compiling it may shave 20-30% of the time off. We can turn off > debugging symbols and compile it as was as its dependencies with > greater optimisation. I don't know if we sacrifice stability if we do > that. What do you think? I think it would be premature to turn of debug symbols and increase optimisation, it would have to be working properly on Windows first. Richard > With github it makes it easy to natively > compile things. I see this as a growing trend. > The splash screen may be necessary for the macOS version as well. I > don't know. I have not had a chance to test that build yet. With the > Mac Os It will surely need something before it will even launch. It > compiles. Maybe if I can run tests at the command line each time it > builds like denemo --version and other sanity checks. > > Best, > Jeremiah >
