Technical Meeting 05/11/2006 1:15PM EDT: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
|- | |- | ||
| 1 | | 1 | ||
| Stimpson | |||
| Test framework alternatives | |||
|- | |||
| 2 | |||
| Shead | | Shead | ||
| PGraph status | | PGraph status | ||
|- | |- | ||
| | | 3 | ||
| McBride | | McBride | ||
| | | Prism over ParaQ status | ||
|- | |- | ||
| 4 | | 4 | ||
| Line 20: | Line 22: | ||
== Action Items == | == Action Items == | ||
* McBride - find out how Squish licensing would apply to the dashboard. | |||
* Stimpson - test Squish with ParaQ. | |||
* Shead - update PGraph code to store 2D data using a 2D data array. | |||
* Shead - commit PGraph code to the repository locations specified by Berk. | |||
== Discussion == | == Discussion == | ||
Clinton discussed ETI's research into commercial test frameworks for ParaQ. It has been confirmed that KDExecutor does not work with Qt 4.0 - they are apparently working on it, and expect their first 4.0 version in "a few weeks". The team agreed that this was not a good sign. In the past, ETI has also looked at "Squish", which supports Qt 4, but has significant licensing costs: $3000 per developer (i.e. create and play tests), and $400 per user (play tests). Berk reminded the team that per-user licensing for test playback affects the dashboard, not just potential Open Source contributors. | |||
Since Tim will be changing priorities from PGraph to 3D Widgets, he gave a briefing on the state of the PGraph implementation. The team discussed the rationale behind using vtkPolyData as output for the PGraph extraction filters. See [[PGraph Implementation]] for details. | |||
Corey gave an update on Prism over ParaQ. In the short-term he won't be using pqMainWindow as the Prism user interface, because pqMainWindow is tightly coupled with pqPipelineBrowser, which isn't needed for Prism. Consequently, Corey will be modifying pqProcessModuleGUIHelper so it isn't pqMainWindow-specific (a good thing to have regardless). Longer-term, Utkarsh is actively working to decouple pqPipelineBrowser from pqMainWindow. | |||
Revision as of 13:11, 11 May 2006
Agenda
| Item | People | Description |
|---|---|---|
| 1 | Stimpson | Test framework alternatives |
| 2 | Shead | PGraph status |
| 3 | McBride | Prism over ParaQ status |
| 4 |
Action Items
- McBride - find out how Squish licensing would apply to the dashboard.
- Stimpson - test Squish with ParaQ.
- Shead - update PGraph code to store 2D data using a 2D data array.
- Shead - commit PGraph code to the repository locations specified by Berk.
Discussion
Clinton discussed ETI's research into commercial test frameworks for ParaQ. It has been confirmed that KDExecutor does not work with Qt 4.0 - they are apparently working on it, and expect their first 4.0 version in "a few weeks". The team agreed that this was not a good sign. In the past, ETI has also looked at "Squish", which supports Qt 4, but has significant licensing costs: $3000 per developer (i.e. create and play tests), and $400 per user (play tests). Berk reminded the team that per-user licensing for test playback affects the dashboard, not just potential Open Source contributors.
Since Tim will be changing priorities from PGraph to 3D Widgets, he gave a briefing on the state of the PGraph implementation. The team discussed the rationale behind using vtkPolyData as output for the PGraph extraction filters. See PGraph Implementation for details.
Corey gave an update on Prism over ParaQ. In the short-term he won't be using pqMainWindow as the Prism user interface, because pqMainWindow is tightly coupled with pqPipelineBrowser, which isn't needed for Prism. Consequently, Corey will be modifying pqProcessModuleGUIHelper so it isn't pqMainWindow-specific (a good thing to have regardless). Longer-term, Utkarsh is actively working to decouple pqPipelineBrowser from pqMainWindow.
