Why Are Changes I Made in Gui-v1 Not Visible in Gui-v2? Do I Need to Make Separate Modifications for

Modifications
, ,
1

Why Are Changes I Made in Gui-v1 Not Visible in Gui-v2? Do I Need to Make Separate Modifications for Gui-v2?

Hi everyone,

I’ve been working with Venus OS and recently transitioned from gui-v1 to gui-v2. While I was able to easily modify gui-v1 by editing the QML files on the GX device, I noticed that these changes don’t carry over or reflect in gui-v2. After some research and testing, I have a few questions and would like clarification:

Observations:

  • In gui-v1, any modifications to the QML files were immediately visible both locally on the GX device and remotely via the browser (VNC-based Remote Console).
  • In gui-v2, editing the QML files on the GX only affects the local on-screen display. These changes are not visible in the remote UI (browser-based WebAssembly version).

Questions:

  1. Why don’t my gui-v1 changes reflect in gui-v2?
  • Is this because gui-v2’s architecture has shifted to using WebAssembly (WASM) for the remote UI?
  1. Do I need to make separate modifications for gui-v2?
  • For local display, I understand I can still modify the QML files. However, how do I modify the WASM version for remote UI?
  • What tools or steps are required for this? I’ve seen references to Qt6 and Emscripten but would appreciate a more detailed guide or workflow.

Request for Guidance:

If anyone has experience modifying gui-v2, especially the WASM version, I’d love to hear how you approached it. Are there any best practices for keeping both the local and remote UIs consistent with custom changes?

Thanks in advance for your help and insights!

2

Hi and welcome.
There are existing topics on this subject here and on the archive.
Such as: Modifying gui-v2
Would encourage you to do some searching on the matter.
Post moved to the relevant category.