A proposel to gui desing- and error-processing

Registered by Florian Busch

Good morning sirs and sires,

Since I'm a big fan of ububtu and... bla... to be concrete:

1. Error button within the gui as a feature of all alpha and beta software (and optional for main releases)
 - to specify errors right after/during their occurance AND set a marker for (potential) crashs (autorepair, etc. bla bla)

2. A comment function for gui-elements of ALL (supported) software.
 - do some point-hold-move-letgo around (the) concerned gui-element(s). and add your comment...

I'm writing something similar, for a project of mine, but I don't like submitting stuff that is not appretiated/wanted/requested/used/blabla...

Ideas, comments, hints?

P.S.: I'm not used to open-source development, so just punch me in the face, if I'm not following the jedi-codex ;)

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.