On Mon, Apr 25, 2011 at 12:05 AM, Phillip Nguyen <[email protected]> wrote: > > > On Apr 24, 9:59 pm, Leonardo Santagada <[email protected]> wrote: >> Any news on this? How about merging it back in pyglet trunk? > > The ubiquitous send_message() weirdness that I am using in the cocoa- > ctypes clone seems like it would not be very maintainable to me, so I > don't think it would be a good idea to merge it into the trunk as it > is. I could be wrong though.
I think keeping it in a separate branch causes definite harm and not much good, and I think the question of when to merge it is independent from the question of whether all the bugs have been fixed (given that merging it won't affect systems that run the other platforms, and that all systems that can use Carbon will still do so by default). This is why I'm in favor of merging it back into the trunk as soon as possible, regardless of bug status. The only exception would be if you planned to do a big refactoring before merging. It sounds like you think that might be a good idea in theory, but won't have time to do one in the forseeable future. If that's the case, I think the choices are merge what you have, or give up merging at all (for the forseeable future). I think merging what you have is *much* better. (This is just my personal take on the situation, from a position of much less knowledge of the details than you have.) - Bruce Smith -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
