Talk:Summit II: Difference between revisions
| Line 4: | Line 4: | ||
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>. | 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? | What does this Pipeline Browser representation show? | ||
| Line 20: | Line 21: | ||
[[Image:Browser_straight_pipeline.png]] | [[Image:Browser_straight_pipeline.png]] | ||
===Conclusion=== | |||
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. | 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. | ||
--[[User:Hollywood|David]] 15:30, 28 March 2006 (EST) | --[[User:Hollywood|David]] 15:30, 28 March 2006 (EST) | ||
Revision as of 15:41, 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.
The Test
What does this Pipeline Browser representation show?
To me, it logically represents this filter graph:
What does this Pipeline Browser representation show?
To me, it shows this filter graph:
Conclusion
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)
