From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: ATTENTION: Tcl/Tk transition
Date: Sun, 30 Oct 2011 04:54:00 -0000 [thread overview]
Message-ID: <20111030045359.GA4943@ednor.casa.cgf.cx> (raw)
In-Reply-To: <CAHiT=DG6+EGQ=q2eyexyaX0ERwAPjQNxrcSmoLjeOpuJ07VY_A@mail.gmail.com>
On Sat, Oct 29, 2011 at 06:31:59PM -0500, Reini Urban wrote:
>On Wed, Oct 26, 2011 at 5:33 PM, Charles Wilson wrote:
>> Here are some of the previous discussions:
>>
>> Interest in "native" Tcl/Tk/Expect/Itcl/... packages?
>> http://cygwin.com/ml/cygwin-apps/2004-10/msg00316.html
>>
>> Does anyone use insight on cygwin?
>> http://www.cygwin.com/ml/cygwin/2008-08/msg00089.html
>>
>> tcl/tk/expect/dejagnu/gdb/insight
>> http://cygwin.com/ml/cygwin/2009-09/msg00311.html
>>
>> gitk unusable in cygwin-1.7.6-1 because tcltk-20080420-1 is native win32
>> app.
>> http://cygwin.com/ml/cygwin/2010-08/msg00913.html
>>
>> ====NOTE====
>> in the gitk thread above, Reini Urban, the cygwin perl and parrot
>> maintainer, was vehemently against switching tcltk from GDI to X11. ?I
>> wonder if his opinion has changed in the past year...
>
>No, I'm still against it, but in minority.
>I tried to fix it, but ran out of time.
>
>Maybe later I can come up with a tk/tcl-native.
I don't see why you need a tcl-native but it should be possible to use
the Windows version of tk to do Windows-native GUI stuff without relying
on X11. The trick is getting that + Cygwin paths, signals, etc. to
play together.
cgf
next prev parent reply other threads:[~2011-10-30 4:54 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 21:02 Yaakov (Cygwin/X)
2011-10-26 21:06 ` Yaakov (Cygwin/X)
2011-10-26 21:24 ` Marco Atzeri
2011-10-26 21:29 ` Marco Atzeri
[not found] ` <1319665558.90381.YahooMailNeo@web114712.mail.gq1.yahoo.com>
2011-10-26 21:49 ` Cary R.
2011-10-26 22:22 ` Christopher Faylor
2011-10-26 22:57 ` Cary R.
2011-10-26 23:35 ` Christopher Faylor
2011-10-27 1:26 ` Cary R.
2011-10-27 4:55 ` Christopher Faylor
2011-10-26 22:33 ` Charles Wilson
2011-10-29 23:32 ` Reini Urban
2011-10-30 4:54 ` Christopher Faylor [this message]
2011-10-31 0:44 ` Yaakov (Cygwin/X)
2011-10-31 23:40 ` Charles Wilson
2011-11-01 0:24 ` Charles Wilson
2011-10-27 0:42 ` Yaakov (Cygwin/X)
2011-10-27 8:08 ` Corinna Vinschen
2011-10-28 3:11 ` Yaakov (Cygwin/X)
2011-10-28 3:55 ` Christopher Faylor
2011-10-28 7:57 ` Corinna Vinschen
2011-10-28 8:21 ` Yaakov (Cygwin/X)
2011-10-28 8:48 ` Corinna Vinschen
2011-10-28 9:34 ` Corinna Vinschen
2011-10-27 1:31 ` Dave Korn
2011-10-27 4:52 ` Christopher Faylor
2011-11-08 1:17 ` Dr. Volker Zell
2011-11-09 23:51 ` Yaakov (Cygwin/X)
2011-11-10 1:59 ` Dr. Volker Zell
2011-11-10 2:38 ` Yaakov (Cygwin/X)
2011-11-10 23:01 ` Dr. Volker Zell
2011-12-03 23:45 ` Charles Wilson
2011-12-05 0:33 ` Yaakov (Cygwin/X)
2011-12-05 2:05 ` Charles Wilson
2011-12-05 3:03 ` Yaakov (Cygwin/X)
2011-12-05 6:25 ` Charles Wilson
2011-12-05 16:15 ` Christopher Faylor
2011-12-05 5:32 ` Yaakov (Cygwin/X)
2012-01-08 1:57 ` Samuel Thibault
2012-01-08 3:36 ` Yaakov (Cygwin/X)
2012-01-08 3:47 ` Yaakov (Cygwin/X)
2012-01-10 8:07 ` Peter A. Castro
2012-01-10 14:27 ` Jason Tishler
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=20111030045359.GA4943@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-apps@cygwin.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).