Bugzilla – Full Text Bug Listing
| Summary: | [editor] handle multi-line status messages in header | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Thomas Ehrnhoefer <thomas.ehrnhoefer> | ||||
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> | ||||
| Status: | CLOSED MOVED | QA Contact: | |||||
| Severity: | trivial | ||||||
| Priority: | P4 | CC: | shawn.minto, thomas.ehrnhoefer | ||||
| Version: | 3.4 | Keywords: | helpwanted | ||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Thomas Ehrnhoefer
The tasks framework does not generally limit summaries to a single line. Connectors can specify the corresponding attribute type if a repository supports multi-line summaries. Do you have a concrete example for a repository that allows that? (In reply to comment #1) > The tasks framework does not generally limit summaries to a single line. > Connectors can specify the corresponding attribute type if a repository > supports multi-line summaries. Do you have a concrete example for a repository > that allows that? It's actually the editor header message, not the summary. Sorry, I do not know what the header message is. Can you attach a screenshot? Created attachment 173941 [details]
message screenshot
Sure, here it is. (nice and red - this one doesn't have multilines)
I don't know what the mylyn internal name for that is. But it's in the task editor header, and it's a message (info or warning or error), hence I called it "header message" ;)
Thanks. Do you have an example where a multi-line error message is used or needed? As far as I know the API does support MultiStatus objects in case several messages need to be displayed (only the first is shown, others are in the tooltip). I am not sure that it's worth adding special handling for multi-line messages on the framework level since is generally not well supported by the platform, e.g. in the error log. I'll mark this as helpwanted in case anyone wants to look into this. I think I was not clear. The screenshot displays an error message, but not a multi line error message. I got that using the Thoughtworks Mingle connector. The problem here is that the first line of the message was only half visible (moved a bit to the top) and so was the second line of the message (moved to the bottom). It seems while Mylyn handles long message nicely (with the ... in between and the full message in tooltip), if the message has a line break, the display in the header gets messed. Sadly I did not take a screenshot and I can't reproduce right now. Wouldn't it make sense somehow change the error message, either just display the first line (and if there are morelines , use "..." and full message in tooltip), or just replace all line breaks with a space? > Wouldn't it make sense somehow change the error message, either just display the
> first line (and if there are morelines , use "..." and full message in tooltip),
> or just replace all line breaks with a space?
Yes, that makes sense to me. I am just not sure whether we need to provide support on the framework level or if this should be handled by the connector providing the error status.
(In reply to comment #7) > > Yes, that makes sense to me. I am just not sure whether we need to provide > support on the framework level or if this should be handled by the connector > providing the error status. I don't know either. I only saw the problem on one connector, so maybe a wontfix for now. 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 |