Community
Participate
Working Groups
Is: If the user tries to insert content that is not allowed at the current cursor position, this attempt is silently ignored. The user has no idea why her action has no effect. Should: A hint should be shown in some unintrusive form (e.g. a slide-in dialog or in the status line), why the in question content cannot be inserted.
This kind of hint should be shown for any editing operation that is refused due to validation issues (i.e. trying to delete the content of an empty element).
There are different ways to show such hint: a) (non-modal) dialog: can not be overlooked but requires user interaction (click 'OK') b) (modal) slide-in dialog: does not block but unusual for this kind of information (which is a feedback of input by the user) c) status line easy to overlooked but non-blocking I think, the user should decide if she or he wants to have a non-modal dialog or not: non-modal dialog (a) with a check box "Do not show this dialog again" (could also be enabled/disabled in Preferences) and to show the hint in the status line (c). What do you think?
(In reply to comment #2) > a) (non-modal) dialog: > can not be overlooked but requires user interaction (click 'OK') Maybe very annoying. > c) status line > easy to overlooked but non-blocking The status line is already used for the path of the current cursor position. This information is essential for positioning the cursor to create new structures like e.g. tables. This brought me to the idea of a slide in dialog or some kind of message that fades into the UI, stays a little time and fades out again. Maybe a bubble or tooltip-like window above the cursor, like the JFace FieldDecoration.
(In reply to comment #3) > ... Maybe a bubble or tooltip-like window above the cursor, > like the JFace FieldDecoration. > +1 Good idea as long as it is associated with the cursor. Maybe we could also show if it is possible to insert text _before_ it is insert, e.g. by a greyed out cursor or/and the suffix " (empty element)" in the path in the status line.
Moved to Mylyn Docs Vex.
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
