From: Keith Seitz <keiths@redhat.com>
To: Patrick Monnerat <Patrick.Monnerat@datasphere.ch>,
insight@sourceware.org
Subject: Re: Is the project still alive ?
Date: Wed, 25 Jun 2014 22:52:00 -0000 [thread overview]
Message-ID: <53AB5285.3020909@redhat.com> (raw)
In-Reply-To: <AB5E58B87EB73C46A38073D8F459F113D9FEA0@dataspheresrv01>
Hi, Patrick,
I wish I had an answer for you, but I don't.
I've been struggling with this very question for about a year now. It
isn't really clear to me that EOLing Insight would affect more than a
handful of people, and there are alternatives out there (Nemevier,
Eclipse-based standalone, QtCreator, Code::Blocks, ...).
Red Hat is no longer using Insight, and, as you correctly state, my time
and paycheck go to working on different projects. Contributions are
(very) few and (very) far between.
A GIT repository exists, but I have not yet pushed it to sourceware.
When I last played with this, I wasn't very pleased by the direction it
was going. It was essentially a clone of the gdb repo with the
insight/libgui bits thrown in. Yuck. [If anyone has any better ideas,
I'm all eyes/ears.]
At one time, my immediate for goal for the project was a slight/small
"reboot":
1) create GIT repo [created, not published, not happy with it]
2) NO in-tree Tcl, Tk, Itcl, Itk, iwidgets, etc. All must be provided by
the platform [or maybe on an auxiliary branch?]
3) Remove dependency on/prune libgui [TkTable is particularly troubling]
4) Linux-only first "release"; cygwin using X and mingw to follow
5) Remove all the Foundry/Code Fusion junk from the tree and
simplify/audit the codebase.
6) Formalize and make "regular" snapshots/updates/releases
I've toyed with jumping straight to a rewrite based on Tom Tromey's
python-based efforts, but it is still unclear whether that would work
well (enough?) on all the platforms I care about (Linux, MinGW, Cygwin).
That notwithstanding, I had convinced myself that I would need a
stop-gap solution until a rewrite was sufficiently advanced to be useful.
In the end, a part of me still believes that there is an audience for
Insight or something insight-like, i.e., a lightweight, *fast*, non-MI
GUI for gdb.
Keith
PS. This note has reminded me that I really should install F21 and see
where that's headed... /me installs rawhide
next prev parent reply other threads:[~2014-06-25 22:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 11:28 Patrick Monnerat
2014-06-24 17:25 ` Bruce Dawson
2014-06-25 22:52 ` Keith Seitz [this message]
2014-06-26 10:15 ` Patrick Monnerat
2014-07-22 17:18 ` Tom Tromey
2014-07-22 17:42 ` Patrick Monnerat
2014-07-22 17:46 ` Keith Seitz
2014-07-23 10:14 ` Patrick Monnerat
2014-09-04 5:54 ` Pavel Fedin
2014-09-04 8:01 ` Richard Tierney
2014-09-04 12:39 ` Fernando Nasser
2014-06-25 5:44 Roland Schwingel
2014-06-25 10:43 ` Patrick Monnerat
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=53AB5285.3020909@redhat.com \
--to=keiths@redhat.com \
--cc=Patrick.Monnerat@datasphere.ch \
--cc=insight@sourceware.org \
/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).