Hi Dirk, > On 28. Nov 2025, at 23:32, Dirk Hohndel via subsurface > <[email protected]> wrote: > > So this email is a request for help and a request for people to refresh my > memory. > > - how much of 'user manual with WebEngine' has been tested? > - what is the latest state of 'printing without WebKit'? > - who else is working on Qt 6 support?
I am glad, there is movement forward in this direction. I am happy to join in here and do some work. Here is my (memory of the current) situation: 1) When I run the binaries the fell out of your recent activities (as of this morning Europe time), they crash upon startup on my arm Mac. Is there something obvious I am missing? 2) I have not been able to build Subsurface on any of my Macs since moving to Apple silicone which has been many months ago. This is very likely due to too much old stuff (in terms of libraries, Qt versions, stuff installed using homebrew) on these machines. Unfortunately just burning the build directory is not enough and not even a brand new clone of https://github.com/subsurface/subsurface in a brand new directory does the job, I have tried several times over the months and sank many hours without any fruit. Unfortunately, I need these computers for my daily work, so a complete reinstall is not an option. What works for me is a thinkpad with Linux where I successfully build Subsurface which is what I have done for about a year now. 3) Almost exactly four years ago, I had a branch to get rid of webkit and replace the functionality with webengine: https://github.com/subsurface/subsurface/compare/master...atdotde:subsurface:webeinginewait If my memory does not fail me, that kind of worked, the user manual did not have any problems. Also printing worked for me on my Mac at the time, but for you we could not make all the images load on time on Linux. At some point this attempt fell asleep. But I am happy to revive it if it is of any use now. Also in view of 2) I can now better test it on Linux myself. Here is, from my memory, what the approach was: In our printing template system, at the time, we made the bad decision to include the profile pictures via special <div> tags. When using webkit to render the page, we could access these tags and replace the by the appropriate <img> tags. In webengine, however, there is no access to individual elements in the DOM, you are supposed to do that via JavaScript (a language that I do not really speak). I managed to come up with some script that should be able to do that but the problem was to determine the time when that script had done its job before shipping the page to the printer. I could not make any callbacks that would be supposed to do that work, so I fell back to just sleeping for a while but on Linux even that seemed not to be sufficient as not all profile pictures were printed. I will now try to bring that old branch up to speed with what you have. An alternative would always be to break backwards compatibility and get rid of the stupid <div> tags and rather do it directly with <img> tags. I don't know how many user that would affect that have written their own printing templates that would have to be adopted. What do you think? Best Robert
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ subsurface mailing list -- [email protected] To unsubscribe send an email to [email protected]
