ParaView 3 Telecon 10/17/2006 1PM EST
| Item | People | Description |
|---|---|---|
| 1 | Moreland | Action Items |
| 2 | Moreland | IEEE Vis Mini-summit |
| 3 | Moreland | November Summit |
| 4 | ETI | Docking windows to tabs/Qt 4.2 |
| 5 | Moreland | New Object View |
| 6 | Moreland | Changing a filter's input |
| 7 | Wylie | Lookmarks vs. Custom Filters |
| 8 | Moreland | Selection, filter parameters, and pipeline changes |
| 9 | All | Roundtable |
Discussion
IEEE Vis Mini-summit
It is agreed that we will meet at Vis on Wednesday @ 1:00
November Summit
Plans have changed a bit. We decided to have at Kitware after all so that we may talk to the extended Kitware family rather than just the two Kitware folks planning on travelling to ETI. The meeting will be held on November 29th and 30th. Agenda coming soon.
Changing a filter's input
Right now there is no way to change the inputs of filters. The reason is that there are some limitations of the way you change inputs in ParaView 2 now. We would like an improvement. We spent some time talking about potential improvements to this mechanism.
We came to some agreement that the mechanism should be similar to ParaView 2 in that there is some sort of chooser box like functionality in the object inspector that allows you to change the input. There is some contention about whether the list should be a simple list showing only valid inputs (like in ParaView 2) or if it show the entire pipeline with invalid inputs grayed out. The latter might be easier to find, but will be necessarily larger and it may quickly get too big to fit well in the UI.
Do to this issue and the fact that we may be short on time till the ParaView 3 released, we decided to punt and basically do the simple list of applicable filters only like in ParaView 2. The only difference is that multi-input filters will also be selected. For multi-input filters, we will use a QListView (or QListWidget) to select multiple inputs. This is also like ParaView 2 except you will be able to change the input at any time.
Out of time
Because we ran out of time (and our teleconferencing equipment crashed), we deferred the rest of the topics to the Technical Meeting 10/19/2006.
