ParaView 3 Telecon 02/06/2007

Item	People	Description
1	Moreland	Action Items
2	All	ParaView 3.0 Deliverables - February Release Postmortem
3	All	ParaView 3.0 Deliverables - This month's work
4	Richardson	Fuzzy Icons
5	Berk	New Icons
6	Ayachit	Splitting Views
7	Ayachit	New Object View
8	Moreland	Vis papers?

Deliverables: Februrary Release

Time (Geveci)

Still a work in progress. Need to update the readers. This is something that will continue to the release. Right now the Exodus reader works. Berk is working on the pvd reader. After that there will be a few readers, but the conversion process is not that hard.

Things like plotting over time need to be integrated. That will happen this month in the plotting deliverable.

Animation (Ayachit)

Most of it is in except a few bugs that Ken put in at the last minute. There are still a few questions to resolve concerning future plans for slide strips and the like.

Volume Rendering GUI (Richardson)

This deliverable was held off due to some upcomming GUI components being desinged under the VolView project that we will leverage. Berk talked with Lisa and Amy last week. They are developing the transfer function infrastructure. Amy committed some stuff to ParaView. There will have to be some tight coupling between VTK components and GUI components.

Instead Mark fixed up some bugs concerning multiple input filters. These bugs came up after the initial implementation alowed us to think about the user interaction.

Client side delivery (DeMarle)

Last week Dave made some changes and updated the Wiki page. He made it simpler to use from the client side python script. There is one bug Dave noticed that in the process of getting the data, if you are running an algorithm that changes the data type then it can run into problems.

Linking (Stimpson)

Clint finished everything and is now working on plugins.

Deliverables: This month's work

Plotting (Ayachit)

Plots are going to move into the main view. There will be ties into last months Time deliverables. Saving and loading of plots. There is also some integration with the pipeline browser to give icons on the prefered view. There will also be hints in the server manager specification.

Color map (Richardson)

This is also going to tie in the volume rendering GUI. Mark will work with Amy on the new widgets that she is creating.

Multiple outputs (Geveci)

Need to add support for filters that have distinct, separate outputs. This comes up a lot in custom filters.

There is a question of the importance of the multiple outputs. One big use case was custom filters, but this is not a big deal anymore because lookmarks are now separate from custom filters. The other big use case is the Prism pluggin, but we could work around by using two filters instead of one. We will make some Wiki design pages, and if it's easy we will do it, if not we may punt for PV 3.0.

Selection (DeMarle)

Updated the Wiki page on selection. Want to fill out the rest of the selection types (threshold selection in histogram, frustum selection, etc.). In the stage of performing VTK filters that perform these selections and integrate into the PV GUI.

There is also the requirement to apply the selection to filters.

Plugins (Stimpson/Cedilnik)

Clint is not here today. He has started a Wiki page on the design of plugins.

Lookmarks (Stanton)

This is a continuing deliverable from last month. There has been extensive discussion in previous meetings and there are Wiki design pages.

Fuzzy Icons

We were using 22x22, but Qt moved to 24x24 in 4.2. The rescaling made them a little fuzzy.

Even when the fuzzyness was taken away, they were still hard to see. Mark will commit the changes so that we can see them. We will move to 24x24 icons.

New Icons

We are going to go with these icons.

Splitting Views

We all immediately agreed that the bar over views shoul have a pull down menu that allows you to change the view type.

After some arguments, most of us agreed that the best behavior for new views is to have the new view be empty (undefined). The view would remain blank until the user specifically selected a type of view (from the pull down menu mentioned above) or selects to view an object in the pipeline browse. When an item is selected in the pipeline browser, the preferred view for that object is created in the empty view and the object is shown in that view.