X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_LOW,TW_MJ
X-Spam-Check-By:	sourceware.org
Message-ID:	<4C781218.20004@cwilson.fastmail.fm>
Date:	Fri, 27 Aug 2010 15:29:28 -0400
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	Cygwin Mailing List <cygwin AT cygwin DOT com>
Subject:	Re: gitk unusable in cygwin-1.7.6-1 because tcltk-20080420-1 is native win32 app.
References:	<20100827182230 DOT 8007 DOT qmail AT web4111 DOT mail DOT ogk DOT yahoo DOT co DOT jp> <AANLkTinVuCaQvBs-ENXDpF5Qk6Xu4dfdrrg3rhcOspwG AT mail DOT gmail DOT com>
In-Reply-To:	<AANLkTinVuCaQvBs-ENXDpF5Qk6Xu4dfdrrg3rhcOspwG@mail.gmail.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 8/27/2010 2:33 PM, Andy Koppe wrote:
> On 27 August 2010 19:22, neomjp wrote:
>> 2. I understand that the reason to have tcltk-20080420-1 as a win32 app is
>> to have a graphical insight that does not depend on X Window.
> 
> Cygwin programs can have Win32 interfaces actually, as proven by the
> likes of rxvt, mintty, and the Xwin server itself.

The real issue is that tcltk-20080420-1 presents the GDI (e.g. native
windows) backend implementation for tcl/tk.  I was proposing that we
eventually modify our offerings so that the new (probably split up)
replacement package(s) present the X11 backend implementation instead.

It has nothing to do with whether "tcltk" is a "win32" *application* as
opposed to a cygwin one.  It's all about which interface the
application/library uses to put graphics on the screen: GDI or X11.

So far, nothing has occurred on that line AFAIK.  If it is to happen,
the current maintainer has to just pull the trigger and say "we are
going to do this". Existing maintainers of tcl/tk clients will then
adapt; until (if) that happens, nothing will change.

I think the big hangups were (a) insight (b) git (c) python-idle.
insight might actually be dead or dying, not sure.  Obviously git and
python-idle both work with X (on linux) so it's doable to convert --
just a nuisance.

--
Chuck

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -