On Sun, 26 Nov 2017 10:20:26 -0200 Gustavo Sverzut Barbieri
said:
> On Sun, Nov 26, 2017 at 2:08 AM, Carsten Haitzler
> wrote:
> >> You don't need that, just use Efl_Class.. that's it. no need to
> >> "type_new", no need to "event_get". Use *any* Efl_Class, then:
> >
> > Yes - I thought it over
On Sun, Nov 26, 2017 at 2:08 AM, Carsten Haitzler wrote:
>> You don't need that, just use Efl_Class.. that's it. no need to
>> "type_new", no need to "event_get". Use *any* Efl_Class, then:
>
> Yes - I thought it over more. a @class function can do this type-safely. pass
> in a loop obj and class
On Sat, 25 Nov 2017 20:59:08 -0200 Gustavo Sverzut Barbieri
said:
> On Thu, Nov 23, 2017 at 10:42 PM, Carsten Haitzler
> wrote: [...]
> >> - broadcast events: use Eo as below:
> >>
> >>* no "event type", just event object (which as its Efl_Class, of
> >> course);
> >
> > that was the idea. y
On Fri, Nov 24, 2017 at 12:17 AM, Jean-Philippe André wrote:
> Hi,
>
> Honestly I'm a bit confused by the use of promise/future as the core since
> ecore events aren't single-shot by definition (yes, some of them are). But
> that's beyond the point for my email.
my point is that you handle as sin
On Thu, Nov 23, 2017 at 10:42 PM, Carsten Haitzler wrote:
[...]
>> - broadcast events: use Eo as below:
>>
>>* no "event type", just event object (which as its Efl_Class, of course);
>
> that was the idea. you allocate a new event type (get an int or handle). you
> then GET the event type obje
Hi,
Honestly I'm a bit confused by the use of promise/future as the core since
ecore events aren't single-shot by definition (yes, some of them are). But
that's beyond the point for my email.
In C++ Felipe implemented eo event callbacks like this:
event_add(event_type, object, functor);
funct
On Thu, 23 Nov 2017 10:12:40 -0200 Gustavo Sverzut Barbieri
said:
> my proposal on this whole topic is a bit different and hopefully simpler:
>
> - one time, single shot (ecore jobs): reimplement as promises/future.
> currently they are done on top of events (to avoid changing the
> ecore_main.c
my proposal on this whole topic is a bit different and hopefully simpler:
- one time, single shot (ecore jobs): reimplement as promises/future.
currently they are done on top of events (to avoid changing the
ecore_main.c), of course this needs to be reversed. Simple and clean.
Just need core chang
Hi,
I talked to raster for clarification.
2017-11-22 14:57 GMT+09:00 Carsten Haitzler :
> So we had a partly done move to efl_loop. it still was all built on top of
> the
> main loop globals. If this is all done right then we can have multiple
> loops
> (e.g. one per thread) and that is a good t
So we had a partly done move to efl_loop. it still was all built on top of the
main loop globals. If this is all done right then we can have multiple loops
(e.g. one per thread) and that is a good thing.
So I've been fixing that. I've done just about all the globals in ecore EXCEPT
ecore events. I
10 matches
Mail list logo
