Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gnome-games gnome-games
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Archive
  • gnome-gamesgnome-games
  • Issues
  • #22
Closed
Open
Issue created May 12, 2018 by Alexander Mikhaylenko@exalmMaintainer

Make Extensions/Plugins sections in preferences more useful

The current Extensions section in preferences has the following problems:

  1. Plugins don't correspond to Libretro cores:
  2. Having a plugin installed for a platform does not mean being able to play games for that platform.
  3. Not all platforms are represented by plugins.
  4. There's a plugin for Nintendo DS, but not for Game Boy Advance, but in stable version there's a core for GBA, but not for DS.
  5. Plugins cannot be turned on or off.
  6. There are no external plugins.
  7. In some cases some of the plugins may not work.
  8. Desktop plugin does not work in Flatpak.
  9. Steam plugin does not work if Steam is installed as Flatpak.
  10. Are they called extensions or plugins? Or maybe both?

Basically, in their current state plugins are just an implementation detail. Many (most?) platforms are supported via Retro.SimpleTypes, and only ones that need special-casing (like filtering out some files, or extracting icons, or fetching info from a game database) have plugins.

See also #21 (closed).

@aplazas suggests replacing this section with a Platforms section that lists available platforms, cores available for them, and (possibly) allows selecting libretro core for each platform.

The latter is unnecessary in Flatpak, but some distributions package multiple cores for the same platform. Currently there's no control over which core is used.

Being able to select cores would bring another problem: saves and save states aren't necessarily compatible between cores, so it might lead to a data loss.

One way to solve that is to be name them after cores instead of platforms.

  • How to migrate them?
  • Sometimes cores are renamed; in that case saves are compatible, and thus need to be migrated. This is not a problem currently, because platform doesn't change.
Assignee
Assign to
Time tracking