Re: Screen Shots

["stripe dog" <stripedog () gmail com>]

> All of yoru large nodes have the "general computer" and "microsoft"
> icons (even things like WAPs).  Is this because you don't have many
> icons, or is the support for changing those not there yet?  Also,

In the first screenshot link, it's 'cause I didn't have support for
different ones. Now everything behaves like the second screenshot link (
http://barney.gonzaga.edu/~cnevins/nmap/screenshots2.htm). While there are
still a lot of unknown devices/vendors, it's due to a lack of icon images
and not program support. I'll add more screenshots at the end of today (with
luck), and remove the old screenshots to avoid the confusion. Dang, I prolly
should have actually set up a blog...

> didn't we decide to use the big icon for the vendor and the little
> one for the device type, or am I mis-remembering?

Um, yes. Yes we did. Somehow I missed that. It's a relatively simple thing
to fix, just change some source images and a couple of variable names. Darn
it, I got attached to those nice large router and firewall icons! ;-)

> Does the application allow you to start it with an Nmap XML filename
> on the command line?  That sounds like a useful feature to have.

Um, no on 1, I agree on 2... I'll add that before releasing it.

> The toggle menu looks quite cool.

Thanks!

> Is the number of host columns based on the window size?  It probably should
be.

Yes and yes. It re-shuffles the nodes when you resize. I'd like to play with
the arrangement/spacing some more, and see what fun logical connections we
can find when I add traceroute support...

> It would be interesting to see an example of a host with lots of
> open ports (maybe 30 or so).  Also, the app should function properly
> even if a host has 128K open ports (64K UDP + 64K TCP).  It doesn't
> have to be easy to brows to a specific port on that machine, but the
> GUI shouldn't crash or screw up the rendering.

At this point, I limit the number of displayed ports so they don't extend
past the node "frame" image. When I add interactive support to the drawing
area, I'd like to have either scrolling or expansion options for the port.
At this point I don't think loading a node with a ton of ports should screw
up the rendering, but if you have a specific host you'd like me to scan and
display to test this, I'm all up for it! If not, I should eventually have
access to a spare box to set up as a host with a bunch of ports open, but
this will happen later.

> Perhaps the port list should indicate protocol ( e.g. TCP or UDP) too
> somehow.  Maybe something simple, like preceeding the UDP port numbers
> with 'U' (e.g. U135).  Or do what Nmap does and use '80/tcp' style.

Consider it done.

> It would be nice if the app could dynamically change the height and
> width of the nodes by extending the appropriate gray
> rectangle.  Then you could keep them as short/thin as necessary
> (maybe make every host in a row the same height, which is calculated
> as the longest height of any element in the row, or a set maximum
> height, whichever is lower).  Every large node on your screenshot
> page wastes vertical space because of having few open ports.

Yeah, I was thinking about how I'd implement it. Since the grey bars/frame
assembly is just a loaded image, I'll probably make each node display a
shortened frame image (no horizontal bar) and add segments of a side bar
image (to preserve some sort of bevel/shadow) until it matches the height of
the port color bars.

> It may be worthwhile to give the Nmap command line used at the top
> of the disagram.  This can be found near the top of the XML.  At a
> minimum, I think the targets should be shown.

Yes, that feature is in the PRD, I simply didn't get around to it. I'll
probably add it in a box near the top or bottom, or near the "more
information" side display that is going to be added soon.

> XML parser "misses things from time to time"?  Strange.

No, no, not the libxml - my own "parser" which reads the tag
names/attributes and builds the nodes from this. I just haven't figured out
all the format options and possible tag name/attribute combinations for
the nmap xml output, and haven't spent the time to do so.

> One more suggestion is to improve the background colors on the port
> description lists.  I realize that these are just placeholders now,
> but you might want to spend a few minutes changing them to lighter
> ones.  It is hard to read the black text on these backgrounds due to
> low contrast.  I think very light hues would look good.

Everyone's a critic (and an interior designer)... Okay, you have a point.
I'll change them :-)

Any other ideas, anyone?

-Cole


_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev