From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.2) In-Reply-To: <326364c20711031150m63a0bee9lb9ba40aaf6f5289e@mail.gmail.com> References: <14ec7b180710291805w79dbfa72p815d72b7a0d5f134@mail.gmail.com> <8ccc8ba40710300107k77ea48c4g4deaeb4938dea1bb@mail.gmail.com> <56a297000710300142h6962b777l2d53ae7b95d407a0@mail.gmail.com> <5D273B2B-22D7-4AFF-A7C7-E94B17A4E6D2@telus.net> <3e1162e60711030823p332b338ah2f8896ceab054204@mail.gmail.com> <326364c20711031150m63a0bee9lb9ba40aaf6f5289e@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jeff Sickel Subject: Re: [9fans] unicode input for OSX-native drawterm Date: Sun, 4 Nov 2007 01:24:42 -0600 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Topicbox-Message-UUID: e88482bc-ead2-11e9-9d60-3106f5b1d025 On Nov 3, 2007, at 1:50 PM, Tom Lieber wrote: > On 11/3/07, David Leimbach 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