<div>On 6/7/12 7:24 AM, Utkarsh Ayachit wrote:</div><div><br></div><div>Lawrence,</div><div><br></div><div>Very good point. I'd definitely vote posting this on the mailing list,</div><div>as I'd like to get feed back from the users/developers before we</div>
<div>decide what would be the best approach for dealing with names. A patch</div><div>is always appreciated :).</div><div><br></div><div>For other bugs you mention, yes, mantis is indeed the best approach.</div><div>For non trivial issues, after reporting the bug, if might be</div>
<div>worthwhile to post on the mailing list to raise awareness. A bug</div><div>requiring some major work is more likely to be fixed if there more</div><div>people are affected by it -- but that's totally optional. We do parse</div>
<div>over the mantis bugs periodically.</div><div><br></div><div>Utkarsh</div><div><br></div><div>On Wed, Jun 6, 2012 at 6:27 PM, Lawrence Angrave <<a href="mailto:angrave@illinois.edu">angrave@illinois.edu</a>> wrote:</div>
<div><br></div><div>Hi Utkarsh,</div><div><br></div><div>I'd be happy to post this/discuss this on the Paraview mailing list or</div><div>Paraview developer public mailing lists</div><div>- if so, let me know which one is a better fit.</div>
<div><br></div><div>Feature suggestion:</div><div> Define, document and implement a convention on how array names are</div><div>consistently mapped to script variables even when the original array name is</div><div>not a valid variable name.</div>
<div>This would affect the "Calculator" "FindData" and "Python Calculator" features (possibly more).</div><div><br></div><div><br></div><div>As a concrete example, suppose you had a point array with the name "1.1 Phase: Total (s)#2" . You would be able to reference it in a script calculation as</div>
<div>"_1_1_Phase__Total_s__2"</div><div><br></div><div><br></div><div>This could be implemented as an instance method eg "GetSanitizedName()" on vtkArray </div><div>(that returns a variable name compliant name),</div>
<div> or we leave vtk alone and implement it as a few static helper methods to be used just before variables</div><div>are referenced in client languages / or calculators.</div><div><br></div><div>Anyway, What do you think?</div>
<div><br></div><div> I'd be happy to help implement an initial first pass of this.</div><div>(It would be useful for RVA - our custom version of ParaView where we have many geologic and oil based variables we read from other packages)</div>
<div><br></div><div>Best,</div><div>Lawrence.</div><div><br></div>