19 Jul
2012
19 Jul
'12
11:03 p.m.
I think it has an obvious application in software architecture
visualization.
It's called drill down and people like it.
You select a dependency between two packages.
The you zoom in (drill down) and you see the two classes that are
actually in dependency.
Drill down, you see the method invocation and the 2 methods
Drill further down, you see the actual instruction in the calling method
[drill down even more and you see the bit code of the compiled method ?
;-) ]
One could also use it to navigate in the code:
Take a variable declaration, zoom in it's type and you open the class
declaration, zoom in the class and you see it's components, ...
May be it is not so much a good idea here, because zooming in makes you
going up and down abstraction levels (from variable to class, to its
components, to an other class, ...)
I'd better go to sleep
nicolas
On 19/07/12 22:33, Alexandre Bergel wrote:
Hi!
I've just found this video:
http://cel.inf.usi.ch/index.php?action=gallery
I am not sure I really want to program a tetris that way, but the tool they have is
interesting. It intensively use zooming in and out. When you zoom in, you see different
objects and when you zoom out they disappear or they change their visual representation.
For Roassal, we are thinking about adding new graphical elements when a particular height
of the camera is reached. The elements will then disappear when the camera is getting
altitude. However, it looks a bit simple in my opinion. Is there any compelling scenario
for a better mechanism?
Is there anything else you guys want to see in this zooming ability?
Cheers,
Alexandre