From: "Martin M. Hunt" <hunt@redhat.com>
To: Ian Roxborough <irox@redhat.com>, Keith Seitz <keiths@cygnus.com>
Cc: Insight Maling List <insight@sources.redhat.com>
Subject: Re: [PATCH/hack] Running from build dir again
Date: Thu, 20 Sep 2001 10:57:00 -0000 [thread overview]
Message-ID: <200109201757.KAA21970@cygnus.com> (raw)
In-Reply-To: <3BA8F4B6.2B79C190@redhat.com>
On the other hand, iwidgets are always distributed as part of the itcl
distribution, so does it really involve much to leave them in and use the
ones that work well? Also, have you been using the latest ones or the 3-year
old iwidgets in sources?
Martin
On Wednesday 19 September 2001 12:40 pm, Ian Roxborough wrote:
> Keith Seitz wrote:
> > On Wed, 19 Sep 2001, Ian Roxborough wrote:
> > > I've been looking at this problem from the other end, i.e. fixing
> > > IWidgets to not be so dumb. But, after some effort I think your
> > > current solution/hack is best. The long term "clean" solution would
> > > seem to center around removing IWidgets from Insight. (!?) Otherwise
> > > it will involve fixing Iwidgets.
> >
> > After using the iwidgets, I would be inclined to agree with you. Iwidgets
> > leave me as warm and fuzzy as tix.
>
> BLT to replace to Tix, BWidgets to replace IWidgets?
>
> Maybe we can replace Tix and IWidgets with BLT?
>
> Reducing the number of GUI toolkits we depend on could be seen
> as a good thing.
>
> Ian.
next prev parent reply other threads:[~2001-09-20 10:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 11:09 Keith Seitz
2001-09-19 12:03 ` Ian Roxborough
2001-09-19 12:08 ` Keith Seitz
2001-09-19 12:28 ` Ian Roxborough
2001-09-20 10:57 ` Martin M. Hunt [this message]
2001-09-20 11:01 ` Keith Seitz
2001-09-20 11:28 ` Ian Roxborough
2001-09-20 11:31 ` Keith Seitz
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=200109201757.KAA21970@cygnus.com \
--to=hunt@redhat.com \
--cc=insight@sources.redhat.com \
--cc=irox@redhat.com \
--cc=keiths@cygnus.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).