Volker: I investigated a bunch of options: OpenSceneGraph (or VulkanSceneGraph), bgfx, sokol, and Magnum.
Magnum seems to fit my use-case: https://github.com/mosra/magnum Don't love all the templating, but otherwise I like it so far. Easy to integrate as a QOpenGLWidget & I think it provides the right level of hand-holding for me :-) Extensive documentation & examples. https://doc.magnum.graphics/magnum/ --- Andy Maloney // https://asmaloney.com mastodon ~ @asmalo...@fosstodon.org <https://fosstodon.org/@asmaloney> On Sat, Feb 15, 2025 at 9:45 AM Volker Enderlein < volkerenderl...@hotmail.com> wrote: > Hi Andy, > > Out of curiosity, what new or boring technology are you migrating your > Qt3D to? > > Cheers, Volker > > Am 14.02.2025 um 16:00 schrieb Andy: > > Thanks Mike. > > I was actually doing something similar and moved away from it in favour of > (more) self-containment! :-) > > I did have some success at making a "litehtml widget" and could probably > replace my docs using it, but I couldn't get the creation of PDFs working > with it properly. I'm sure it could be done, but I have too many other > things to do (e.g. migrating away from Qt3D), so for now I live with the > Chromium beast... > > It would be great to have a non-JavaScript HTML/CSS layout capability - > maybe beef up Qt::TextFormat to add Qt::HTMLCSSText using litehtml or > something like that. Then it would be dead-simple to drop in a QLabel with > some properly laid-out HTML/CSS anywhere you want. > > --- > Andy Maloney // https://asmaloney.com > mastodon ~ @asmalo...@fosstodon.org <https://fosstodon.org/@asmaloney> > > > On Thu, Feb 13, 2025 at 6:40 PM Michael Jackson < > mike.jack...@bluequartz.net> wrote: > >> @Andy <asmalo...@gmail.com> >> We went down this road years ago with the same issues as you with >> respect to running in a sensitive environment and having the extra process >> running. We eventually switched to using sphinx to generate our >> documentation, ship it as a non-compressed folder that has the HTML web >> site. We then added code to just use QDesktopProcess(?) or something like >> that to just launch the needed html doc in the user’s web browser of >> choice. Not saying this would work for your situation but just another data >> point to consider. >> >> -- >> Mike Jackson mike.jack...@bluequartz.net >> BlueQuartz Software www.bluequartz.net >> President/Owner Dayton, Ohio >> Principal DREAM.3D Developer >> >> >> On Feb 13, 2025 at 10:53:05, Andy <asmalo...@gmail.com> wrote: >> >>> Vladimir: >>> >>> Thanks for the survey. There wasn't a free-form comment section at the >>> end of the survey, but I had a couple of notes... >>> >>> I use QWebEngine for three things for my desktop application: (1) >>> displaying my manual (built using the Qt help system), (2) displaying HTML >>> reports I generate on the fly using a template system (KTextTemplate), and >>> (3) saving those reports as PDFs. >>> >>> Using QWebEngine had several consequences: >>> >>> 1) On Windows only MSVC is supported, so it changed my development >>> tooling. MSVC is a pain to use since there are so many little things that >>> are different/unsupported (w.r.t. clang or gcc). It would save me a lot of >>> time not to have to worry about those differences. >>> 2) Now I have to pull in & ship libs (WebChannel, Positioning, Quick? >>> QML stuff?) that I don't use directly >>> 3) Now I have to deal with questions from my customers about >>> QWebEngineProcess (I deal in a moderately sensitive area where they take >>> security a bit more seriously) >>> 4) The size of my shipping applications went from 60 MB to 136 MB >>> (Windows) and 38 MB to 250 MB (not directly comparable since I also >>> switched to universal builds, so probably ~125 MB) >>> 5) The drastic increase in size not only impacts user downloads, but it >>> also means the signing & notarizing stuff is much slower for me >>> >>> None of my HTML/docs/reports use JavaScript, so ideally, for my use >>> cases, Qt would offer a lighter HTML/CSS layout widget (maybe using >>> something like litehtml (https://github.com/litehtml/litehtml), but >>> more complete/robust) that would allow display/interaction with >>> non-JavaScript pages, and allow saving them to PDF. If I'm not mistaken, Qt >>> Creator uses litehtml for its docs? >>> >>> Summary: I'd love to get rid of this Chromium behemoth and replace it >>> with something more reasonable for my use-cases. >>> >>> Thanks! >>> >>> --- >>> Andy Maloney // https://asmaloney.com >>> mastodon ~ @asmalo...@fosstodon.org <https://fosstodon.org/@asmaloney> >>> >>> >>> On Wed, Feb 12, 2025 at 4:38 AM Vladimir Minenko via Interest < >>> interest@qt-project.org> wrote: >>> >>>> Good morning all interested in Qt! >>>> >>>> Qt is conducting a user survey about Qt WebEngine and Qt WebView. We >>>> want to hear users' feedback to properly align the priorities for the >>>> development of these components. We would appreciate your input. >>>> >>>> If you use Qt WebEngine or Qt WebView, please take 15–20 minutes to >>>> complete the survey. >>>> >>>> Some of you might have received a personalized email with an invitation >>>> to this survey. Please use the link in that email to submit your responses. >>>> If you saw this announcement on other email lists or the Qt Forum, please >>>> respond only once. >>>> >>>> Please respond as soon as possible, but no later than March 7th, 2025, >>>> when the survey will close. Click here to start: >>>> >>>> https://www.surveymonkey.com/r/LC9D3DF >>>> >>>> Thank you for your time and participation! >>>> >>>> -- >>>> Vladimir Minenko >>>> vladimir.mine...@qt.io >>>> +49 171 90 61 461 >>>> >>>> Product Lead for Qt Foundations, mobile and desktop platforms >>>> The Qt Company GmbH - https://qt.io >>>> >>>> Haus 31F, Balanstr 73, 81541 Munich, Germany >>>> >>>> Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen >>>> Sitz der Gesellschaft: Berlin >>>> Registergericht: Amtsgericht Charlottenburg, HRB 144331 B >>>> >>>> _______________________________________________ >>>> Interest mailing list >>>> Interest@qt-project.org >>>> https://lists.qt-project.org/listinfo/interest >>>> >>> _______________________________________________ >>> Interest mailing list >>> Interest@qt-project.org >>> https://lists.qt-project.org/listinfo/interest >>> >> > _______________________________________________ > Interest mailing > listInterest@qt-project.orghttps://lists.qt-project.org/listinfo/interest > > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > https://lists.qt-project.org/listinfo/interest >
_______________________________________________ Interest mailing list Interest@qt-project.org https://lists.qt-project.org/listinfo/interest
