Carsten Haitzler <[EMAIL PROTECTED]> [2004-06-22 20:28]: > > I'm talking about ecore_evas_callback_foo_set() :) > > aaah yes. i see what you mean. the reason i did this is it matched evas's > setting of callbacks on objects better - i guess this is open for debate :)
Okay, reasons for using ecore_event instead: o Used widely in ecore-based libs/apps, everyone who's familiar with Ecore is also familiar with ecore_event o API consistence with other ecore-based libs reasons against it: o API similar to evas' o callbacks only occur for the object (ecore evas) you registered them on IMHO, the last point is really weak. If we don't use ecore_event because event handlers are always global and not tied to a specific object, we admit that the system sucks :] IMHO two, most users (developers) don't care whether the API is similar to Evas, because they'll prolly never use Evas' callback system directly, because that's what they use ecore_evas for. Please, folks, comment :) -- Regards, Tilman ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
