<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>This looks like a much better design. Here are some further suggestions.</div>
</div>
</div>
<ul>
<li>I am worried that only combining messages that are reported one after another (with no error in between) will not be aggressive enough. A lot of errant events span two or more error messages, and these messages may be in a loop. You won't catch the duplicates
if you are only looking for similar errors spawned one after the other. Perhaps the output window can listen to the undo/redo stack and combine all similar messages issued between events in the undo/redo stack.</li><li>The filter mechanism does not make much sense to me. It's too complicated, too different from every other application I've ever used, and doesn't seem to have much value. My recommendation is on the first pass to simply not implement any filtering. Once
the verbosity improvements are made, I expect the output list to be short enough to be not worthwhile to filter. If you do want to implement filtering, I would change the "Filter All" pulldown menu with a simple toggle button that turns warning and debug message
on and off. I would change the right-click functionality with a line edit widget that, when text was typed in, to show only messages that match the given text.</li><li>There should be a way to easily export errors to text with details so users can post them to the mailing list. One or more of the following should be available: select rows of the table and copy-paste to text; have a text view that shows the output in the
old text verbosity; have an export button that saves the errors to a file.</li></ul>
<div>-Ken</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Dan Lipsa <<a href="mailto:dan.lipsa@kitware.com">dan.lipsa@kitware.com</a>><br>
<span style="font-weight:bold">Date: </span>Monday, January 19, 2015 at 9:42 AM<br>
<span style="font-weight:bold">To: </span>ParaView Developers List <<a href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>><br>
<span style="font-weight:bold">Subject: </span>[EXTERNAL] [Paraview-developers] Output Window Redesign<br>
</div>
<div><br>
</div>
<div>
<div>
<div dir="ltr">Hi all,
<div>We are redesigning the output window for ParaView and we would like your feedback.</div>
<div>Here is (roughly) how we see the new output window.</div>
<div><br>
</div>
<div><a href="http://www.paraview.org/Wiki/Output_Messages_Window">http://www.paraview.org/Wiki/Output_Messages_Window</a><br>
</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Dan</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
</span>
</body>
</html>