public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sources.redhat.com
Subject: RE: Source navigator roadmap, features list, etc.?
Date: Tue, 03 Oct 2000 16:02:00 -0000	[thread overview]
Message-ID: <Pine.SOL.3.91.1001003155308.11471M-100000@cse.cygnus.com> (raw)
In-Reply-To: <5D2A198567EED311BD0F009027A25C87402387@SRVMAIL-ANN>

On Wed, 27 Sep 2000, William Gacquer wrote:

> Yahoo! The community rules!
> 
> More seriously, if I can give you my wishlist...
> 
> 1/ automatic recognition of new files in the project directories

Not sure about that one. Perhaps a feature to rescan for new files
would be a good idea, but it should not be automatic.

> 2/ a better interface with CVS ( why not an integration of tkCVS in SN?)

This one is a well known problem that we need to deal with.

> 3/ an expand/collapse button in the project tree view (expansion is the
> default but my project is so big that I would prefer a collapse by default)
> 4/ Drag&Drop with KDE/Gnome (I known, that's Tk's stuff)

What exactly are you itching to drop into SN? Drag and Drop is something
that seems really cool but I find to be less than useful unless it
is very consistent across applications.

> 5/ a UML-istic class view (even if it's not editable)
> 6/ clicking on xref-ed objects/functions opens the file where the
> object/function is used (by default, it opens the file a function
> implementation)

Yup, I looked into this before but I could not fix it without
a redesign.

> 7/ a clever "replace-in-files"
> 8/ an interface with GNAT (with tkGNAT?)
> 9/ a autoconf/automake project creation as in kdevelop

This one is hard to do in a general way, but we could do
something like writing a configure.in for the user in the
same way that we write a Makefile.

> 10/ a possibility to hide/show all SN-controlled windows

This is already implemented, see the Windows->Iconize Project
menu item.

> 11/ a search-and-replace dialog that can jump directly to the next occurence
> by clicking on replace
> 12/ working real-regular-expressions everywhere

The trick will be how the user can tell the system to use
a regexp vs a glob for a given entry box.

Mo DeJong
Red Hat Inc

  parent reply	other threads:[~2000-10-03 16:02 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Thomas>
     [not found] ` <Heller's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Wed,>
     [not found]       ` <"Fri,>
     [not found]         ` <15>
     [not found]       ` <"Mon,>
     [not found]         ` <20>
     [not found]       ` <"Tue,>
     [not found]       ` <"Thu,>
     [not found]         ` <3>
     [not found]           ` <Aug>
     [not found]             ` <2000>
     [not found]               ` <15:23:58>
     [not found]                 ` <-0800>
     [not found]                   ` <Mo>
     [not found]               ` <05:03:28>
     [not found]                 ` <-0700>
2000-09-15  5:06                   ` SN452 Installation Rouviere, Stephane
2000-09-15  5:24                     ` Bruce Stephens
2000-09-15 11:20                       ` Syd Polk
     [not found]               ` <18:21:47>
     [not found]                 ` <+0200>
2000-08-03  9:22                   ` Getting started with tcl Thomas Heller
2000-08-03  9:40                     ` Bruce Stephens
2000-08-03 10:19                       ` Syd Polk
2000-09-27  1:12                   ` Source navigator roadmap, features list, etc.? William Gacquer
2000-09-27 22:16                     ` Bruce Stephens
2000-09-28  9:15                       ` Berek
2000-09-28 13:26                         ` Syd Polk
2000-09-28 13:22                       ` Syd Polk
2000-10-03 16:02                     ` Mo DeJong [this message]
2000-10-04 10:25                       ` Syd Polk
2000-10-04 13:27                         ` SN Printing Under WIN/NT Berek
2000-10-04 15:27                           ` Mo DeJong
2000-10-04 16:50                             ` Paul Selormey
2000-10-04 17:04                               ` Mo DeJong
2000-10-05 12:06                           ` Syd Polk
2000-10-05 13:13                             ` Berek
2000-11-20  4:47 future plans Simone Contini
2000-11-20 12:02 ` Syd Polk
2000-11-20 15:24 ` Mo DeJong
2000-11-20 15:37   ` Timothee Besset
2000-11-21 11:02     ` Mo DeJong
2000-11-20 16:13   ` Tom Tromey
2000-11-21 12:22     ` Syd Polk
2000-11-21 12:31       ` Mo DeJong
2000-11-21 12:32       ` Tom Tromey
2000-11-21 15:18         ` Bruce Stephens
2000-11-21 15:47           ` Tom Tromey
2000-11-21 15:41         ` Syd Polk
  -- strict thread matches above, loose matches on Subject: below --
2000-10-05  1:16 Source navigator roadmap, features list, etc.? William Gacquer
2000-10-05  0:52 dave.banham
2000-10-04  0:53 leonp
2000-10-04  2:42 ` Timothy M. Shead
2000-09-29  0:26 dave.banham
2000-09-29 11:32 ` Syd Polk
2000-09-28  0:23 dave.banham
2000-09-28 13:25 ` Syd Polk
2000-09-28 17:28   ` Ben Elliston
2000-09-29  6:06     ` Bruce Stephens
2000-09-25 22:04 Timothee Besset
2000-09-26  9:23 ` Syd Polk
2000-09-26 10:30 ` Berek
2000-09-26 10:37   ` Syd Polk
2000-09-27 21:41   ` Ben Elliston
2000-10-03  9:44     ` Mo DeJong
     [not found] <William>
     [not found] <Rouviere,>
     [not found] <Syd>

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=Pine.SOL.3.91.1001003155308.11471M-100000@cse.cygnus.com \
    --to=mdejong@cygnus.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).