public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: insight@sources.redhat.com
Subject: Phasing out of tix
Date: Fri, 20 Oct 2000 09:53:00 -0000	[thread overview]
Message-ID: <39F0786C.83144FFC@cygnus.com> (raw)

Here is a list of the currently used tix Widgets, the current favorite candidate for
replacing it and the files affected.

By far the most difficult (and perhaps with more controversial replacement option) is the
tixTree that shows up in the Local ad Watch Windows.  Feel free to suggest alternatives,
but hurry.

I will be doing it as a background task.  If someone wants to help just let me know 
so we don't work on the same thing.

I have a close attachment to the Tree thing, so I would like to do it myself.
But it is not a closed deal as I have too many things on my plate already.
This will be the last one as we may use the BLT hierbox and in this case we want to
add BLT to the sources as we remove tix (so we don't grow it much).

I will also add a iwidgets::disjointlistbox to the Register Window to allow
selecting/hidding multiple registers and the new KOD window will use the
iwidgets::scrolledhtml that is already currently used by the Help Window.


Here is the list:


tixScrolledListBox	iwidgets::scrolledlistbox	stackwin.itb process.itb
							actiondlg.tcl tracedlg.tcl

tixScrolledWindow	iwidgets::scrolledframe		bpwin.itb regwin.itb

tixScrolledText		iwidgets::scrolledtext		tdump.tcl

tixLabelFrame		iwidgets::labeledframe		tracedlg.tcl

tixControl		iwidgets::spinint		globalpref.itb srcpref.itb

tixMeter		iwidgets::feedback		download.itb

tixTree			BLT::hierbox			variables.tcl







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

                 reply	other threads:[~2000-10-20  9:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=39F0786C.83144FFC@cygnus.com \
    --to=fnasser@cygnus.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).