On 12/23/2017 09:56 AM, Vincent Torri wrote:
On Thu, Dec 21, 2017 at 8:54 AM, Pierre Couderc wrote:
On 12/19/2017 09:44 AM, Vincent Torri wrote:
I am glad to have developed my first application under efl (eegrep =
multidimensional grep).
With legacy API.
The more there are EFL apps, the be
On Thu, Dec 21, 2017 at 8:54 AM, Pierre Couderc wrote:
> On 12/19/2017 09:44 AM, Vincent Torri wrote:
>>>
>>>
>>> I am glad to have developed my first application under efl (eegrep =
>>> multidimensional grep).
>>> With legacy API.
>>>
>> The more there are EFL apps, the better.
>>
>> But the pro
On 12/19/2017 07:05 AM, Pierre Couderc wrote:
I am glad to have developed my first application under efl (eegrep =
multidimensional grep).
With legacy API.
Thanks for all your comments.
I am glad that you all encourage my choice... ;)
On 12/19/2017 09:44 AM, Vincent Torri wrote:
I am glad to have developed my first application under efl (eegrep =
multidimensional grep).
With legacy API.
The more there are EFL apps, the better.
But the project should also do advertising (phoronix, /., linuxfr.org
for french, reddit, lwn, e
On 12/19/2017 08:15 PM, 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 ?
Not to mention the treatment fo
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 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
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
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
> 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/1
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
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-
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:
>
"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
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
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
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
18 matches
Mail list logo
