X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,TW_SV,TW_TX
X-Spam-Check-By:	sourceware.org
Message-ID:	<4C79769B.1070102@x-ray.at>
Date:	Sat, 28 Aug 2010 22:50:35 +0200
From:	Reini Urban <rurban AT x-ray DOT at>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6
MIME-Version:	1.0
To:	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> <4C781218 DOT 20004 AT cwilson DOT fastmail DOT fm> <AANLkTinRHi3hKBViNo5bszm5=brVhLX_cpbv6eG=yT32 AT mail DOT gmail DOT com> <4C793018 DOT 7030005 AT cwilson DOT fastmail DOT fm>
In-Reply-To:	<4C793018.7030005@cwilson.fastmail.fm>
X-IsSubscribed:	yes
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

Charles Wilson schrieb:
> On 8/28/2010 10:31 AM, Reini Urban wrote:
>> 2010/8/27 Charles Wilson:
>>> Obviously git and
>>> python-idle both work with X (on linux) so it's doable to convert --
>>> just a nuisance.
>>
>> A big nuisance in my eyes.
>> Why do I have to start a xserver, when I can use native fast small GDI?
>
> Why do you have to start cygserver (for posix IPC), when you can use
> native fast small named pipes, or native fast small shared memory?

Because we don't have posix IPC semantics in native windows.

> So, the right answer is a "real" port of tcl/tk.  There are two ways to
> do this:
>
>    1) just compile it like you would on unix. Then, you get X11, not GDI
> -- but you also avoid all the other win32isms. This will "just work";
> recompile with the "correct" options and you're golden.
>
>    2) disentagle all the assumptions in the tcl/tk code between
> "windowing system" and "win32ness as it relates to non-windowing code".
> This is a BIG job, and NOBODY wants to do it.

I did it for perltk two years ago and posted the patches to the perltk 
tracker. It was a nobrainer, needed one day and was straightforward.
Tk is very well prepared for supporting windows GDI or unix X.

But I'm not interested to maintain it. And I'm not interested
to have to start startxwin for a simple tk gui.

pTk is essentially the same as Tk upstream, just portable, hence the 
name. Just two lines are problematic, using the unix event loop with 
/dev/windows should be replaced by using the native windows event loop.
pTk/mTk/win/tkWinX.c:
GetMessage() via select() on /dev/windows and callback did not work for me.
http://rt.cpan.org/Public/Bug/Display.html?id=31792

I have no idea what would be involved to try out the pTk cygwin Win32 
wish instead of the original tk wish. If anyone is concerned about our 
current tcltk path mess should try it. http://search.cpan.org/dist/Tk/
The Tk svn already has my cygwin patches in.
But I have more important things to do.

--
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 -