[Ns-developers] Visualization library
Mathieu Lacage
mathieu.lacage at sophia.inria.fr
Mon Mar 17 09:31:47 PDT 2008
On Sun, 2008-03-16 at 22:40 -0600, Jeremy wrote:
> 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
I personally think that it would be really nice if a piece of code which
is being designed to be shipped with ns-3 could also be implemented in a
more open manner than what everyone used to do in ns2: big code drops of
fully-designed and almost finished products might be nice for the
original developers but it is much harder to digest for the ns-3
maintainers.
It seems to me that it would also make _a lot_ of sense to host an open
discussion about the feature set, architecture, and scope of such an
important piece of code for the project (if it is set to become an
official gui). And, again, posting your code as read-only early will
help others assess the scope of what you want to achieve which might
make it easier to gather momentum around a useful single tool.
> 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.
I think that it would be really useful to everyone if you used a public
repository, whatever tool you use: I am sure that a hosting solution can
be found for you which allows you to control who gets write access if
that is your worry but it sure would be pretty cool to provide a public
read-only repo of your current devel work.
> Finally, I meant to include this in my last email, but our project
> homepage is at http://toilers.mines.edu/Public/NsInspect . Again, if
thanks.
regards,
Mathieu
More information about the Ns-developers
mailing list