metainformation in the theme file #14141

New issue

Open

opened 2026-02-22 00:44:19 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-22 00:44:19 -05:00

Owner

Originally created by @b-user on GitHub (Dec 24, 2022).

Suggestion

Add fields to the theme to store meta information.
Add the meta information display to the user interface.

Use case

Using UI, the user can identify the origin, version (etc.) of the theme.
at the moment, there are difficulties and confusion with this.

Extra info/examples/attachments

At the moment, github has

a dozen theme with the same content, but different names
different versions of one theme (different dates, with different flaws)

At the moment, meta information about the theme (in the theme file) absent.
It is not possible to understand what kind of theme it is (point 1), and which version (point2), only by the filename.

By meta information, I represent

internal theme name/title),
version/release date
compatible with the qbittorrent version (4.23/4.30/4.50 etc.)
flag: dark/light/universal/other,
author
contact information/uri
optional comment * optional (with a large seal for the future) - part of the graphic preview/logo (so as not to restart qbit; for visual association)

It would be nice if meta information was displayed in the interface next to the topic selection path (or something like that).

Originally created by @b-user on GitHub (Dec 24, 2022). ### Suggestion Add fields to the theme to store meta information. Add the meta information display to the user interface. ### Use case Using UI, the user can identify the origin, version (etc.) of the theme. at the moment, there are difficulties and confusion with this. ### Extra info/examples/attachments At the moment, github has 1. a dozen theme with the same content, but different names 2. different versions of one theme (different dates, with different flaws) At the moment, meta information about the theme (in the theme file) absent. It is not possible to understand what kind of theme it is (point 1), and which version (point2), only by the filename. By meta information, I represent * internal theme name/title), * version/release date * compatible with the qbittorrent version (4.23/4.30/4.50 etc.) * flag: dark/light/universal/other, * author * contact information/uri * optional comment * optional (with a large seal for the future) - part of the graphic preview/logo (so as not to restart qbit; for visual association) It would be nice if meta information was displayed in the interface next to the topic selection path (or something like that).

deekerman added the

Feature request

Themes

labels

2026-02-22 00:44:19 -05:00

deekerman commented

2026-02-22 00:44:25 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 25, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 25, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**