On Sat, 17 Dec 2005 18:26:17 +0900 Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote:
> you need to add the concept of ecore objects. then being able to > attach things to the ecore objects - that includes keepign the > callback handler list within the object, not in the global list. so > now it will walk only the list of callbacks that it will finally be > calling. otherwise your idea is good - it's just that you really need > to remove the useless walking as u wont really save much. :) That was gonna be my next suggestion. I didn't want to hit you with it all at once, the email was already too long. I did hint at that though. Apart from Ecore_Exe, what other Ecore things will we want to do this for? Since my other recent big email boiled down to "ecore_x's fd handler is an annoying hack" that might be one candidate which might hide that hack locally to ecore_x. That's just bullshit of the top of my head though, I haven't looked at ecore_x. On the other hand, that is probably heavily tied to low speed event stuff that the ecore event system was written for.
pgpfxphJ5pnk3.pgp
Description: PGP signature
