Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Qt for WebAssembly
  4. got my app running...
Forum Updated to NodeBB v4.3 + New Features

got my app running...

Scheduled Pinned Locked Moved Unsolved Qt for WebAssembly
4 Posts 2 Posters 556 Views 1 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.
  • mzimmersM Offline
    mzimmersM Offline
    mzimmers
    wrote on last edited by
    #1

    ...actually looks pretty good (just a few things to clean up).

    We'd like to use this for our field service folks to remotely access the app. I'm not clear on a couple things:

    1. would we have an in-house dedicated server with emscripten and all that, running a web server?
    2. what is the deliverable to the client(s)?
    3. according to the docs, "Emscripten provides the emrun utility for test-running applications. Emrun starts a web server, launches a browser, and will also capture and forward stdout/stderr (which will normally go to the JavaScript console)." So to where does stdout/stderr get forwarded? I'm trying to figure out how to get feedback from the app that I normally see through the use of qDebug() and console.log() statements in the code.

    Thanks for any clarification.

    MesrineM 1 Reply Last reply
    0
    • mzimmersM mzimmers

      ...actually looks pretty good (just a few things to clean up).

      We'd like to use this for our field service folks to remotely access the app. I'm not clear on a couple things:

      1. would we have an in-house dedicated server with emscripten and all that, running a web server?
      2. what is the deliverable to the client(s)?
      3. according to the docs, "Emscripten provides the emrun utility for test-running applications. Emrun starts a web server, launches a browser, and will also capture and forward stdout/stderr (which will normally go to the JavaScript console)." So to where does stdout/stderr get forwarded? I'm trying to figure out how to get feedback from the app that I normally see through the use of qDebug() and console.log() statements in the code.

      Thanks for any clarification.

      MesrineM Offline
      MesrineM Offline
      Mesrine
      wrote on last edited by
      #2

      @mzimmers

      1. You just need a web server that serves HTML, no need for emscripten.

      2. the app.html, app.js, app.wasm, qtLoader.js. With this the client can run the application in any webserver.

      3. I normally use the developer console of the browser.
        All the messages from qDebug and console.log are shown there.

      mzimmersM 1 Reply Last reply
      3
      • MesrineM Mesrine

        @mzimmers

        1. You just need a web server that serves HTML, no need for emscripten.

        2. the app.html, app.js, app.wasm, qtLoader.js. With this the client can run the application in any webserver.

        3. I normally use the developer console of the browser.
          All the messages from qDebug and console.log are shown there.

        mzimmersM Offline
        mzimmersM Offline
        mzimmers
        wrote on last edited by
        #3

        @Mesrine said in got my app running...:

        the app.html, app.js, app.wasm, qtLoader.js. With this the client can run the application in any webserver.

        So, if I distribute these files to customers, how do they invoke the application?

        MesrineM 1 Reply Last reply
        0
        • mzimmersM mzimmers

          @Mesrine said in got my app running...:

          the app.html, app.js, app.wasm, qtLoader.js. With this the client can run the application in any webserver.

          So, if I distribute these files to customers, how do they invoke the application?

          MesrineM Offline
          MesrineM Offline
          Mesrine
          wrote on last edited by
          #4

          @mzimmers
          Normally, those files are distributed over the internet through a web server.
          Like:
          https://eddytheco.github.io/NftMinter/
          Github uses a server to distribute those files to clients(browsers).

          But if your client downloads those files and serves them under his own server, it is the same.

          They can invoke the application locally in the same way you do when testing and developing. By running emrun, or with a python webserver, in general, using a web server. Some applications must use https(secure environment).

          1 Reply Last reply
          1

          • Login

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