On 6/29/07, Enlightenment CVS <[EMAIL PROTECTED]> wrote:
> - etk_signal_connect("popped_up", ETK_OBJECT(menu),
> ETK_CALLBACK(_entropy_etk_context_menu_popup_cb), NULL);
> + etk_signal_connect("popped-up", ETK_OBJECT(menu),
> ETK_CALLBACK(_entropy_etk_context_menu_popup_cb), NULL);
this is just plain stupid... why do etk use strings to identify object
signals instead of enumerations? This would:
- turn run-time errors into compile-time errors
- reduce binary size
- reduce memory usage
- reduce runtime overhead
imo this should be changed to int and enums.
BTW, I was talking with ewl guys and their usage of just one callback
type and they have no problems, why not also move to this solution? it
would enable us to remove the ugly marshalers AND make it
compiler-friendly.
these are really big infrastructural changes, but better doing it now
than never and carrying some kludges forever (like gtk).
--
Gustavo Sverzut Barbieri
--------------------------------------
Jabber: [EMAIL PROTECTED]
MSN: [EMAIL PROTECTED]
ICQ#: 17249123
Skype: gsbarbieri
Mobile: +55 (81) 9927 0010
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
