From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] unicode input for OSX-native drawterm
Date: Sun, 4 Nov 2007 01:24:42 -0600 [thread overview]
Message-ID: <B0485A86-1378-44F7-B91D-8D20C21002F0@corpus-callosum.com> (raw)
In-Reply-To: <326364c20711031150m63a0bee9lb9ba40aaf6f5289e@mail.gmail.com>
On Nov 3, 2007, at 1:50 PM, Tom Lieber wrote:
> On 11/3/07, David Leimbach <leimy2k@gmail.com> wrote:
>> Carbon is still in Leopard. Just built the latest native drawterm
>> using it like 5 minutes ago.
>
> Yes, it's just that its days have been numbered by Apple.
and like old OS 9, it's dead.. no longer being supported or going
anywhere.
That said, we're lucky that the current drawterm code in Carbon
behaves properly: Apple does not support any GUI code or event loops
from Cocoa or Carbon in anything other than the main thread--and the
current Carbon port is a direct reflection of the X11 ports, which
let child threads create their own event loops to handle drawing: a
direct conflict w/ the current supported architecture for Carbon or
Cocoa.
I'd like to see a Cocoa front end that is launched as a separate
process. Sure you take a bit of a hit on the pass-thru, but you can
then let the Cocoa event loop do it's odd things on top of Mach and
let drawterm and other code use the Plan 9 model.
jas
next prev parent reply other threads:[~2007-11-04 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14ec7b180710291805w79dbfa72p815d72b7a0d5f134@mail.gmail.com>
2007-10-30 1:20 ` underspecified
2007-10-30 1:39 ` underspecified
2007-10-30 8:07 ` Francisco J Ballesteros
2007-10-30 8:42 ` Noah Evans
2007-11-03 15:14 ` Paul Lalonde
2007-11-03 15:23 ` David Leimbach
2007-11-03 18:50 ` Tom Lieber
2007-11-04 7:24 ` Jeff Sickel [this message]
2007-11-04 10:54 ` Charles Forsyth
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=B0485A86-1378-44F7-B91D-8D20C21002F0@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).