<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
it is possible to have a dockable panel? And if you hide the panel
and new messages are printed a warning icon will blink in the corner
of the main window of paraview.<br>
<br>
see attached image.<br>
<br>
Felipe<br>
<br>
Le 19/01/2015 19:13, Scott, W Alan a écrit :<br>
<span style="white-space: pre;">><br>
> I also like the design proposed. Also, the ability to
combine messages will be a godsend, and is exactly what we need.<br>
><br>
> <br>
><br>
> Regarding Kens comments below, I wouldn’t change one word.
Perfect. Especially regarding his first bullet.<br>
><br>
> <br>
><br>
> Alan<br>
><br>
> <br>
><br>
> *From:*Paraview-developers
[<a class="moz-txt-link-freetext" href="mailto:paraview-developers-bounces@paraview.org">mailto:paraview-developers-bounces@paraview.org</a>] *On Behalf Of
*Moreland, Kenneth<br>
> *Sent:* Monday, January 19, 2015 10:37 AM<br>
> *To:* Dan Lipsa; ParaView Developers List<br>
> *Subject:* [EXTERNAL] Re: [Paraview-developers] Output Window
Redesign<br>
><br>
> <br>
><br>
> This looks like a much better design. Here are some further
suggestions.<br>
><br>
> · 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.<br>
><br>
> · 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.<br>
><br>
> · 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.<br>
><br>
> -Ken<br>
><br>
> <br>
><br>
> *From: *Dan Lipsa <<a class="moz-txt-link-abbreviated" href="mailto:dan.lipsa@kitware.com">dan.lipsa@kitware.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:dan.lipsa@kitware.com"><mailto:dan.lipsa@kitware.com></a>><br>
> *Date: *Monday, January 19, 2015 at 9:42 AM<br>
> *To: *ParaView Developers List
<<a class="moz-txt-link-abbreviated" href="mailto:paraview-developers@paraview.org">paraview-developers@paraview.org</a>
<a class="moz-txt-link-rfc2396E" href="mailto:paraview-developers@paraview.org"><mailto:paraview-developers@paraview.org></a>><br>
> *Subject: *[EXTERNAL] [Paraview-developers] Output Window
Redesign<br>
><br>
> <br>
><br>
> Hi all,<br>
><br>
> We are redesigning the output window for ParaView and we
would like your feedback.<br>
><br>
> Here is (roughly) how we see the new output window.<br>
><br>
> <br>
><br>
> <a class="moz-txt-link-freetext" href="http://www.paraview.org/Wiki/Output_Messages_Window">http://www.paraview.org/Wiki/Output_Messages_Window</a><br>
><br>
> <br>
><br>
> Thanks,<br>
><br>
> Dan<br>
><br>
> <br>
><br>
> <br>
><br>
><br>
><br>
> _______________________________________________<br>
> Powered by <a class="moz-txt-link-abbreviated" href="http://www.kitware.com">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at
<a class="moz-txt-link-freetext" href="http://www.kitware.com/opensource/opensource.html">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Search the list archives at:
<a class="moz-txt-link-freetext" href="http://markmail.org/search/?q=Paraview-developers">http://markmail.org/search/?q=Paraview-developers</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
>
<a class="moz-txt-link-freetext" href="http://public.kitware.com/mailman/listinfo/paraview-developers">http://public.kitware.com/mailman/listinfo/paraview-developers</a></span><br>
<br>
<br>
- -- <br>
Felipe Bordeu Weldt<br>
Ingénieur de Recherche<br>
- -------------------------------------<br>
Tél. : 33 (0)2 40 37 16 57<br>
Fax. : 33 (0)2 40 74 74 06<br>
<a class="moz-txt-link-abbreviated" href="mailto:Felipe.Bordeu@ec-nantes.fr">Felipe.Bordeu@ec-nantes.fr</a><br>
Institut GeM - UMR CNRS 6183<br>
École Centrale Nantes<br>
1 Rue de La Noë, 44321 Nantes, FRANCE<br>
- -------------------------------------<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1<br>
<br>
iQEcBAEBAgAGBQJUvhL+AAoJEE/fMfNgU9/D0CcIAKS3VcLDrr0T7UyDnbWYhElx<br>
6Ey2yywjzUJC+htgmTNUxbKVdzuHrGuG6Tya7DVNWZdE0ofjS18cEgR7vI8/JJfd<br>
EwQIbKl/qKKQbiPKNXW/BBB+bI4XJrlfgys2+cAv4jXSisBA2QeAtNxaNI27Abxs<br>
hqIbDxe1G9bEhqze6L+BtKDRU+ojoFmlRktvhHUPSVjrH3PnSlJgEr+3Y0n6C5zu<br>
3Y0pOVkJQe03Qsstc9Qs9qWATPY1GFMsl80c7XHGBU13Ak9xweb9JAdjdA+G7ojr<br>
qRKUQ/MQZ/4WY2/BZOaJvzo6RIalDkHMtVssSc5+zdr4hWUeRO1giKFQTZtJnrc=<br>
=7Frd<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>