issue 1: ok we have a bit of a consistency issue when it comes to efl interfaces. eo_base class.
eo_parent_set, eo_parent_get, eo_key_data_set, eo_event_freeze, eo_event_callback_priority_add... etc. all these eo_* ... should then not be efl_* for consistency with efl interfaces? question 2: then we have another one... why not just drop down to e_* instead of efl_ ala glib? get more concise... -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
