Talk:Summit II: Difference between revisions

From ParaQ Wiki
Jump to navigationJump to search
Line 1: Line 1:
=Pipeline Browser=
=Pipeline Browser=
When I look at Mark's diagram, it seems clear to me that we're asking the wrong question.  Look at this representation.  Without thinking about implementation, draw the graph that it represents.   
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>.
 
What does this Pipeline Browser representation show?


[[Image:Browser_01.png]]
[[Image:Browser_01.png]]
Line 8: Line 12:
[[Image:Browser_branch_pipeline.png]]
[[Image:Browser_branch_pipeline.png]]


I think this representation:
What does this Pipeline Browser representation show?


[[Image:Browser_02.png]]
[[Image:Browser_02.png]]


Shows this filter graph:
To me, it shows this filter graph:


[[Image:Browser_straight_pipeline.png]]
[[Image:Browser_straight_pipeline.png]]

Revision as of 15:39, 28 March 2006

Pipeline Browser

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 user, not a programmer.

What does this Pipeline Browser representation show?

Browser 01.png

To me, it logically represents this filter graph:

Browser branch pipeline.png

What does this Pipeline Browser representation show?

Browser 02.png

To me, it shows this filter graph:

Browser straight pipeline.png

In other words, when I look at the 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. To me, this is the correct sacrifice to make, because it makes the whole widget easier to understand. I like it for the first rev.

--David 15:30, 28 March 2006 (EST)