Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. QtWebEngine
  4. Safe to delete unnecessary webengine resources like locales and devtools .pak files?
Qt 6.11 is out! See what's new in the release blog

Safe to delete unnecessary webengine resources like locales and devtools .pak files?

Scheduled Pinned Locked Moved Unsolved QtWebEngine
webenginedeploymentchromium
7 Posts 3 Posters 643 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    Dan D
    wrote last edited by
    #1

    Hi I want to bundle WebEngine in my package and by default it ships lots of translation resources (translations/qtwebengine_locales/*.pak) and other resources like (resources/qtwebengine_devtools_resources.pak)

    I use WebEngine to open static license page and IdP login page to capture token. Nothing else is or should be used.

    Can I safely remove these resources to free up some deployment space?

    jsulmJ 1 Reply Last reply
    0
    • D Dan D

      Hi I want to bundle WebEngine in my package and by default it ships lots of translation resources (translations/qtwebengine_locales/*.pak) and other resources like (resources/qtwebengine_devtools_resources.pak)

      I use WebEngine to open static license page and IdP login page to capture token. Nothing else is or should be used.

      Can I safely remove these resources to free up some deployment space?

      jsulmJ Offline
      jsulmJ Offline
      jsulm
      Lifetime Qt Champion
      wrote last edited by
      #2

      @Dan-D Webengine is quite heavy to show license pages. QTextDocument can render a subset of HTML (setHtml()).

      https://forum.qt.io/topic/113070/qt-code-of-conduct

      D 1 Reply Last reply
      0
      • jsulmJ jsulm

        @Dan-D Webengine is quite heavy to show license pages. QTextDocument can render a subset of HTML (setHtml()).

        D Offline
        D Offline
        Dan D
        wrote last edited by
        #3

        @jsulm I agree. We are changing that. Just need a green light from team

        1 Reply Last reply
        0
        • SGaistS Offline
          SGaistS Offline
          SGaist
          Lifetime Qt Champion
          wrote last edited by
          #4

          Hi,

          And for login, you have the Qt Network Authorization module.

          Interested in AI ? www.idiap.ch
          Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

          D 1 Reply Last reply
          1
          • SGaistS SGaist

            Hi,

            And for login, you have the Qt Network Authorization module.

            D Offline
            D Offline
            Dan D
            wrote last edited by
            #5

            @SGaist Unfortunately, while I'd like to remove WebEngine entirely, we can't eliminate it because we still depend on the embedded browser for IdP authentication. It's one of the supported login methods, and a significant number of customers use it.

            1 Reply Last reply
            0
            • SGaistS Offline
              SGaistS Offline
              SGaist
              Lifetime Qt Champion
              wrote last edited by
              #6

              You might want to check the Qt WebView module as well. It might be lighter.

              Interested in AI ? www.idiap.ch
              Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

              D 1 Reply Last reply
              0
              • SGaistS SGaist

                You might want to check the Qt WebView module as well. It might be lighter.

                D Offline
                D Offline
                Dan D
                wrote last edited by
                #7

                @SGaist Thank you for this suggestion!

                I've actually evaluated this option, the problem for my case is that the application runs on Linux. Unfortunately, according to the docs, the underlying engine for web view for Linux is Qt's web engine.

                On Linux, Qt WebView depends on the Qt WebEngine module to render content.

                Currently or main concerned is the control on QT libraries. Current the app use system provided QT libraries. I am planning to ship a self contained package first. And the main concern around this is the deployment tree size.

                Removing these resources saved ~80MBs but I am not sure if that would break anything

                1 Reply Last reply
                0

                • Login

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups
                • Search
                • Get Qt Extensions
                • Unsolved