Talk:Summit II: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
=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. | |||
[[Image:Browser_01.png]] | |||
To me, it logically represents this graph: | |||
[[Image:Browser_branch_pipeline.png]] | |||
I think this representation: | |||
[[Image:Browser_02.png]] | |||
Shows this filter graph: | |||
[[Image: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. | |||
--[[User:Hollywood|David]] 15:30, 28 March 2006 (EST) | |||
Revision as of 15:35, 28 March 2006
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.
To me, it logically represents this graph:
I think this representation:
Shows this filter graph:
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)
