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.

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

Ship OSD icons separately #20

Open
seriyps opened this issue Oct 12, 2024 · 4 comments
Open

Ship OSD icons separately #20

seriyps opened this issue Oct 12, 2024 · 4 comments

Comments

@seriyps
Copy link
Collaborator

seriyps commented Oct 12, 2024

In this commit OSD icons were embedded into the source code. I don't think it was the right decision, because it limits customization.
gehee/FPVue_rk@7ab9e11

Also, might be nice to think about some ways to customize the OSD somewhat more than it is possible now. Maybe introduce some ways to define OSD elements declaratively in a file?

@widgetii
Copy link
Member

It's a perfect idea.

@luastoned
Copy link
Collaborator

I thought about OSD elements being defined by some configuration as well.
Maybe even pull stats from a stream/different file so noone has to touch the source code to add new blocks..

@seriyps
Copy link
Collaborator Author

seriyps commented Oct 21, 2024

Created a separate ticket to discuss flexible OSD #27

@seriyps
Copy link
Collaborator Author

seriyps commented Nov 6, 2024

It is partially handled in #36 , but we need to improve our build system so it generates some kind of archive or .deb that will include binary and icons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants