public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Gianandrea Rigoni <gianandrea.rigoni@libero.it>
Cc: insight@sources.redhat.com
Subject: Re: Phasing out tix
Date: Mon, 06 Nov 2000 15:43:00 -0000	[thread overview]
Message-ID: <3A074215.170F68C3@cygnus.com> (raw)
In-Reply-To: <3A04C47C.C2C9EA45@libero.it>

Gianandrea Rigoni wrote:
> 
> Hello everybody!
> 
> why phasing out Tix when it is currently mantained
> and it seems to be revamped?
> 

When this decision was made it was not.

But the real question now is the opposite: why to use Tix?

We are using itcl, and several of the Tix widgets are available
as iwidgets, what makes it more convenient for us to use.

The only widget we really need Tix for is the tixTree.  It, however, 
does not have some of the features we would like.

But we badly need a few things from BLT (like "busy") and BLT has a Tree
that seems to be more powerful that the tixTree.

We cannot have too many Tcl tools in our source tree and linked to gdb for
obvious reasons, so we opted for BLT as it is being maintained and Tix, at 
the time, was not.

I am very glad to hear that Tix is being maintained now.  Not because of
this project, but because it may be useful for other Tcl/Tk projects.

With regards to Insight, though, I don't see any reason to keep it.
If you think there are good reasons for keeping it, please let me know.

Regards,
Fernando

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

      reply	other threads:[~2000-11-06 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-05  5:10 Gianandrea Rigoni
2000-11-06 15:43 ` Fernando Nasser [this message]

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=3A074215.170F68C3@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=gianandrea.rigoni@libero.it \
    --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).