public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: "'insight@sources.redhat.com'" <insight@sources.redhat.com>,
	Jim Ingham <jingham@apple.com>
Subject: Port to GTK+ and GNOME
Date: Tue, 03 Dec 2002 12:17:00 -0000	[thread overview]
Message-ID: <3DED13C9.9070506@redhat.com> (raw)

Dear Insight developers and friends,

With the increasing acceptance of GTK+ and GNOME in many *ix systems, 
Insight may have to follow the pack and become more consistent with the 
GNOME look-and-feel and somehow migrate to use GTK+ in some form.

There are currently 3 different possible approaches:

1) Use gnocl (loosely modeled after TK)
2) Use tcl-gtk (just wraps GTK, or any other GObject based library)
3) add a GTK+ port to TK itself

All of these approaches have their merits and there are trade-offs among 
them.  I wonder if some of you haven't given any thoughts already to 
this and perhaps, have used any of these packages mentioned in 1 and 2, 
know the developers, what the prospects are etc. (these projects are 
still to release -- all they have are betas at the moment).

A GTK port of TK (as we currently have the Win32 and "Unix" variants) 
would make automatically all Tcl/Tk programs to use GTK (and some GNOME 
widgets like the file chooser).  But I wonder how much of the 
look-and-feel of GNOME would we get, as it would be still Tk on top 
(probably more of the look than the feel).

There is also the problem of implementation --  there is no clear API 
interface between these Tk layers. The process was not documented either 
(done by Sun, ages ago).  The magic seems to be done by changing the Tk 
callbacks to some windows or unix specific functions in the windows or 
unix subdirectories (only one of the two is configured) but there is 
little common ground between what was done for one and the other.  It 
will probably require a very good TK internals knowledge.


Things that we must discuss, besides the maintainability issues related 
to using one of the packages 1 and 2, are the effort required to 
complete the task.  We don't have many developer hours to do this as we 
all seem to be very busy with our other affairs.

We will probably want to coordinate with other Tcl?Tk open source 
projects (like Source Navigator, Red Hat Database Administrator etc.) so 
that we do not waste efforts going in opposite directions.


Please take some time to think about this and speak your minds.  The 
future of Insight may depend on this.


Regards to all,
Fernando



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

             reply	other threads:[~2002-12-03 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 12:17 Fernando Nasser [this message]
2002-12-03 13:02 ` Ian Roxborough
2002-12-03 15:22   ` Fernando Nasser
2002-12-03 16:06     ` Ian Roxborough
2002-12-16 13:22 ` Mo DeJong
2002-12-16 18:22   ` Fernando Nasser
2002-12-17 14:19   ` Fernando Nasser
2002-12-19  0:55     ` Mo DeJong

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=3DED13C9.9070506@redhat.com \
    --to=fnasser@redhat.com \
    --cc=insight@sources.redhat.com \
    --cc=jingham@apple.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).