Actually, I don't really understand this one—in general, I'm a fan of GraphViz (Prefuse?), but in this case, the interface seems not to offer any new information; it seems to just be an unscalable rehash of the current system. What happens when you try to display an actual game? I've never seen a finished game with less than 20 objects, and I've never seen an event which had about three non-code DND tiles. This presentation just won't work for real games.
That said, the interface could be effectively used to display inter-resource dependencies. For instance, if it showed "Objects" -> (Group name)* -> (Object name) -> (Script name)*, that would be mostly tractable (as long as you had to click a group to make it the root and display its objects). It would also be useful for people when they wanted to change the behavior of a script—especially if you could filter by script name.
The same can be said for most combinations of resources. It'd be easier to bundle resources into loadable/unloadable packages if you could quickly see what all references them.
Showing actual code, though, just won't scale.
JDI exports expressions
as trees, not whole pieces of code. A complicated expression looks like this
An entire script would not be fun or easy to navigate in this form. I'll be adding that capability for my own debugging purposes, but it's not something we really want to hand users.