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

Add accessories/metadata properties to game data #302

Open
rsubtil opened this issue Oct 13, 2023 · 2 comments
Open

Add accessories/metadata properties to game data #302

rsubtil opened this issue Oct 13, 2023 · 2 comments
Labels
backlog Ideas to eventually implement, but not currently prioritary. question Further information is requested topic:core Issues or pull requests related to RetroHub itself

Comments

@rsubtil
Copy link
Member

rsubtil commented Oct 13, 2023

(suggested on Discord)

The idea is to add a property on game data in order to specify some details about that particular game, such as "lightguns, mouse, keyboard, rumble, 3 or 6 button, analog etc.".

This presents a challenge though: leaving it a plain "string" array for users to specify makes this non standardized for themes to take advantage of, but defining these properties in the app's code is also a significant task requiring plenty of research.

This idea has potential though as it can be help in organizing the user's library more easily, but the implementation of it needs to be better discussed and experimented on before being tackled.

@rsubtil rsubtil added question Further information is requested topic:core Issues or pull requests related to RetroHub itself backlog Ideas to eventually implement, but not currently prioritary. labels Oct 13, 2023
@Ro-Borges
Copy link

Hello, it was me who suggested it. I don't know if it is possible, but maybe it could have a set of predefined/generic accessories that could be expanded with user-defined ones. This way, the themes would have a standard to comply with, and the users could customize their build with a more specific set if they desire.

@rsubtil
Copy link
Member Author

rsubtil commented Oct 13, 2023

Yes, I think that's a good solution for now. It will require some significant research and user input though, so this will be in the backlog for a while until the app is released and this receives more user feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Ideas to eventually implement, but not currently prioritary. question Further information is requested topic:core Issues or pull requests related to RetroHub itself
Projects
None yet
Development

No branches or pull requests

2 participants