Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fixed links #132

Merged
merged 1 commit into from
Feb 6, 2024
Merged

fixed links #132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pages/docs/device-app/develop.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,6 @@ To get your project started quickly, we provide a complete framework made to dev
- [A `Rust` Boilerplate](https://github.com/LedgerHQ/app-boilerplate-rust) and
- [A Plugin Boilerplate](https://github.com/LedgerHQ/app-plugin-boilerplate)

More information on these components can be found in the [tutorials](./tutorials), [development environment](./tutorials)
and [tools](./tools) sections.
More information on these components can be found in the [tutorials](./develop/tutorials), [development environment](./develop/tutorials#development-environment)
and [tools](./develop/tools) sections.

2 changes: 1 addition & 1 deletion ...docs/device-app/develop/ui/ledger-nano-display/low-level-display-management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ See [the sample apps](https://github.com/LedgerHQ/ledger-sample-apps) for exampl

## BOLOS UX

The BOLOS UX is the implementation of the device-wide user interface; it is a component of the [dashboard application](../../../../architecture/bolos#dashboard). Applications delegate certain jobs to the BOLOS UX in order to retain consistency across all apps for certain UI components, as well as to allow the operating system to override the application's UI when necessary (for example, when locking the screen). The application interfaces with the BOLOS UX using `os_ux(...)`, which is a system call. However, applications don't need to call this function as it is automatically called by the display interaction helpers (the `UX_` macros).
The BOLOS UX is the implementation of the device-wide user interface; it is a component of the [dashboard application](../../../architecture/bolos#the-dashboard). Applications delegate certain jobs to the BOLOS UX in order to retain consistency across all apps for certain UI components, as well as to allow the operating system to override the application's UI when necessary (for example, when locking the screen). The application interfaces with the BOLOS UX using `os_ux(...)`, which is a system call. However, applications don't need to call this function as it is automatically called by the display interaction helpers (the `UX_` macros).

Applications should delegate **Events** like **Button Push Events** to the BOLOS UX (in this case, using `UX_BUTTON_PUSH_EVENT(...)`) instead of handling them directly, in case the BOLOS UX needs to override the application's UI. If the event is consumed by the BOLOS UX (for example, a pressed button while the user is unlocking the screen) then the event is not passed on to the application.

Loading