|
|
| Line 1: |
Line 1: |
| =Pipeline Browser=
| | Content moved to [[Pipeline Browser Ideas]] page. |
| ==Tree View Problems==
| |
| The following image shows why we can't use just an indent for fan out in a tree view.<br>
| |
| [[Image:pipelineexample02.png]]
| |
| | |
| When only using an indent to show fan-out, both pipelines look the same to the user. Adding the split item lets the user see there are multiple outputs. The user will have to learn the meaning of the split item, but I think that is preferred to confusing the user.
| |
| | |
| ::A tree view on the mac doesn't have the little lines connecting the items as shown in the image above. This may be a reason to implement our own hierarchy view. We would also be able to use the same model for the hierarchy view and the graph view.
| |
| ::--[[User:Mark|Mark Richardson]] 15:43, 28 Mar 2006 (EST)
| |
| | |
| ==What does a hierarchy mean?==
| |
| When I look at Mark's diagram, it seems clear to me that we're asking the wrong question. Let's turn the problem around, and look at things from the user standpoint.
| |
| | |
| Take this simple test: Look at a Pipeline Browser representation, and without thinking about (code, etc.) implementation, draw the graph that it represents. Think as a <i>user</i>, not a <i>programmer</i>.
| |
| | |
| ===The Test===
| |
| What does this Pipeline Browser representation show? To me, it logically represents [http://www.paraview.org/ParaQ/index.php/Image:Browser_branch_pipeline.png this filter graph. ]
| |
| | |
| | |
| [[Image:Browser_01.png]]
| |
| | |
| | |
| What does this Pipeline Browser representation show? To me, it shows [http://www.paraview.org/ParaQ/index.php/Image:Browser_straight_pipeline.png this filter graph.]
| |
| | |
| | |
| [[Image:Browser_02.png]]
| |
| | |
| ===Conclusion===
| |
| In other words, when I look at the Pipeline Browser hierarchy, I think it naturally leads to 'indentation means connection'. If we do it this way, I think we solve several problems - the thing makes sense, and I think it's easy to understand. Of course, this comes at the sacrifice of width - large chains of filters will be 'wide', because we always indent. Remember - we decided not to indent during our design discussion, because we didn't want these things becoming wide.
| |
| | |
| To me, the 'indent means connection' design makes sense, and it makes the whole widget easier to understand. Because of this, I like it for the first rev. We can, through user testing see how long a typical pipeline becomes (how wide they become), and address that problem.
| |
| | |
| --[[User:Hollywood|David]] 15:30, 28 March 2006 (EST)
| |
| | |
| ==Alternate Views==
| |
| | |
| The following image shows an alternate hierarchy view:<br>
| |
| [[Image:pipelineexample03.png]]
| |
| | |
| The view on the left would describe the pipelines on the right. If the pipeline branches had more filters connected to them, they would form a vertical chain under each of the branching filters. I added the server icon in there to get that discussion rolling too.
| |
| | |
| --[[User:Mark|Mark Richardson]] 17:13, 28 Mar 2006 (EST)
| |
