Two questions: 1. How do you plan to handle the scale of real-world applications, ie really deep hierarchies, really long "call stacks"? 2. Will you support actual graphs with loops at some point, or will ilographs be trees?
Two questions: 1. How do you plan to handle the scale of real-world applications, ie really deep hierarchies, really long "call stacks"? 2. Will you support actual graphs with loops at some point, or will ilographs be trees?
1) Yep, I have a plan to implement "collapsed" nodes when zoomed out of large perspectives. This is pretty straightforward when resources are nested since you can just show the parent node (and an indicator that there are children). Also, when a perspective gets too large or busy, you can always make another!
2) Trees work best in perspectives of course, but there is some support for loops (see https://app.ilograph.com/Git%2520Webhooks%2520on%2520AWS/Exe...). There's no perfect way to display generic graphs with loops, so I'm still experimenting with the algorithm to lay them out.