[Paraview-developers] [EXTERNAL] Re: Output Window Redesign
Scott, W Alan
wascott at sandia.gov
Mon Jan 19 13:13:23 EST 2015
I also like the design proposed. Also, the ability to combine messages will be a godsend, and is exactly what we need.
Regarding Kens comments below, I wouldn't change one word. Perfect. Especially regarding his first bullet.
Alan
From: Paraview-developers [mailto:paraview-developers-bounces at paraview.org] On Behalf Of Moreland, Kenneth
Sent: Monday, January 19, 2015 10:37 AM
To: Dan Lipsa; ParaView Developers List
Subject: [EXTERNAL] Re: [Paraview-developers] Output Window Redesign
This looks like a much better design. Here are some further suggestions.
* 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.
* 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.
* 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.
-Ken
From: Dan Lipsa <dan.lipsa at kitware.com<mailto:dan.lipsa at kitware.com>>
Date: Monday, January 19, 2015 at 9:42 AM
To: ParaView Developers List <paraview-developers at paraview.org<mailto:paraview-developers at paraview.org>>
Subject: [EXTERNAL] [Paraview-developers] Output Window Redesign
Hi all,
We are redesigning the output window for ParaView and we would like your feedback.
Here is (roughly) how we see the new output window.
http://www.paraview.org/Wiki/Output_Messages_Window
Thanks,
Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview-developers/attachments/20150119/d5b097ab/attachment-0001.html>
More information about the Paraview-developers
mailing list