Plugin management

[dim-ghub]

Hi, I've begun work on a PR for hyprpm management through hyprmod, Im wondering what your thoughts on how we should achieve this are. Since hyprland plugins are external, we can't account for every possible setting they may have. So, should we just attempt to implement each plugin one at a time or leave a lot of up to the user and just provide a GUI frontend?

[BlueManCZ]

Hi, thanks for the interest, and nice to see someone already digging into a PR for this!

Architecturally this will be tough. I think the best approach would be a dedicated plugin page listing the plugins HyprMod supports (and which ones are enabled), where clicking a plugin opens a page or dialog with settings generated from its definition/schema file. This way we could add a new plugin in the future just by adding a new schema file, without touching any UI code.

You can check the current schema for most HyprMod options in /data/schema/options.json. It builds on top of the auto-generated hyprland-schema, with some custom tweaks, and the UI is mostly generated from that, so a similar per-plugin schema approach would fit naturally.

If the changes end up getting hard to track, feel free to split it into multiple PRs rather than one big one, it'll make the review process easier.

I don't currently use any plugins myself, so this hasn't been high on my priority list, but I'm glad someone's picking it up, and happy to help figure out the design.

[dim-ghub]

This is my idea for the latter approach, could be better. Its not very intuitive.

[dim-ghub]

This implementation could be kept for adding "custom" entries for plugins we dont support yet.

[BlueManCZ]

I see we posted at the same time. 😄

[BlueManCZ]

Yes, that's a good idea. Keep it as a fallback method if the user really wants to add an option that is not yet supported.

[dim-ghub]

I'll start with hypr-dynamic-cursors as its the only plugin I personally use, will give us a good groundwork for how we want future pages to look

[dim-ghub]

Supported plugins implementation:

Let me know your thoughts. This is the hard part, implementing other plugins will be easier

[dim-ghub]

If youre happy with this, Ill go ahead and draft a PR

[BlueManCZ]

The UI looks good. I would surface the count of set options and enabled/disabled status right in the supported plugins list. Go ahead and create a PR, so I can take a look at the implementation.

[dim-ghub]

I will in a moment, working on an issue with wrapping plugins with if statements so they dont cause issues if the plugin isnt loaded

if hl.plugin.plugin_name then
    ...
end

[dim-ghub]

PR opened:
#60

[dim-ghub]

Also, heres this in relation to your last suggestion