[Ns-developers] Visualization library

Jeremy jnorman at mines.edu
Mon Mar 17 13:50:40 PDT 2008


We do welcome any suggestions or comments you may have about iNSpect. To
help with this, what I did was write a quick shell script to post up to date
working copies of our code every night list by build number. This listing is
at http://alamode.mines.edu/~jnorman/toilers/inspect/

If you have any questions, please let me know.
Jeremy Norman

On Mon, Mar 17, 2008 at 10:31 AM, Mathieu Lacage <
mathieu.lacage at sophia.inria.fr> wrote:

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


-- 
Curiosity didn't kill the cat, it taught it something it didn't know before.


More information about the Ns-developers mailing list