Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. Showcase
  4. Decoupled QML frontend/backend architecture for Node js, Android, Webapp and Native usecases
Forum Updated to NodeBB v4.3 + New Features

Decoupled QML frontend/backend architecture for Node js, Android, Webapp and Native usecases

Scheduled Pinned Locked Moved Showcase
1 Posts 1 Posters 624 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.
  • R Offline
    R Offline
    r0ller
    wrote on last edited by
    #1

    This is a sketch for a cross-platform architecture where the frontend is qml and the backend is c++. I know that qt is cross-platform by design but I was looking for a design with which I can have the same frontend and backend everywhere even in a client-server setup. Besides that I also wanted more freedom (not being bound to a specific android ndk version) but also wanted to keep qml as a ui even for non qt c++ backend. So I started by decoupling the qml ui and looked for a design pattern with which the communication can be solved in each scenario.

    You can find the project here with the wiki, code and the build artifacts:

    https://github.com/r0ller/qwa/wiki

    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