From: Bill Brune <bill_brune@ltx.com>
To: Emilio Riva <Emilio.Riva@marconi.com>
Cc: sourcenav@sources.redhat.com
Subject: Re: Sorry, but... this project is still alive?
Date: Thu, 11 Apr 2002 09:25:00 -0000 [thread overview]
Message-ID: <3CB5B8D8.E3B0471A@ltx.com> (raw)
In-Reply-To: <OFEB4C67B6.B80BFBDA-ONC1256B98.002EFD1E@uk.marconicomms.com>
Hi all,
Well, for me, this tool is a boon for my development problems. I have to deal
with
over 10 Million lines of C++ spread over some 900 directories with no real
organization.
Source Nav builds a database in about 4 hours and then I don't have to care
where anything lives.
It tells me exactly what I want to know, where things are declared and where
things are implemented. and
then zaps me to them. Perfect.
I don't care for the editor, so I modified a button on the editor pane
to pop up gvim on the current file to edit it, and I fixed the
revision-control functions to check-in and out of clearcase.
The rest is perfect. The include map is something to behold (at least for my
code), and the class tree is just great.
This tool is a piece of work. Thanks to everyone.
-Bill Brune
Emilio Riva wrote:
> It's a lot of time that Sorce Navigator development seems to be stopped (no
> new releases, no news): are you still working on it? I've only found a
> SourceForge project to extend the graphic interface...
> There are a lot of little problems with actual release of snavigator:
> Project Editor don't work correctly, the cross-reference functionality
> hangs frequently with big project trees, it's not easy to extend syntax
> (i.e. like in vim or scintilla text editor)... And what about adding
> doxygen/javadoc extended comment support? And an easier way to extend user
> menu, configuration tools,...? And a better support for teams of developers
> working on the same project tree and on the same (big) server? I mean, in
> this case the cross reference database should be shared, not duplicated for
> every developer...
> I think that snavigator is a great tool, and I hope you'll find the time to
> continue it's development and optimization.
>
> thank you,
> Emilio Riva
next prev parent reply other threads:[~2002-04-11 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 2:45 Emilio Riva
2002-04-11 8:49 ` irox
2002-04-11 9:25 ` Bill Brune [this message]
2002-04-11 13:53 ` Khamis Abuelkomboz
[not found] <OFEB4C67B6.B80BFBDA-ONC1256B98.002EFD1E@uk.marconicomms.co m>
2002-04-11 8:29 ` Randall R Schulz
2002-04-12 0:03 Emilio Riva
2002-04-12 0:16 Emilio Riva
2002-04-12 7:19 Left Spin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CB5B8D8.E3B0471A@ltx.com \
--to=bill_brune@ltx.com \
--cc=Emilio.Riva@marconi.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).