<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI Emoji";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR-CA" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Hi Utkarsh,<br>
<br>
I was wondering if there is a way to contribute to ParaView in terms of UI design and features propositions. I would really like to see ParaView evolve not just in term of performance/capabilities, but also in usability.
<br>
<br>
I understand the requirements are often aligned with performance and bug fixes, but maybe to see an actual UI design proposition would convince your customers and contributors to go forward with a redesign.
<br>
<br>
I could definitely help in making that ParaView UI 2.0 proposition, and I am sure other users would too.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif">Jonathan Borduas<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA" style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Utkarsh Ayachit [mailto:utkarsh.ayachit@kitware.com]
<br>
<b>Sent:</b> Friday, March 31, 2017 8:28 PM<br>
<b>To:</b> Jonathan Borduas <jonathan.borduas@caboma.com><br>
<b>Cc:</b> ParaView <paraview@paraview.org><br>
<b>Subject:</b> Re: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Totally agreed. The pipeline browser hasn't been updated since early ParaView 3.0 days, I'd guess a 2009. It surely can be made better. In the end, it boils down to the need and time availability. Since it works well for 80/90% of the cases,
we (and our customers and contributors) often end up prioritizing other features and bug fixes. We do offer
<a href="https://www.kitware.com/what-we-offer/#consulting">various consulting options</a>, if you're keen on getting it updated <span style="font-size:9.5pt;font-family:"Segoe UI Emoji",sans-serif">😊</span><span style="font-size:9.5pt">.</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Utkarsh<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Fri, Mar 31, 2017 at 6:00 PM, Jonathan Borduas <<a href="mailto:jonathan.borduas@caboma.com" target="_blank">jonathan.borduas@caboma.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<p class="MsoNormal">Hi Utkarsh,<br>
<br>
Thank you for your answer. As a user, especially with a complex tree, I found this unpractical. I have the reflex when searching for a filter to scroll down if the filters is "afterward".<br>
<br>
I do prefer the GitTree representation of ParaViewWeb. My opinion is that a GitTree could be the optimal representation of the pipeline.<br>
<br>
The GitKraken GitTree could be a good inspiration for a redesigned pipeline browser
<span style="font-family:"Segoe UI Emoji",sans-serif">😊</span>.<br>
<br>
Best regards<br>
<span style="color:#888888"><br>
<span class="hoenzb">Jonathan Borduas</span></span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><br>
-----Original Message-----<br>
From: Utkarsh Ayachit [mailto:<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>]<br>
Sent: Friday, March 31, 2017 2:25 PM<br>
To: Jonathan Borduas <<a href="mailto:jonathan.borduas@caboma.com">jonathan.borduas@caboma.com</a>><br>
Cc: <a href="mailto:paraview@paraview.org">paraview@paraview.org</a><br>
Subject: Re: [Paraview] Pipeline not respecting the arrow of time after changing the inputs of a filter<br>
<br>
Jonathan,<br>
<br>
The arrow is not intended to have a "top/down" direction, just a "back-to-root" direction. It can be interpreted as "ProgrammableFilter1" can be found somewhere on the main trunk.<br>
<br>
On Thu, Mar 30, 2017 at 11:21 PM, Jonathan Borduas <<a href="mailto:jonathan.borduas@caboma.com">jonathan.borduas@caboma.com</a>> wrote:<br>
><br>
> Dear ParaViewers,<br>
><br>
><br>
> I came across some weird behaviour in ParaView: We have a custom<br>
> BooleanOperation filter that have two outputs (custom ParaView build).<br>
> If both outputs are the inputs of an Append Geometry and we update the<br>
> inputs of the BooleanOperation Filter, the Append Geometry will be<br>
> moved before the BooleanOperation Filter.<br>
><br>
><br>
> I always though that if there was any dependencies in a pipeline, the<br>
> representation would respect the "arrow of time" that goes from top to<br>
> bottom.<br>
> Please look at the picture here attached (same behaviour with a<br>
> ProgrammableFilter instead of a Append Geometry).<br>
><br>
><br>
> Is my comprehension at fault here or is it a bug ?<br>
><br>
><br>
> Thank you,<br>
><br>
><br>
> Jonathan Borduas<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Please keep messages on-topic and check the ParaView Wiki at:<br>
> <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br>
><br>
> Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" target="_blank">
http://markmail.org/search/?q=ParaView</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://public.kitware.com/mailman/listinfo/paraview" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>