[Ns-developers] Visualization library

[Jeremy]

Sorry it took me so long to respond, it's spring break  for us and I was out
of office.

Just to clarify what we are hoping to have occur is to have iNSpect
distributed with ns-3 as a standalone piece of software. That being said,
for now we are planning on focusing on continuing development of iNSpect as
a standalone package rather than switching our version control system.
However, anyone who would like a copy of our working code, I'd be happy to
send it to you directly or if you would like to be more involved, we can
figure out a solution.

Finally, I meant to include this in my last email, but our project homepage
is at http://toilers.mines.edu/Public/NsInspect . Again, if you would like a
copy of inspect, please contact me directly rather than the link that page
provides so that you can get the latest copy rather than the original (but
stable) Toilers code for ns-2. We also have a small development site up at
http://www.google.com/group/nsinspect which includes a bit of documentation
about how to easily extend the source to get you started once you have a
working copy (the articles vary in timely accuracy).

Hope this is useful to everyone,
Jeremy Norman

On Wed, Mar 12, 2008 at 10:45 AM, Mathieu Lacage <
mathieu.lacage at sophia.inria.fr> wrote:

>
> 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.
>
>