Ideas for graphics output

Hello,

i'd like to gather some opinions for my graphical Maps
application: any suggestion is appreciated.

The are several paradigms around.
Starting from Adriano Monteiro's proposal:

http://umit.sourceforge.net/umit_proposals_2007/umit_mapper1.png

this is a very clear interface but lacks some important infos,
eg the links between routers and net-segments are not shown at
all, and this could be confusing comparing different networks.
This is solved in the Cheops-NG representation:

http://cheops-ng.sourceforge.net/images/cheops.jpg

UmitMapper describes graphically each host:

http://umit.sourceforge.net/umit_proposals_2007/umit_mapper3.png

according to me this information should pertain mostly to the
"regular" GUI (as in umit), but in the gfx output for each host
i could put in informations about the host vulnerability level
extrapolated from some db (eg CVE), latency, etc...

My aim is to let the end user choose what informations to display
for the single hosts: this could be a sort of useful filter, since
the needed information pops out and you don't have to grep through
a long nmap output.
An example is this, where different ballons pop out:

http://afterglow.sourceforge.net/screenshot3.jpg

Last but not least, every gfx element should be as limited in size
as possible; beside, uninteresting hosts could be subjected to
culling... indeed the app needs to be scalable and render anything
from a small lan to *some* big networks. Representing all the hosts
in a class B would end up in gfx bloat, a graph explosion somewhat
like protein homology representation... d'oh! this scares me down!

Two questions:

- do you think 3d visualizations like these are confusing?
http://afterglow.sourceforge.net/screenshot1.jpg
http://projects.icapsid.net/fe3d/screens.html

- what informations would you like to find for each host?

Thanks.

-- 
Francesco Pettene
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org