ParaView 3 Telecon 06-25-2009: Difference between revisions
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
| 7 || Ayachit || ParaView 3.6 Release Update | | 7 || Ayachit || ParaView 3.6 Release Update | ||
|} | |} | ||
== Axes and labeling == | |||
Our axes and labeling sucks. We should make it better. | |||
We have several implementations of axes in VTK, none work well in all cases. | |||
Berk will start a Wiki page on axes design requirements. The rest of the team should comment. Julien will be responsible for implementation. | |||
One issue with our current labels is the ability to show non-ascii characters. Super/subscripts are important. Rotation is also good. Jason Shephard has already implemented a version that uses Qt under the cover that can handle all this. | |||
== Scatter plot user interface == | |||
There was a question whether we would support multiple inputs at a time. That makes no sense, so that is (no longer) a use case. | |||
== Stronger Dashboards == | |||
That dashboard has more green lately. The random failures seem to be resolved. | |||
To enforce a green dashboard, some one (probably Dave Partika) will be responsible for monitor the dashboards and making sure developers fix their bugs. We are also thinking of a way to publicly humiliate people who break checkin rules. | |||
Berk suggests adding a task to the 3.8 deliverables to increase code coverage. | |||
Revision as of 12:46, 25 June 2009
| Item | People | Description |
|---|---|---|
| 1 | Ice | MARS/V&V Milestone issues |
| 2 | Berk | Axes and labeling |
| 3 | Julien/Utkarsh | Scatter plot user interface |
| 4 | Moreland | Stronger Dashboard
|
| 5 | Thompson | Statistics Update |
| 6 | Feng | Parallel Coordinates Update |
| 7 | Ayachit | ParaView 3.6 Release Update |
Axes and labeling
Our axes and labeling sucks. We should make it better.
We have several implementations of axes in VTK, none work well in all cases.
Berk will start a Wiki page on axes design requirements. The rest of the team should comment. Julien will be responsible for implementation.
One issue with our current labels is the ability to show non-ascii characters. Super/subscripts are important. Rotation is also good. Jason Shephard has already implemented a version that uses Qt under the cover that can handle all this.
Scatter plot user interface
There was a question whether we would support multiple inputs at a time. That makes no sense, so that is (no longer) a use case.
Stronger Dashboards
That dashboard has more green lately. The random failures seem to be resolved.
To enforce a green dashboard, some one (probably Dave Partika) will be responsible for monitor the dashboards and making sure developers fix their bugs. We are also thinking of a way to publicly humiliate people who break checkin rules.
Berk suggests adding a task to the 3.8 deliverables to increase code coverage.
