OpenVoiceOS / OpenVoiceOS/ovos-gui
QML over HTTP server
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 5
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
When QML resources are served via HTTP paths (and possibly any non-file:// path), a special qmldir file is expected to exist for relative-path file resolution.
One potential option for Docker would be to bind the served resource directory to the host where the GUI client runs and translate paths to the host path (similar logic to how we currently translate paths to served URLs).
Alternatively, we just need to ensure that qmldir exists and is defined or else log some warning.
There may be other limitations to non-local resources for Qt and other GUI infrastructures to consider.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how QML resources are served over HTTP and how existing logic translates resource paths to served URLs. Compare the Docker host-path option with ensuring a qmldir file exists or logging a warning, and define done as handling non-file:// resources without unresolved relative paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- frontend, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100