https://bugs.kde.org/show_bug.cgi?id=406779
Bug ID: 406779
Summary: Do not filter out backends as missing, they may just
need proper configuration
Product: cantor
Version: 19.04
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: fil...@kde.org
Reporter: jsar...@gmail.com
CC: alexander.se...@web.de, alexanderrie...@gmail.com
Target Milestone: ---
I would strongly recommend against filtering out missing backends at cantor
startup (talking about the prompt that appears when no default backend has been
set). This is a matter of usability, mostly important for new users trying
cantor:
- A new user may want to configure Cantor to use e.g. Octave (This applies to
anyone, but will use Octave as an example, because it's what happened to me)
- System's Octave version may be old, so the user install it easily e.g. via
flatpak
- Now the user opens Cantor, but Octave is not one of the options.
- This sets the impression that Octave is not supported.
- However, the truth is that Octave just needs proper configuration.
- The way to configure it currently is by choosing any of the available
backends and go to Cantor settings to adjust those for Octave.
- I propose to improve usability here by presenting all backends without
filtering.
- If the selected backend is not properly configured (e.g. Octave), its
settings should be opened, so the user can set them right.
[ moved to become a specific bug from
https://bugs.kde.org/show_bug.cgi?id=406684 ]
--
You are receiving this mail because:
You are watching all bug changes.
