The tree and graph view have also been two things on my mind, but my ideas around them have been to improve them, but keep them separated as they are now.
The thing that bothered me with the dependency graph was that it is IMO such an important and useful tool but it depends on graphviz, so is generally not directly available on windows by default and one has to download an ~35 mb install just to see one simple image and there is not much one can do with this image in the end. So I was looking for something that could work out of the box on all FC supported platforms, would be more simple / smaller from the package / code side and more powerful for the user. My idea and research was in to html / javascript. Googling a bit around I found there are a few projects around this, some also still based on graphviz, and I am sure it could be further extended for things like zoom, pan, group ???, cluster ???, ... (did not yet research what would be the best way to go forward).
https://github.com/mdaines/viz.js/
https://github.com/cpettitt/dagre
https://github.com/cpettitt/dagre-d3
https://github.com/cpettitt/graphlib-dot
https://github.com/gyuque/livizjs
https://github.com/bpartridge/graphviz.js
https://www.nodebox.net/code/index.php/Graph
https://code.google.com/p/canviz/ (requires graphviz? must find something that does not!)
http://visjs.org/ https://github.com/almende/vis
http://arborjs.org/ https://github.com/samizdatco/arbor
http://www.ryandesign.com/canviz/ DEMO
http://arborjs.org/halfviz/#/journey-under-the-sea DEMO
http://arborjs.org/halfviz/#/python-grammar DEMO
http://arborjs.org/atlas/ DEMO
http://theantworks.herokuapp.com/industry-report/tesla/ DEMO with also zoom and pan
http://visjs.org/examples/network/graph ... llery.html DEMO with also zoom and pan
http://www.lexmath.com/grafos/sigma/eje ... sters.html DEMO with also zoom and pan
http://stackoverflow.com/questions/7034 ... javascript
http://socialcompare.com/en/comparison/ ... -libraries
---
And about the tree view... My idea / wish (not directly connected to the dependency graph as discussed by others) was to simple add an option to make the tree view work in two different modes. the first would be to keep it as it is now, the second / new mode however would be to split the tree view in two views. In the first we would have only model related objects (basically things that are in the dependency graph) and in the second we would have all the other stuff (lets call them documents for now).