Re: [MACTCL] Drop Carbon support from Tk-Aqua?

[Kevin W. <kw...@co...>]

Hi Torsten,

On 9/26/12 4:33 AM, Torsten Berg wrote:
> I am, however, a bit uneasy about the current development of Tk-Cocoa since there is no-one around to help us getting further. How many years could it take before the event loop is fixed? I see some 4-5 other bugs listed in the SF tracker that are open for years now and with no fix in sight and I see a few other issues regularly when writing Tk code using Tk-Cocoa (yes, I should really try and make them reproducible and report them). Unfortunately, my Objective C and Cocoa knowledge is far too limited to be of any help here and it is difficult for me to ask the community to develop Tk-Cocoa further without really being able to help personally.

I plan to revisit the event loop stuff in the near future and see if I 
can figure it out. Believe me, I am very frustrated with the performance 
of Tk-Cocoa, and have attempted to address it in the past--the lack of 
progress is not for lack of trying, it's just very complicated. I 
appreciate what a hard job Daniel Steffen had to do in integrating two 
such disparate frameworks (Tk and Cocoa).

If there are other open bugs, it would be very helpful if you can 
identify them so I can take a look. Example scripts illustrating the 
problem are even better, but at a minimum please post the bug numbers here.

When I assumed actively maintaining Tk-Cocoa last year, I went through 
years worth of open bugs, fixed a lot that were low-hanging fruit, 
closed others as obsolete, and committed patches to some when patches 
were provided; I also added a large section of documentation to the Tk 
man pages on the tk:mac commands. I thought that cleaned things up 
substantially, but perhaps there are issues I've missed. More recently 
I've just focused on keeping the backport up-to-date. Adrian Robert has 
submitted several extremely helpful patches to fix issues he's 
identified; Adrian, thank you again.

In the meantime, thanks to all for the feedback, and feel free to add more.

--Kevin

-- 
Kevin Walzer
Code by Kevin
http://www.codebykevin.com