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

[Feature Request] Uneditable option or field just to show information #586

Open
naokiri opened this issue Aug 26, 2022 · 2 comments
Open

Comments

@naokiri
Copy link
Member

naokiri commented Aug 26, 2022

User story

As a fcitx5 plugin developer, I want to show some information to users.

Suggested feature

I want a Option of kind not editable, and not saved or stored.

Current most easy endpoint for plugins that has UI is Options in configtool.
I'd utilize that and whenever a config has skipSave() that returns true or if it has some property like "IsNonEditable", use the StringOption-like TextField but readonly parameter is set to true.

I would use it like this to show the plugin version or library build version.
config

@naokiri naokiri changed the title [Feature Request] Static option or field just show information [Feature Request] Uneditable option or field just to show information Aug 26, 2022
@wengxt
Copy link
Member

wengxt commented Aug 27, 2022

ok, the readonly field kinda makes sense, but as a side note.. we do have "Version" field already in addon.

So in order to display version, we might want to try some different UI option. I was thinking about adding an "about" window like KDE or sth, though we don't have much to display there.

Any suggestion?

图片

taking kde's kcm as a reference

@naokiri
Copy link
Member Author

naokiri commented Aug 27, 2022

I feel that's good if plugins can add arbitrary field on it.
In my case I probably would want to show the version of the addon itself and the version of the main underlying library, so just extracting the existing version string won't be enough.

Having very plain 'about' window for default is acceptable in my opinion. Like that example even if it is just license and author it still is a meaningful default information and if plugins don't have more to add it is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants