[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ui-best-practices-working-group] Question regarding error notification in editors
|
Hi, Eitan.
I believe the guideline is out of date.
Prior to Eclipse 3.0, problems indeed appeared in the tasks view. Starting with Eclipse 3.0, markers with a marker type of problem moved to the problems view. [1].
In Eclipse 3.4, a generic markers view was introduced for those who preferred the old style. [2].
From a guideline point of view, it probably makes sense to change this to say "Problems view." From an implementation point of view, it's best to mark the resource with a problem marker, knowing it will show up in whichever view the user chooses.
susan
[1] http://wiki.eclipse.org/FAQ_Why_don%27t_my_markers_show_up_in_the_Tasks_view%3F
[2 ]http://update.eclipse.org/downloads/drops/R-3.4-200806172000/whatsnew3.4/eclipse-news-part1.html
"Kurejwowski, Eitan" ---01/26/2010 11:24:14 PM---Hi guys, I came across this guideline:
![]()
| ![]()
| ![]()
To: "ui-best-practices-working-group@xxxxxxxxxxx" <ui-best-practices-working-group@xxxxxxxxxxx>
cc:
Subject: [ui-best-practices-working-group] Question regarding error notification in editors |
Hi guys,
I came across this guideline:
Guideline 6.29
Use the Task view to show errors found when the Save command is invoked.
http://wiki.eclipse.org/User_Interface_Guidelines#Error_Notification
Is this a mistake? Shouldn’t we use the Problems view for error notification instead of the Task view?
Best Regards,
Eitan_______________________________________________
ui-best-practices-working-group mailing list
ui-best-practices-working-group@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ui-best-practices-working-group


