-
Notifications
You must be signed in to change notification settings - Fork 494
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
Explore using own menu implementation with curses
#2364
Comments
I absolutely agree with this and was thinking the same thing. |
I'll try to get started on some code, happy to collect any suggestions on how to use it flexibly. |
I'm throwing out this as a discussion not a must. But to me it feels like a good idea to completely disconnect the UI part into a As it would make it easier down the line to choose flavor of UI. Would this be desired? As there's been numerous discussions about a GUI and that was treated this way. They'd have |
So how would the tui then be integrated into archinstall? Repo or just a module will lead to a similar outcome probably as the tui needs to be initialised and the components then plugged in. Maybe I'm missing a bigger picture here, what would the benefit be to have a different repo for it? |
Ideally the TUI could perhaps transit into doing Having two repos would make things a bit more maintainable by allowing more administrative privileges to be distributed without giving access to everything. I've been dabbling with a similar idea for the translations, as there's numerous PR's for translations and they don't really have an effect on the core features. Giving It's mainly just a structural change for making maintenance more diverse. |
Let me try to unwrap that, the TUI would be a new standalone repo/library that will import What would happen to the menu system in archinstall? Would that be thrown out and only have the core functionality in there, basically all core logic that is included in the
All other functionality is tightly coupled with the current menu system and only used to create the configuration that is then relevant for the above points. Another question is Looking at the development environment, I see that creating a completely separate repo will cause a lot of friction for devlopers and contributors that want to get onboarded. It will be more complex to setup and get people involved. For the translation part, it's a bit of a isolated component as it doesn't have anything to do with the functionality of |
Currently
archinstall
is usingsimple-term-menu
for rendering the menu on the tty. Although the library does its job, it is also somewhat limited on the possibilities beyond a simple menu display. Information can only be shown from a top to bottom approach and there is no way of utilizing other spaces on the screen to be more flexible.An alternative approach could be to use
curses
, this would require a custom implementation of the existing menu capabilities but would then allow to add a lot more customization on top.The text was updated successfully, but these errors were encountered: