Ivan Reese
Ivan Reese
Ivan Reese
Ivan Reese
Kartik Agaram
wtaysom
08/02/2019, 7:51 AMKartik Agaram
shalabh
08/02/2019, 8:30 AMwtaysom
08/02/2019, 8:49 AMogadaki
08/02/2019, 11:22 AMogadaki
08/02/2019, 11:22 AMogadaki
08/02/2019, 11:24 AMogadaki
08/02/2019, 11:25 AMogadaki
08/02/2019, 11:28 AMogadaki
08/02/2019, 11:34 AMogadaki
08/02/2019, 11:38 AMogadaki
08/02/2019, 11:41 AMogadaki
08/02/2019, 11:44 AMshalabh
08/02/2019, 4:41 PMGarth Goldwater
08/02/2019, 8:11 PMalltom
08/03/2019, 3:39 PMshalabh
08/03/2019, 4:39 PMalltom
08/03/2019, 4:45 PMalltom
08/03/2019, 9:30 PMIvan Reese
Instead of picturing a filter as pulling matching items out of the list, we bring them forward pushing the non-matching items back. From one point of view, it's the normal, filtered list. From another, literally from the side, you can see the distribution of matches. Are they all in the middle? Periodic? Erratic?
[...]
One view that's really nice for imperative programming is to line up all the steps that modify a variable along a horizontal with the immediate context for each modification shown above and below the assignment.That sounds very similar to how I'm planning to handle a few common features such as find & replace, showing all call sites of a function, and even viewing function definitions via their call sites. I'd use multiple cameras to render different parts of the 2d code plane, stacking the views from those cameras at different depth layers vaguely like a "card" interface, to make it quick to flip between different locations in the code. This is similar to what you get with conventional windows/tabs, but by putting things together in the same space you can draw dynamic connections between them and play with the in-between depth space. It's neat to think about leveraging depth for a timeline view, though it butts up against two of my constraints — the "human-scale" sense of time will sometimes mean showing thousands of events from many different objects all at once; and the default timeline GUI is something like 2000x100 pixels big. Not sure what ideas I could adapt from William that'd fit within these constraints, but feel free to make suggestions. @shalabh and @ogadaki offered a bunch of excellent ideas for visualizing things, many of which I already plan to do in the main editor view — but they are visualizations that integrate or aggregate across time rather than differentiate to distinguish the moment-to-moment changes. @Garth Goldwater said
the leisure programming environment has a bunch of ideas—if no one has them at hand i can look harderI've never heard of this, and I'd love a link if you can find it, Garth. (You should throw it in #C5T9GPWFL in case anyone else is interested.) Thanks again for the thoughts. More are welcome. If I've done a bad job of articulating my problem and you are interested in understanding it better, please let me know and I can post some drawings or something.
ogadaki
08/05/2019, 11:08 AMogadaki
08/05/2019, 11:17 AMit butts up against two of my constraints — the "human-scale" sense of time will sometimes mean showing thousands of events from many different objects all at onceMaybe you will have to use some integrate/aggregate kind of view? Then you will have to decide the way you or the user choose the range in the event sequence on wich you integrate/aggregate for each view. Arbitrary steps and ranges (say every 50 events, [1,50] then [51,100]) may be poor at catching particular patterns (especially if a pattern happens on two successive ranges).
wtaysom
08/05/2019, 4:09 PMGarth Goldwater
08/05/2019, 6:21 PMGarth Goldwater
08/05/2019, 6:21 PMGarth Goldwater
08/05/2019, 6:21 PMGarth Goldwater
08/05/2019, 6:22 PMshalabh
08/05/2019, 6:29 PMogadaki
08/05/2019, 8:07 PMshalabh
08/06/2019, 2:23 AMalltom
08/06/2019, 3:29 PMIvan Reese