Re: [E-devel] What are we going to release?

2017-12-18 Thread Jean-Philippe André
Hi, On Tue, Dec 19, 2017 at 2:43 AM, 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 > develop

Re: [E-devel] [Efl-technical-documentation] Site statistics

2017-12-18 Thread Pierre Couderc
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 we are intending to discontinue." I don't disagree. But if we de-

Re: [E-devel] ecore / efl loop work

2017-12-18 Thread Jean-Philippe André
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't do. The test case passes because it's badly written (marks the success va

Re: [E-devel] Type info in futures

2017-12-18 Thread Jean-Philippe André
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 full > description to find it's return type: > https://www.enlightenment.o

Re: [E-devel] Site statistics

2017-12-18 Thread Simon Lees
On 18/12/17 22:53, Andrew Williams wrote: > 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 hits are alrea

Re: [E-devel] What are we going to release?

2017-12-18 Thread Stephen Houston
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 development efforts and attracting new developers. Count me in as on the side

Re: [E-devel] [Efl-technical-documentation] Site statistics

2017-12-18 Thread Andrew Williams
Hi, It is indeed confusing. We have done our best to describe the situation in the docs and given users the choice. What would be really helpful would be a timeline or plan so that those making the choice can make it an informed one. Andrew On Mon, 18 Dec 2017 at 16:28 Stephen Houston wrote: >

Re: [E-devel] [Efl-technical-documentation] Site statistics

2017-12-18 Thread Stephen Houston
"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 we are intending to discontinue." I don't disagree. But if we de-prioritize the old API at the cost of furthering

Re: [E-devel] [Efl-technical-documentation] Site statistics

2017-12-18 Thread Andrew Williams
Hi, Apologies I was using "legacy" by way of definition to separate it from "unified" APIs. We are now fighting a battle of multiple focuses - Some tell me that we are pushing the Unified / interfaces as fast as we can and anything (such as release) would slow us down. Others are reporting that le

Re: [E-devel] [Efl-technical-documentation] Site statistics

2017-12-18 Thread Stephen Houston
With 4 and 5, I think this should be sent in a follow up to cedric's website redesign thread. As I think, and a lot of people agree, the look and feel of the website needs a lot more work than just a few layout/content changes. On Mon, Dec 18, 2017 at 9:43 AM Stephen Houston wrote: > I disagree

Re: [E-devel] [Efl-technical-documentation] Site statistics

2017-12-18 Thread Stephen Houston
I disagree with #1. It's not Legacy API until it is actually, you know, legacy. Who knows how long the "beta" api will be before released and how long it will be until there is a stable release of it that will work full featured for application, especially elementary, development. To not provide

[E-devel] Type info in futures

2017-12-18 Thread Andrew Williams
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 full description to find it's return type: https://www.enlightenment.org/develop/api/efl/io/manager/method/open THanks, Andy -- http://andywilliam

[E-devel] Site statistics

2017-12-18 Thread Andrew Williams
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 hits are already for the beta API documentation 3) Most of the hits to /do

Re: [E-devel] ecore / efl loop work

2017-12-18 Thread Jean-Philippe André
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 Time: December 14, 2017 9:30 PM > > > UTC Time: December 15, 2017 5:30 AM > > > F

Re: [E-devel] FOSDEM 2017

2017-12-18 Thread Carsten Haitzler
On Sun, 17 Dec 2017 19:50:16 + Tom Hacohen said: > This one is from last year. ;) Dang. It is... I'm a bit late. :) > On 17 Dec 2017 15:01, "Carsten Haitzler" wrote: > > > On Mon, 5 Dec 2016 14:09:00 +0100 Philippe Caseiro < > > caseiro.phili...@gmail.com> > > said: > > > > didn't submit.

Re: [E-devel] FOSDEM

2017-12-18 Thread Carsten Haitzler
On Sun, 17 Dec 2017 19:51:13 + Tom Hacohen said: > I'm also coming. Want to book my travel. When is everyone getting > there/leaving? > > I'm thinking doing Friday - Sunday? I'll be there for those days. :) > -- > Tom > > On 17 Dec 2017 15:01, "Carsten Haitzler" wrote: > > > On Wed, 22