Hello.
Summary:
o Coverity issue rate still increasing
o Pending patch reviews dropped (Thanks to JP, I guess)
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parentheses reflect the values from
last week to give you a trend.
CI:
o O
Hi,
Thanks for the feedback, much sounds like what I had hoped to add (this was
a first pass to trim out the bulk - more layout and styling to be done).
On your first point the question is whether this is abstract documentation
or language specific. The view that I have taken in formatting these
Hi,
I follow. I'll regenerate the docs as soon as it's in so we can get a more
complete picture of widget inheritance within Efl.*
Thanks,
Andy
On Tue, 12 Dec 2017 at 00:49 Jean-Philippe André wrote:
> On Tue, Dec 12, 2017 at 2:31 AM, Andrew Williams
> wrote:
>
> > Hi,
> >
> > Perfect, that's
> efl_future_Eina_FutureXXX_then(data, f);
now must rename these efl_future_Eina_FutureXXX_then() helpers to
efl_future_then().
Worth remembering: efl_future_then() is the one that links/binds an
object to the future, if the object dies, then the futures are
cancelled.
After that we need to
On Tue, Dec 12, 2017 at 10:23 AM, Gustavo Sverzut Barbieri
wrote:
>> efl_future_Eina_FutureXXX_then(data, f);
>
> now must rename these efl_future_Eina_FutureXXX_then() helpers to
> efl_future_then().
>
> Worth remembering: efl_future_then() is the one that links/binds an
> object to the futur
On Tue, 12 Dec 2017 10:23:23 + Andrew Williams said:
> Hi,
>
> Thanks for the feedback, much sounds like what I had hoped to add (this was
> a first pass to trim out the bulk - more layout and styling to be done).
That's cool. It's a step in a good direction then. :)
> On your first point
Hi,
I don’t know if there is much value including the graph - for non-trivial
classes it’s very difficult to render at any readable size. My preference
would be to remove it, the inheritance tree shows the important
information...
Thanks,
Andy
On Tue, 12 Dec 2017 at 14:06, Carsten Haitzler wrote
Thanks for your work, few comments to improve it a little more:
> +typedef struct _Ctx {
> + Eina_Promise *p;
> + Eina_Bool should_fail;
> + Ecore_Timer *timer;
efl_loop_timeout(loop, seconds) will return a future that resolves
once at a given time, it's a non-recurring timer.
if you want
Hi,
Thanks so much for the suggestions. The Ecore_Timer was a copy/paste issue
but the others are all new to me :)
Andy
On Tue, 12 Dec 2017 at 20:51, Gustavo Sverzut Barbieri
wrote:
> Thanks for your work, few comments to improve it a little more:
>
> > +typedef struct _Ctx {
> > + Eina_Promi
On Tue, 12 Dec 2017 15:11:13 + Andrew Williams said:
> Hi,
>
> I don’t know if there is much value including the graph - for non-trivial
> classes it’s very difficult to render at any readable size. My preference
> would be to remove it, the inheritance tree shows the important
> information
On Tue, Dec 12, 2017 at 7:19 PM, Jaehyun Cho
wrote:
> jaehyun pushed a commit to branch master.
>
> http://git.enlightenment.org/core/efl.git/commit/?id=
> 4f40d476aac297c5dfa7ad340a2629ccc30f993d
>
> commit 4f40d476aac297c5dfa7ad340a2629ccc30f993d
> Author: Jaehyun Cho
> Date: Tue Dec 12 19:1
11 matches
Mail list logo
