public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Berek" <berek@usa.net>
To: <sourcenav@sources.redhat.com>
Subject: SN Printing Under WIN/NT
Date: Wed, 04 Oct 2000 13:27:00 -0000	[thread overview]
Message-ID: <005501c02e41$70241a20$7113a8c0@concord.com> (raw)
In-Reply-To: <4.2.0.58.20001004102624.00dad380@pop.cygnus.com>

Lot's of problems printing hierarchy and cross reference charts under NT. I
have SN installed on 1/2 dozen PC's. Some use Postscript drivers, others
PCL, some use both. All have same results printing on 1/2 dozen networked
printers. Basically, printing is garbled: letters, symbols, and lines
overlaying each other. Have to resort to doing NT alt-print screen and
pasting into MS Word, then printing from Word.

In Class view, C++ class members that are "private" have symbol (transparent
diamond) for "public". Private members should have no symbol at all. Both
public and private have the public symbol.

I'm concerned about comments made by SN Development (Syd Polk?) about
priority given to Perl parser. I know of more than 1/2 dozen companies in my
area that have been forced to scale back use of SN because of many problems
with C++ parser: 3Com, Lucent, Cienna, Concord Communications, Broadband
Access Systems, Cisco, Fidelity... Unless C++ parsing bugs are fixed, SN
cannot be relied upon as a development tool. We desparately need accurate
cross references. Those of us that us SN are forced to fall back on grep's.
Please review your priorities.

Tx
Steve Dow

----- Original Message -----
From: "Syd Polk" <spolk@redhat.com>
To: <sourcenav@sources.redhat.com>
Sent: Wednesday, October 04, 2000 13:27
Subject: RE: Source navigator roadmap, features list, etc.?


> At 04:02 PM 10/3/00 -0700, Mo DeJong wrote:
> >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.
>
> I think that we should have a checkbox on the directory selection dialog
> that says "Live directory". If this is checked, the directory will be
> scanned every time the project is refreshed.
>
>
> Syd Polk spolk@redhat.com
> Engineering Manager +1 415 777 9810 x 241
> Red Hat, Inc.
>
>
>
>

  reply	other threads:[~2000-10-04 13:27 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Thomas>
     [not found] ` <Heller's>
     [not found]   ` <message>
     [not found]     ` <of>
     [not found]       ` <"Mon,>
     [not found]         ` <20>
     [not found]       ` <"Wed,>
     [not found]       ` <"Fri,>
     [not found]         ` <15>
     [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]               ` <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
2000-10-04 10:25                       ` Syd Polk
2000-10-04 13:27                         ` Berek [this message]
2000-10-04 15:27                           ` SN Printing Under WIN/NT 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
     [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
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
     [not found] <Pine.SOL.3.91.1001005110411.28967A-100000@cse.cygnus.com>
2000-10-05 13:07 ` SN Printing Under WIN/NT Berek
2000-10-05 13:28   ` Mo DeJong
2000-10-05 13:49     ` Berek
2000-10-05 14:06   ` Ben Elliston
     [not found] <Rouviere,>
     [not found] <Syd>
     [not found] <William>

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='005501c02e41$70241a20$7113a8c0@concord.com' \
    --to=berek@usa.net \
    --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).