I know that it’s not on the top of your priority list, but here’s something that I thought about. Currently, there is several “menu drivers”. But when you look at the code, you see that it’s not really a driver. The driver does not drive the menu, it’s RetroArch which tells the menu what to do. It’s not a driver, it’s a skin ; there is absolutely no difference between glui or xmb, except the visual appearance, the options and behaviour are the same.
For me, a menu driver should be a lot more low-level : it should be able to get the inputs directly, read files and folders, edit some parameters and operate stuff on its own (like loading game and core), and not by waiting for RA to populate its entries. I think that it could lead to more diversified menus. For example, Lakka could become more user-friendly and more gaming console-like, by removing some “technical” stuff and being transparent for the user. Because right now Lakka is just a Linux distribution with a beautilul emulator built-in, not a gaming console. It even has to patch RA to work.
Currently the menu driver is the entries system, and the skins are glui, rmenu, xmb, etc. Maybe we could create another system which would allow to replace the entry system with something else (but by keeping the same features), and tho be able, for example, to build Lakka directly in RA without having to patch anything.
What do you think about it ?