ParaView 3 Telecon 04-08-2009: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
== 3.8 Release == | == 3.8 Release == | ||
== Transition to git == | |||
== pvserver/pvws/tws consolidation == | |||
== Label vs. Name in SMXML == | |||
Not long ago we had some problems with Python scripting where many names of proxies and properties were significantly different from their label. This cause confusion, especially when transitioning between the GUI, Python scripting, and C++ code. | |||
I thought we informally agreed that all labels should be basically the same as the name with explicit spacing unless there was a good reason to do otherwise. We even talked about enforcing this in the XML parsing. However, I am still seeing new proxies and properties being added that break this rule. (I most recently noticed the AMRDualClip/Contour proxies.) | |||
Revision as of 10:10, 6 April 2010
| Item | People | Description |
|---|---|---|
| 1 | Moreland | Project Randy |
| 2 | Utkarsh | 3.8 Release |
| 3 | Utkarsh | Transition to git |
| 4 | Moreland | pvserver/pvws/tws consolidation |
| 5 | Moreland | Label vs. Name in SMXML |
| 6 | Moreland | Stronger Dashboard
|
Project Randy
Update on running on large computers.
3.8 Release
Transition to git
pvserver/pvws/tws consolidation
Label vs. Name in SMXML
Not long ago we had some problems with Python scripting where many names of proxies and properties were significantly different from their label. This cause confusion, especially when transitioning between the GUI, Python scripting, and C++ code.
I thought we informally agreed that all labels should be basically the same as the name with explicit spacing unless there was a good reason to do otherwise. We even talked about enforcing this in the XML parsing. However, I am still seeing new proxies and properties being added that break this rule. (I most recently noticed the AMRDualClip/Contour proxies.)
