On Tue, 22 Jun 2004 20:54:57 +0200 Tilman Sauerbeck <tilman@...>
> Carsten Haitzler <raster@...> [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
> 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 :]
it's a convenience that this works this way. but not essential. one thing a
change would involve is a change in a reasonable amount of code (and non trivial
changes)... what we need to weight up - is - is this worth it? do we have both
ways of doing it (at least for a while) as a transition?
> 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.
well you end up having to use it one way or the other. if not evas's callback
system you end up using edje's callback system... or using ewl's! :)
> Please, folks, comment :)
> 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 http://www.blackhat.com
> enlightenment-devel mailing list
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) raster@...
熊耳 - 車君 (数田) raster@...
Tokyo, Japan (東京 日本)