From: khamis2@t-online.de (Khamis Abuelkomboz)
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 13:53:00 -0000 [thread overview]
Message-ID: <3CB5F7DE.2000909@t-online.de> (raw)
In-Reply-To: <OFEB4C67B6.B80BFBDA-ONC1256B98.002EFD1E@uk.marconicomms.com>
well, my logic in adding components and improving SN is based on my
needs. So I added
all the parsers (in sn-extensions) because I had to deal with those
languages, especially the
html parser. the bug fixes camed mostly for the editor, the symbol
browser and the grep
functionality (the part I work with).
As Irox mentioned, if you run into the need of failed functionality take
for you some
hours and try to add some stuff to SN. I agree, that this is not easy,
but with our
help, you should be able to do some work in this way.
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...
>
and some couple of new parsers ..
>
>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,
>
For your unluck, I don't use xref, so there will be no improvment
on xref coming from me.
>it's not easy to extend syntax
>(i.e. like in vim or scintilla text editor)...
>
Using external editors is possible in SN, it's the question how good :-)
Actually
you can specify for every language type an external editor (did you know
this?)
> And what about adding
>doxygen/javadoc extended comment support?
>
I don't work with Java. Once I get a project in java I would go and
implement the failed
components (sounds waiting for some years, so don't really wait for this
:-).
>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...
>
It's possible in SN to share the same project (one of the hidden
functionalities in SN). Just open the
project as different user. It's not real project sharing, but something
of DB-like sharing.
>
>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
>
>
--
--
Dipl.-Informatiker
Khamis Abuelkomboz
Rosenweg 124
58239 Schwerte
+49 2304 898560 (Telefon)
+49 2304 898561 (Fax)
http://khamis.oimanager.de
next prev parent reply other threads:[~2002-04-11 20:53 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
2002-04-11 13:53 ` Khamis Abuelkomboz [this message]
[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=3CB5F7DE.2000909@t-online.de \
--to=khamis2@t-online.de \
--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).