Files
RedBear-OS/local/recipes/qt/qtbase/source/doc/global/app-examples-template/README.md
T
vasilito f31522130f fix: comprehensive boot warnings and exceptions — fixable silenced, unfixable diagnosed
Build system (5 gaps hardened):
- COOKBOOK_OFFLINE defaults to true (fork-mode)
- normalize_patch handles diff -ruN format
- New 'repo validate-patches' command (25/25 relibc patches)
- 14 patched Qt/Wayland/display recipes added to protected list
- relibc archive regenerated with current patch chain

Boot fixes (fixable):
- Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset)
- D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped)
- redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped)
- daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch)
- udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async)
- relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs
- greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait)
- greeter-ui: built and linked (header guard unification, sem_compat stubs removed)
- mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps
- greeter config: removed stale keymapd dependency from display/greeter services
- prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified

Unfixable (diagnosed, upstream):
- i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort
- kded6/greeter-ui: page fault 0x8 — Qt library null deref
- Thread panics fd != -1 — Rust std library on Redox
- DHCP timeout / eth0 MAC — QEMU user-mode networking
- hwrngd/thermald — no hardware RNG/thermal in VM
- live preload allocation — BIOS memory fragmentation, continues on demand
2026-05-05 20:20:37 +01:00

3.0 KiB

Qt Application Examples Template

Use the 'app-examples-template.qdoc' file when creating or updating any of the Qt application examples.

The purpose of the template is to make it easier for technical writers and developers to create documentation with a consistent look and feel. The consistent look and feel also enhances user experience. For this to work, you cannot move the sections around. You can and must change the text within the angle brackets and check the links.

To use the template

  1. Copy the file to the doc/src folder in your documentation project.
  2. Change the text within angle brackets to fit your example.

Application examples structure

  • State the objective of the example.

  • Explain which Qt technologies are used.

  • Explain what Qt features are shown.

  • (Optional) Create a workflow diagram for more complicated examples. The WebEngine Push Notifications Example demonstrates this well.

QUIP-21 explains how to use images in Qt Documentation.

Explain how to run the example

(Optional) Provide relevant platform information

  • List any platform limitations or exceptions, if applicable.

(Optional) Provide a UI walkthrough

  • Use for more complicated examples.
  • The walkthrough describes how to navigate and access different parts of the example/UI.
  • The Coffee Machine example demonstrates this well.

(Optional) Provide a list of the main Qt classes and modules the examples uses

(Optional) Create a class diagram

Describe Feature A

  • Explain the implementation of the feature in the code.

Feature B... (Add a separate feature section for all relevant features)

  • Explain the implementation of the feature in the code.

(Optional) Include Squish testing information if applicable

  • If example was tested with Squish, include squish-tested-example.qdocinc

(Optional) Create a Best practices section

  • Add any relevant best practices.
  • Use \sa command to link to All Qt Examples, and to other relevant documentation.
  • A link to the source code is automatically generated whenever the \example command is used.