On 11/08/16 14:49, Gustavo Sverzut Barbieri wrote:
> On Wed, Aug 10, 2016 at 11:34 PM, Carsten Haitzler <ras...@rasterman.com>
> wrote:
>> On Wed, 10 Aug 2016 13:03:03 -0300 Gustavo Sverzut Barbieri
>> <barbi...@gmail.com> said:
>>
>>> On Wed, Aug 10, 2016 at 12:07 PM, Carsten Haitzler <ras...@rasterman.com>
>>> wrote:
>>>> On Wed, 10 Aug 2016 15:41:00 +0100 Tom Hacohen <t...@osg.samsung.com> said:
>>>>
>>>>> Hey there,
>>>>>
>>>>> Sorry it took me so long to get to this one. I've been dealing with
>>>>> other things, and every time I got back to this I had more clashes and
>>>>> hell. I'm finally at a stage I can merge most of it, so I'm happy,
>>>>> though I have one question before I push.
>>>>>
>>>>> At the moment I changed it as follows:
>>>>> Eo.Base -> Efl.Object
>>>>> Eo.Override -> Efl.Object.Override
>>>>>
>>>>> I'm quite OK with this change. The problem comes with the actual
>>>>> functions. At the moment they are:
>>>>>
>>>>> efl_ref()
>>>>> efl_add()
>>>>> efl_del()
>>>>> efl_finalize()
>>>>> efl_name_set()
>>>>> efl_parent_get()
>>>>
>>>> these. we know at this level of the base api namespace that efl_ here is
>>>> actually an efl OBJECT and we are doing something to it. that's
>>>> understood/implied. adding more wordiness doesnt help with any of that,
>>>> just
>>>> makes code more verbose and adds more typing effort.
>>>
>>> isn't clear to me... at least not after coming back :-)
>>
>> then all those OO developers are horrible. i mean:
>>
>> window.name_set("hello");
>>
>> how do i know name_set() method is operating on an object? gee. it had better
>> become
>>
>> window.object_name_set("hello");
>>
>> or
>>
>> window->object_name_set("hello");
>
> not really since it Would be Efl (namespace) Object (base class) and
> name_set (method). So it would be window.name_set().
>
> you can see from Tom's email that the base class is Efl.Object, not
> simply Efl. If those method were auto-generated by eolian, you'd have
> what I asked, because it's consistent ;-)
>
Yeah, and it was also the case with Eo.Base, but we override the prefix. :)
>
>> ok. now i know how it works!
>>
>> i'm being a bit snide :) but EFL/EO api *IS* AN OBJECT API. it's the BASIC
>> REQUIREMENT. they all take an object as parameter.
>
> You can read in my comment that I'm coming from outside of this whole
> Eo and unified Efl discussion, thus it wasn't clear to me and likely
> won't be for others in the same situation.
>
> [...] lengthy rant which I get [...]
>
> It's inconsistent and I'd rather avoid that, but okay if I'm the only
> one to be annoyed by it... I also like to type less :-)
------------------------------------------------------------------------------
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
