On Wed, Dec 20, 2017 at 12:41 PM, Carsten Haitzler
wrote:
> On Wed, 20 Dec 2017 11:58:21 +0900 Jean-Philippe André
> said:
>
> > On Wed, Dec 20, 2017 at 11:01 AM, Carsten Haitzler >
> > wrote:
> >
> > > On Mon, 18 Dec 2017 20:16:49 +0900 Jean-Philippe André <
> j...@videolan.org>
> > > said:
>
On Wed, Dec 20, 2017 at 12:36 PM, Carsten Haitzler
wrote:
> On Wed, 20 Dec 2017 11:19:30 +0900 Jean-Philippe André
> said:
>
> > On Wed, Dec 20, 2017 at 11:10 AM, Carsten Haitzler >
> > wrote:
> >
> > > On Tue, 19 Dec 2017 11:53:13 +0900 Jean-Philippe André <
> j...@videolan.org>
> > > said:
>
On Tue, 19 Dec 2017 19:20:16 -0500 Cedric Bail said:
> Hello everyone,
>
> It has been a long time since this idea has been brewing, but we never have
> felt like we needed to formalize how to interact between each other in a
> respectful cooperative way. I feel this has changed and evolved in t
On Wed, 20 Dec 2017 11:58:21 +0900 Jean-Philippe André said:
> On Wed, Dec 20, 2017 at 11:01 AM, Carsten Haitzler
> wrote:
>
> > On Mon, 18 Dec 2017 20:16:49 +0900 Jean-Philippe André
> > said:
> >
> > > On Sat, Dec 16, 2017 at 12:20 PM, Carsten Haitzler > >
> > > wrote:
> > >
> > > > On Fri,
On Wed, 20 Dec 2017 11:19:30 +0900 Jean-Philippe André said:
> On Wed, Dec 20, 2017 at 11:10 AM, Carsten Haitzler
> wrote:
>
> > On Tue, 19 Dec 2017 11:53:13 +0900 Jean-Philippe André
> > said:
> >
> > > Hey raster,
> > >
> > > I'm confused by something, see ecore_test_ecore_main_loop_timer_in
On Wed, Dec 20, 2017 at 11:01 AM, Carsten Haitzler
wrote:
> On Mon, 18 Dec 2017 20:16:49 +0900 Jean-Philippe André
> said:
>
> > On Sat, Dec 16, 2017 at 12:20 PM, Carsten Haitzler >
> > wrote:
> >
> > > On Fri, 15 Dec 2017 14:29:22 -0500 Cedric Bail said:
> > >
> > > > > Original Mess
On Wed, Dec 20, 2017 at 11:10 AM, Carsten Haitzler
wrote:
> On Tue, 19 Dec 2017 11:53:13 +0900 Jean-Philippe André
> said:
>
> > Hey raster,
> >
> > I'm confused by something, see ecore_test_ecore_main_loop_timer_inner,
> > and ecore_test_ecore_main_loop_event_recursive.
> > This test runs the m
On Tue, 19 Dec 2017 12:31:04 -0500 Cedric Bail said:
> The open question will be for bindings, especially the one that have already
> an existing user base. I would love to see the python bindings allow for the
> same smooth transition as for the C API, for the same reason as we already
I think
On Mon, 18 Dec 2017 12:23:08 + Andrew Williams said:
> Hi all.
>
> Since adding Google Analytics a while back I have some interesting
> statistics that I thought I would share:
>
> 1) Very few people read our Stable API documentation - around 0.5% of our
> page hits
> 2) Over 5% of the page
On Mon, 18 Dec 2017 20:16:49 +0900 Jean-Philippe André said:
> On Sat, Dec 16, 2017 at 12:20 PM, Carsten Haitzler
> wrote:
>
> > On Fri, 15 Dec 2017 14:29:22 -0500 Cedric Bail said:
> >
> > > > Original Message
> > > > Subject: [E-devel] ecore / efl loop work
> > > > Local Ti
On Tue, 19 Dec 2017 15:56:43 -0200 Gustavo Sverzut Barbieri
said:
> On Mon, Dec 18, 2017 at 9:04 AM, Jean-Philippe ANDRÉ
> wrote:
> > jpeg pushed a commit to branch master.
> >
> > http://git.enlightenment.org/core/efl.git/commit/?id=784a5b56a3c798e5a8081e2ce30c79cd8ef7b326
> >
> > commit 784a5b
On Tue, 19 Dec 2017 11:53:13 +0900 Jean-Philippe André said:
> Hey raster,
>
> I'm confused by something, see ecore_test_ecore_main_loop_timer_inner,
> and ecore_test_ecore_main_loop_event_recursive.
> This test runs the main loop inside the main loop, which the documentation
> says you shouldn'
On Wed, Dec 20, 2017 at 2:56 AM, Gustavo Sverzut Barbieri <
barbi...@gmail.com> wrote:
> On Mon, Dec 18, 2017 at 9:04 AM, Jean-Philippe ANDRÉ
> wrote:
> > jpeg pushed a commit to branch master.
> >
> > http://git.enlightenment.org/core/efl.git/commit/?id=
> 784a5b56a3c798e5a8081e2ce30c79cd8ef7b32
On Wed, 20 Dec 2017 09:53:05 +1030
Simon Lees wrote:
> >
> Both mostly dual.
Well there goes my only assumption as to why one system has issues and
not another. I guess maybe hardware. Some things like screenshot I
would not think involved hardware drivers. I guess it could. Hardware
would be
Hello everyone,
It has been a long time since this idea has been brewing, but we never have
felt like we needed to formalize how to interact between each other in a
respectful cooperative way. I feel this has changed and evolved in the past
month to a point where I am writing this email to see
On 20/12/17 09:05, William L. Thomson Jr. wrote:
> On Wed, 20 Dec 2017 08:22:49 +1030
> Simon Lees wrote:
>
>> On 20/12/17 05:39, William L. Thomson Jr. wrote:
>>> On Mon, 18 Dec 2017 17:43:29 +
>>
>>> I completely disagree! EFL is a total mess! IMHO what needs to be
>>> done is EO and Wayl
On Wed, 20 Dec 2017 08:22:49 +1030
Simon Lees wrote:
> On 20/12/17 05:39, William L. Thomson Jr. wrote:
> > On Mon, 18 Dec 2017 17:43:29 +
>
> > I completely disagree! EFL is a total mess! IMHO what needs to be
> > done is EO and Wayland should be EFL 2.x. 1.x should remain legacy
> > and X,
On 20/12/17 05:39, William L. Thomson Jr. wrote:
> On Mon, 18 Dec 2017 17:43:29 +
> Stephen Houston wrote:
>
>> I really think a consensus needs to be reached here. The uncertainty
>> has too many ill effects in other areas of the project, not the least
>> of which is documentation as Andy
On Tue, 19 Dec 2017 14:15:33 -0500
"William L. Thomson Jr." wrote:
> On Tue, 19 Dec 2017 07:05:28 +0100
> Pierre Couderc wrote:
>
> > I am glad to have developed my first application under efl (eegrep
> > = multidimensional grep).
> > With legacy API.
> > Should I regret not having used Gnome ?
On Tue, 19 Dec 2017 07:05:28 +0100
Pierre Couderc wrote:
> I am glad to have developed my first application under efl (eegrep =
> multidimensional grep).
> With legacy API.
> Should I regret not having used Gnome ?
Not at all, stuff like the following is wonderful! New one today
https://gi
On Mon, 18 Dec 2017 17:43:29 +
Stephen Houston wrote:
> I really think a consensus needs to be reached here. The uncertainty
> has too many ill effects in other areas of the project, not the least
> of which is documentation as Andy has said, as well as a difficulty
> prioritizing developmen
Hello Pierre,
My intent was never to suggest that. I was only suggesting that the
distinctions within the api could be confusing enough that a new developer
could easily mistake it or misunderstand it and decide not to use either.
Andrew, myself, and most other developers involved have used and c
On Mon, Dec 18, 2017 at 11:31 PM, Jean-Philippe André wrote:
> Hi,
>
> On Tue, Dec 19, 2017 at 12:25 AM, Andrew Williams
> wrote:
>
>> Hi,
>>
>> Is there a way that we can preserve type information when using
>> Eina_Future?
>>
>> For example on the Efl.Io.Manager "open" method I have to read the
On Mon, Dec 18, 2017 at 9:04 AM, Jean-Philippe ANDRÉ wrote:
> jpeg pushed a commit to branch master.
>
> http://git.enlightenment.org/core/efl.git/commit/?id=784a5b56a3c798e5a8081e2ce30c79cd8ef7b326
>
> commit 784a5b56a3c798e5a8081e2ce30c79cd8ef7b326
> Author: Jean-Philippe Andre
> Date: Mon De
Hi Pierre,
I, as most others here, think that picking EFL is a great choice.
We are in a time of flux but there is no reason to regret having used the
current stable (legacy) API.
As cedric notes this will be supported for many years and we will be
offering a smooth transition to the new Unified A
for eina_future, with my suggested implementation all the
promises/futures will be bound to their objects. If the object dies,
the futures are cancelled...
eolian should come to help and all methods returning futures should be
automatically bound to the object, unless they are explicitly marked
as
> Original Message
> Subject: Re: [E-devel] [Efl-technical-documentation] Site statistics
> Local Time: December 18, 2017 10:05 PM
> UTC Time: December 19, 2017 6:05 AM
> From: pie...@couderc.eu
> To: enlightenment-devel@lists.sourceforge.net
>
> On 12/18/2017 05:28 PM, Stephen Ho
On Tue, Dec 19, 2017 at 7:05 AM, Pierre Couderc wrote:
> On 12/18/2017 05:28 PM, Stephen Houston wrote:
>>
>> "If we are to de-prioritise the new API at the cost of further development
>> of legacy APIs then we are prolonging the period of time in which we
>> request developers to use an API which
28 matches
Mail list logo
