public inbox for
 help / color / mirror / Atom feed
From: "Emilio Riva" <>
To: "Bill Brune <bill_brune" <>
Subject: Re: Sorry, but... this project is still alive?
Date: Fri, 12 Apr 2002 00:16:00 -0000	[thread overview]
Message-ID: <> (raw)

As I said, this is a good work... anyway, it's not bug-free.
the navigator (in particular, "hyper" task)  hangs a lot of times in our
software tree, maybe for the presence of relatively complex macros... is
there a way to catch some error messages? I could post these messages to
the developers to help understanding the problem.
When you switch to another editor (gvim, scite, xemacs,...) you loose the
context menu... I'm wrong? Is there the possibility to interface an
external editor with Source Navigator? Somewhere I saw a project that
integrates gvim with cscope, that's a similar approach.


Sent by:

To:   Emilio Riva <>

Subject:  Re: Sorry, but... this project is still alive?

Hi all,

Well, for me, this tool is a boon for my development problems.  I have to
over 10 Million lines of C++ spread over some 900 directories with no real
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
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
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
> 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
> menu, configuration tools,...? And a better support for teams of
> 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
> every developer...
> I think that snavigator is a great tool, and I hope you'll find the time
> continue it's development and optimization.
> thank you,
> Emilio Riva

             reply	other threads:[~2002-04-12  7:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12  0:16 Emilio Riva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-12  7:19 Left Spin
2002-04-12  0:03 Emilio Riva
     [not found] < m>
2002-04-11  8:29 ` Randall R Schulz
2002-04-11  2:45 Emilio Riva
2002-04-11  8:49 ` irox
2002-04-11  9:25 ` Bill Brune
2002-04-11 13:53 ` Khamis Abuelkomboz

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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