ParaView 3 Telecon 04-08-2009: Difference between revisions
| Line 33: | Line 33: | ||
== pvserver/pvws/tws consolidation == | == pvserver/pvws/tws consolidation == | ||
The Titan Web Services (TWS) and ParaView Web Services (PVWS) are currently completely separate projects. Since there are people interested in using both at the same time, | |||
== Label vs. Name in SMXML == | == Label vs. Name in SMXML == | ||
Revision as of 12:33, 8 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
Image rendering saving seems to be working.
3.8 Release
First release candidate eminent.
Transition to git
On the week of the 19th, there will be a code freeze to transition to git.
pvserver/pvws/tws consolidation
The Titan Web Services (TWS) and ParaView Web Services (PVWS) are currently completely separate projects. Since there are people interested in using both at the same time,
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.)
