Hey there, As agreed I've now moved Eo to the Efl namespace. There is only one thing left to rename and then I will be done. That remaining item is "Eo_Event". This is the extra parameter passed to the event callbacks that includes things like the event info, object and the event description. I was going to just rename it to Efl_Event, but unfortunately this is already taken by an interface.
My options are now to either rename Efl_Event to something else, and then Eo_Event to that. Or just rename Eo_Event to something that doesn't clash. I'm not feeling very creative today and can't come up with a good name. I'm lazy, so I'd rather just rename Eo_Event to something that doesn't clash, but given that Eo_Event is used all over the place, and the other is rarely used, I'd rather keep the Eo_Event name short, call it Efl_Event and rename the other one. Any naming suggestions? Thanks, Tom. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
