From: Steven Johnson <sjohnson@sakuraindustries.com>
To: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Current Status of Insight
Date: Thu, 12 May 2005 21:46:00 -0000 [thread overview]
Message-ID: <428504D9.7000609@sakuraindustries.com> (raw)
In-Reply-To: <1115911019.4491.17.camel@lindt.uglyboxes.com>
Hi Keith,
Thanks for the informative reply. I suppose the question is (and this
is the right place to ask it):
1. What do the user's of Insight think about this? Is it worth it? Does
anyone really care anymore?
>At one time I considered branching, dumping all the Tcl code (assigned
>to Red Hat) and rewriting in some form of gtk (all new code assigned to
>FSF). I don't believe there is enough interest to justify this work,
>though.
>
>
2. Is there enough interest to do what you say, and attempt to create an
insight derivitave, that is assignable to the FSF? (Not suggesting
Keith do it, just gauging the interest, if it is there, then there
should be people willing to contribute to the effort (money or time or
both).)
>DDD, Eclipse CDT, xgdb (and friends) are all still options.
>
Yes they are, ive tried to use them, and even though they have some nice
fancy features, they just lack basic usability. I keep finding myself
wishing they were more like Insight. But that could just be my simple
brain. And for what its worth ive never found the MI or CL Tack a front
end over the top approach to be (a) very effective, or (b) very
reliable. I much prefered how Insight really just linked with GDB and
went from there. There is a maintained TUI in GDB, so I cant see why
there shouldnt be a maintained GUI in GDB either.
So what your really saying (if i understand your post), is the main
impediment to breathing new life into insight (apart from re-writing
large chunks) is a standard FSF assignment. Sheesh, i think that is
really weak for RedHat's part, given everything they have made out of
the work of the FSF and the GNU Licence. How hard is it to just sign it
over, they obviously dont give two tosses about it, so whats the big
deal. (But i Digress).
I am sadened by this state of affairs, because I believe Insight was a
really great part of GDB.
Steven Johnson
next prev parent reply other threads:[~2005-05-12 21:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 10:07 Steven Johnson
2005-05-12 10:13 ` Jon Beniston
[not found] ` <2636500f05051203276a294e8f@mail.gmail.com>
2005-05-12 10:29 ` Nickolay Kolchin
2005-05-12 15:17 ` Keith Seitz
2005-05-12 21:46 ` Steven Johnson [this message]
2005-05-12 22:42 ` Duane Ellis
2005-05-12 22:45 ` Duane Ellis
2005-05-13 2:09 ` Christopher Faylor
2005-05-13 2:19 ` Keith Seitz
2005-05-13 13:53 ` Steven Johnson
2005-05-13 14:05 ` Christopher Faylor
2005-05-13 14:18 ` Jon Beniston
2005-05-13 14:21 ` Christopher Faylor
2005-05-13 14:16 ` Hans W. Horn
2005-05-13 14:29 ` Christopher Faylor
2005-05-13 14:33 ` James Lemke
2005-05-14 11:14 ` Nickolay Kolchin
2005-05-17 12:51 ` Fernando Nasser
2005-05-16 22:07 ` Steven Johnson
2005-05-13 1:15 Paul Schlie
2005-05-13 8:14 Roland Schwingel
[not found] <1115992411.3092.ezmlm@sources.redhat.com>
2005-05-13 15:44 ` E. Weddington
2005-05-13 17:15 ` Christopher Faylor
2005-05-13 17:35 ` Bernhard Walle
2005-05-13 17:45 ` Christopher Faylor
2005-05-13 17:58 ` Bernhard Walle
2005-05-13 21:51 ` Fernando Nasser
2005-05-14 14:54 ` Duane Ellis
2005-05-14 17:25 ` Bernhard Walle
2005-05-17 19:38 ` Fernando Nasser
2005-05-14 22:13 Paul Schlie
2005-05-16 5:35 ` Steven Johnson
2005-05-17 19:33 ` Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18 ` Paul Schlie
2005-05-16 23:45 Paul Schlie
2005-05-17 8:26 Roland Schwingel
2005-05-17 10:18 ` Steven Johnson
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=428504D9.7000609@sakuraindustries.com \
--to=sjohnson@sakuraindustries.com \
--cc=insight@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).