[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [rkward] [Bug 357375] New: Improve type checking for varslots (soft / hard)
From: Thomas Friedrichsmeier via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date: 2015-12-31 21:43:38
Message-ID: bug-357375-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=357375
Bug ID: 357375
Summary: Improve type checking for varslots (soft / hard)
Product: rkward
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: User Interface
Assignee: rkward-devel@kde.org
Reporter: thomas.friedrichsmeier@ruhr-uni-bochum.de
Summarized from discussion on mailing list:
https://mail.kde.org/pipermail/rkward-devel/2015-November/004333.html
--"Soft" warnings--
1. The warning symbol shown next to problematic objects could be repeated next
to / inside the
"Submit"-button.
1b. On pressing the "Submit"-button, there could be a warning dialog:
"Do you really want to do this?", with a "Don't ask again" option. This dialog
should specify where the problem is found (which varslot, which object/s), and
what it is (as already available per object).
-- "Hard" checks --
2. If allowing for hard checks, and in particular if we allow for hard
checks _in addition to_ soft checks, these should work by refusing the
object in question right away. Most elegant option might be by showing a
(closable but non-modal) pop-up notification.
-- Fine tuning --
3. Optional hard checking might need a little more control than a
single boolean. For instance, a plugin author might want to enforce a
hard "num_dimensions"-check, but only a soft "types"-check. So perhaps
the semantics would be hard_checks="num_dimensions classes types", with
either "num_dimensions" or "" as the default.
--
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic