Flow coloring rather than sizing would have avoided making many of the oplets near-invisible. Probably really have to see what the coloring effect looks like - e.g. is it obvious without looking at some coloring legend that one count (or rate) is greater than another? Not clear that’s a requirement, though it seems beneficial.
On the other hand I also like the size-adjusted presentation as it can make it the value differences more readily apparent. It’s just that the current presentation seems to shrink things too much. Maybe an adjustment in the scaling algorithm would help. > On Mar 21, 2016, at 3:56 PM, Susan Cline <[email protected]> wrote: > > Thanks for your suggestions. > > Yes, I too was thinking of click + drag to focus on a specific area. > > >> On Mar 21, 2016, at 10:00 AM, Dale LaBossiere <[email protected]> wrote: >> >> Collapse/expand is good. Might be even more valuable if an app could >> somehow identify some collection of streams/oplets as being part of some >> larger concept. e.g., when one has created a utility fn that takes some >> input streams, adds some flow operations, and creates some output streams, >> it would be good to be able to collapse/expand the function’s generated >> “sub-flow”. >> >> Another mechanism that would be helpful in focusing in on a sub-region of a >> graph would be to enable defining a bounding region and then showing only >> the info in that region - i.e., left-click-drag a box. >> >> I’ve got an app in a Tuple Count view where, due to flow scaling, I can’t >> really see the oplets. There may be times when an overall zoom control >> would be desired. This isn’t one of them for me :-) I don’t want to have >> to scroll around to bring the oplets of interest into view. >> > > Would a tuple count (only color the oplet by tuple count, but not size it) + > static view help with this issue? I.e, the flow looks the same as in static > view, but the oplets are colored according to flow count?
