<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Dirk,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 24. Nov 2021, at 19:32, Dirk Hohndel via subsurface <<a href="mailto:subsurface@subsurface-divelog.org" class="">subsurface@subsurface-divelog.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div class="">Hi Robert</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><br class=""></div><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">thanks for the slight push. This made me sit down and implement the template editing with WebEngine. I decided that for the time being, the Subsurface „Preview“ button is not really needed to be ported to WebEngine as the OS also supplies preview capabilities in the printing dialog (at least MacOS does, I hope my assumption about Windows and Linux is correct here). </div></div></div></blockquote><div class=""><br class=""></div><div class="">I think so - that does seem fairly universal. I can test this on Windows; I actually have a physical Windows machine now so I can do more testing on that - I still dislike actually USING Windows, but at least I can run Subsurface and try the different device connections without having to go through a virtualization layer and wondering which problems might be caused or hidden by virtualization...</div></div></div></div></blockquote><div><br class=""></div><div>Since Windows still uses WebKit, this whole thing should be a no-op there, no functionality to test. </div><div><br class=""></div><div>What I meant is: I removed the preview button in our own dialogue <img apple-inline="yes" id="DB628923-B5DC-48DC-BF96-82AE606CA76E" width="370" height="507" src="cid:320F6BF6-6532-49A3-A2C5-FF97234F4BE5" class=""></div><div><br class=""></div><div>since when you press the „Print“ button, it opens the OS print dialogue</div><div><img apple-inline="yes" id="2C33B1FB-A7AA-4CBD-94E9-BDFFFF4B0CAC" width="578" height="413" src="cid:A6B3C609-B09B-4B73-AE99-55F3E0EBB8DE" class=""></div><div><br class=""></div><div>which under the „PDF“ selector again offers to open a preview/print to a PDF. Are there similar options on Linux?</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""></div><div class="">What I don't have, so far, is an Apple M1 system. I played with the idea of getting a Mac Mini but then decided that I didn't really need yet another machine. I already have an insane amount of computers here :)</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">So, I consider my „replace webkit with WebEngine“ branch feature complete and ready for merging. The replacement is still subject to a make option (USE_WEBENGINE) but my suggestion would be to make that ON by default on all platforms but Windows and then ditch WebKit wherever possible.</div></div></div></blockquote></div></div></div></blockquote><div><br class=""></div><div>Until early next week, I am still in quarantine. Then I hopefully can go back to the office with the M1 Mac that started this whole shebang. I cannot build there (as explained) but I hope I can build on another Mac and move the binary there (I have not tried that, though) and run it in rosetta.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div class=""><br class=""></div>My understanding is that we'll need to keep this on Windows as long as we can. So I'm thinking that for a good long time the Windows builds will be Qt 5.15 + QtWebKit.</div><div class="">In parallel we can work on moving the Mac to Qt 6 + QtWebEngine</div><div class=""><br class=""></div><div class="">That should allow us to build on M1/ARM - so this seems like a "best of both worlds" idea... I hope.</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">A corresponding PR can be found here: <a href="https://github.com/subsurface/subsurface/pull/3352" class="">https://github.com/subsurface/subsurface/pull/3352</a></div></div></div></blockquote><div class=""><br class=""></div>I'll look at this today.</div></div></div></blockquote><div><br class=""></div><div>I commented there as well.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Let me mention that I took care not to break backwards compatibility for templates. Some things (in particular the profiles) would have been easier with a slight change of template syntax but for the benefit of users that made their own templates (are there many?) I decided not to force them to update their templates.</div></div></div></blockquote><div class=""><br class=""></div><div class="">There are a few. I remember that when I broke a feature in a build a year or so ago (thanks to the pandemic time has lost all meaning, so take that time frame with a grain of salt), I quickly got complaints. Mainly from Germans, though :)</div></div></div></div></blockquote><div><br class=""></div><div>Good. So this wasn’t in vain.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Let me mention that I realized only now that the fact that our printing is via html allows to include html tags in the dive notes to be rendered in the printout. And of course that allows you to embed images from the web (like our logo…). This is of course also true for the templates. There is room for CI (printing our logo on divelog print outs or include dynamic content from the web, e.g. ads for <a href="http://www.hohndel.org/" class="">www.hohndel.org</a> or similar). The possibilities are infinite.</div></div></div></blockquote><br class=""></div><div class="">What is <a href="http://www.hohndel.org/" class="">www.hohndel.org</a>? What are ads?</div><div class="">Funnily enough, since I no longer have a server that I think of as "<a href="http://hohndel.org/" class="">hohndel.org</a>" this ends up automagically forwarding to <a href="http://subsurface-divelog.org/" class="">subsurface-divelog.org</a>... kinda neat :)</div><div class="">I do use "hohndel.name" for my underwater photography.</div></div></div></blockquote><div><br class=""></div><div>Whatever. But one could think about having print templates with room for larger images which would be downloaded from some web space...</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">But I digress. I'll look at the PR. With 5.0.5 just released this seems like the perfect time. And I also want to merge Berthold's profile changes - I already worry if there is breakage once we mix those two.</div></div></div></blockquote><br class=""></div><div>I don’t think there will be too much overlap (famous last words).</div><div><br class=""></div><div>Best</div><div>Robert</div><div><br class=""></div><br class=""></body></html>