[Ns-developers] Visualization library

[Mathieu Lacage]

On Tue, 2008-03-11 at 22:42 -0600, Jeremy wrote:

[snip]

> handle ns-2 wired traces. Currently, we are adding parsers for the
> PCAP trace format and plan to start more in-depth ns-3 wired/wireless
> parsing soon. Most of our current focus has been on finishing the
> visualization updates necessary for wired traces and updating the
> wireless visualization to a new format. We hope to have the
> visualization portion done within the next couple weeks.
> 
> Just as a note for completeness, iNSpect version 4 currently relies
> on g++ 4.1.2 and 4.2.1, gtkglext 1.2.0 (distributed with iNSpect),
> and OpenGL 2.0. Previous versions were tested on cygwin, redhat, and
> Windows XP SP2 (Using Dev C++). We plan to keep the new version of
> iNSpect at least as portable as the previous versions.
> 
> Finally, I would like to extend a warm welcome to any suggestions or
> help that we can get from the ns-3 development community to make this
> update. If you would like to assist in this effort, please contact me
> at jnorman at mines.edu (or respond to this message).

What would be potentially useful is to be able to have access to a
public repository of the code, regardless of whether the code works or
not. Being able to look at it early might help spot early problems with
the ns-3 integration, and thus save you a lot of time later down the
road.

If your goal is integration in ns-3, you will have to use mercurial, so,
it might make sense to move your repository history (if you have one) to
mercurial now to avoid the later pain.
(http://www.selenic.com/mercurial/wiki/index.cgi/RepositoryConversion
explains how to do this but if you have questions about this process, I
suspect I can probably help, feel free to drop by on
irc.freenode.net#ns-3)

I hope that this helps.

regards,
Mathieu

PS: it would also be probably useful to include a link to your project's
homepage in your email: a quick google search for "iNSpect" did not turn
up much.