Technical Meeting 04/06/2006 1:15PM EDT: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
|- | |- | ||
| 1 | | 1 | ||
| Shead | |||
| Debug / error output & widget naming followup. | |||
|- | |||
| 2 | |||
| Geveci | | Geveci | ||
| One performance/memory issue we have in paraview is due to the fact that we are creating a lot of widgets. Essentially, we create 1 widget per property. This amounts to thousands of widgets. Is ParaQ doing the same? Or are widgets grabbed from a pool (or something similar)? Is creating thousands of widgets an issue with Qt? The problem comes from the fact that our GUI is dynamic and grows as the user creates more pipeline objects. | | One performance/memory issue we have in paraview is due to the fact that we are creating a lot of widgets. Essentially, we create 1 widget per property. This amounts to thousands of widgets. Is ParaQ doing the same? Or are widgets grabbed from a pool (or something similar)? Is creating thousands of widgets an issue with Qt? The problem comes from the fact that our GUI is dynamic and grows as the user creates more pipeline objects. | ||
|- | |- | ||
| | | 3 | ||
| Geveci | | Geveci | ||
| When does the GUI push values to the server manager? In Accept or everytime a widget changes? How are we going to handle domains? For example, when the user changes the active array, the range of the contour value widget has to be updated. In ParaView, this is done by setting a special value called "unchecked value" on the property and asking it to update all dependent domains. | | When does the GUI push values to the server manager? In Accept or everytime a widget changes? How are we going to handle domains? For example, when the user changes the active array, the range of the contour value widget has to be updated. In ParaView, this is done by setting a special value called "unchecked value" on the property and asking it to update all dependent domains. | ||
|- | |- | ||
| 4 | | 4 | ||
|- | |- | ||
| 5 | | 5 | ||
|} | |} | ||
Revision as of 20:37, 3 April 2006
Agenda
| Item | People | Description |
|---|---|---|
| 1 | Shead | Debug / error output & widget naming followup. |
| 2 | Geveci | One performance/memory issue we have in paraview is due to the fact that we are creating a lot of widgets. Essentially, we create 1 widget per property. This amounts to thousands of widgets. Is ParaQ doing the same? Or are widgets grabbed from a pool (or something similar)? Is creating thousands of widgets an issue with Qt? The problem comes from the fact that our GUI is dynamic and grows as the user creates more pipeline objects. |
| 3 | Geveci | When does the GUI push values to the server manager? In Accept or everytime a widget changes? How are we going to handle domains? For example, when the user changes the active array, the range of the contour value widget has to be updated. In ParaView, this is done by setting a special value called "unchecked value" on the property and asking it to update all dependent domains. |
| 4 | ||
| 5 |
