You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
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
It would be nice if meta information was displayed in the interface next to the topic selection path (or something like that).
The text was updated successfully, but these errors were encountered: