On Tue, 2 Apr 2019 09:37:33 -0400 Mike Blumenkrantz
said:
> The page background loaded and the page content remained blank for a long
> time before eventually loading. Seems a bit better today but still the same
> issue.
hmmm. ok. i was wondering if it's the kiwi-irc stuff that basically adds
sl
Works for me, and I have cleared all browser caches. Weird.
Here's an archived version, for your reading pleasure:
https://web.archive.org/web/20190402142721/https://www.enlightenment.org/playground/choose-your-api.md
Xavi
On Tue, 2 Apr 2019 at 15:37, Mike Blumenkrantz <
michael.blumenkra...@gm
The page background loaded and the page content remained blank for a long
time before eventually loading. Seems a bit better today but still the same
issue.
On Mon, Apr 1, 2019 at 7:41 PM Carsten Haitzler
wrote:
> On Mon, 1 Apr 2019 13:59:00 -0400 Michael Blumenkrantz
> said:
>
> > Seems reason
On Mon, 1 Apr 2019 13:59:00 -0400 Michael Blumenkrantz
said:
> Seems reasonable. Is that page intended to load in under 15 minutes or are we
> having server issues again?
Do you see the content in full but then still have the busy spinner going for a
while with no visible updates until this spin
Seems reasonable. Is that page intended to load in under 15 minutes or are we
having server issues again?
On Mon, 1 Apr 2019 19:55:13 +0200
Xavi Artigas wrote:
> This is an idea of what I had in mind:
> https://www.enlightenment.org/playground/choose-your-api.md
>
> Xavi
>
> On Mon, 1 Apr 201
This is an idea of what I had in mind:
https://www.enlightenment.org/playground/choose-your-api.md
Xavi
On Mon, 1 Apr 2019 at 17:39, Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> I agree with the point that newcomers will have no idea what EO is (and
> they should not need to know
I agree with the point that newcomers will have no idea what EO is (and
they should not need to know). It's best to have naming targeted at the
newcomer demographic since any developers which are already invested in the
community will inherently know which API is being referred to regardless of
wha
The problem I see with EO is that newcomers don't know what it is, so it
needs to be introduced.
But then again, we could do something similar: *Components (Classic)*
vs *Unified
(EO)*.
I have been envisioning for a while a first page on the Developers section,
clearly split in two, saying:
CHOOSE
create a poll : https://framadate.org/create_poll.php?type=autre
Vincent
On Mon, Apr 1, 2019 at 3:58 PM Mike Blumenkrantz
wrote:
>
> Component (Classic) seems acceptable, though I think there is still room
> for people to not understand what is meant by this term.
>
> On Mon, Apr 1, 2019 at 9:32
On Mon, 1 Apr 2019 15:31:46 +0200 Xavi Artigas said:
> Thank you all for your feedback!
>
> My comments:
> Universal works too, but I think Unified is more specific as to its purpose.
> I wasn't sure about the Classic name so I welcome alternatives. I like
> Components because it clearly states
Component (Classic) seems acceptable, though I think there is still room
for people to not understand what is meant by this term.
On Mon, Apr 1, 2019 at 9:32 AM Xavi Artigas wrote:
> Thank you all for your feedback!
>
> My comments:
> Universal works too, but I think Unified is more specific as
Thank you all for your feedback!
My comments:
Universal works too, but I think Unified is more specific as to its purpose.
I wasn't sure about the Classic name so I welcome alternatives. I like
Components because it clearly states its problem. However, we would need to
explain that "the API that y
I'd prefer "component" and "unified". They say the classics never go out of
style, but they do.
On Mon, Apr 1, 2019 at 5:32 AM Xavi Artigas wrote:
> Hello everybody,
>
> TL;DR: Current docs are a mess because of inconsistent naming of the two
> APIs (old and new). I propose we call them Classic
On 01/04/2019 22:39, Hermet Park wrote:
Sounds good to me. Agree on this idea.
Maybe universal API could be one another option...
I think calling the old API the "Worst" api and the new API the "Best"
API is probably the best way forward.
--
Simon Lees (Simotek)
Sounds good to me. Agree on this idea.
Maybe universal API could be one another option...
On Mon, Apr 1, 2019 at 6:32 PM Xavi Artigas wrote:
> Hello everybody,
>
> TL;DR: Current docs are a mess because of inconsistent naming of the two
> APIs (old and new). I propose we call them Classic and Un
Hello everybody,
TL;DR: Current docs are a mess because of inconsistent naming of the two
APIs (old and new). I propose we call them Classic and Unified and revamp
the docs site.
As you know, we have all been laboring in the past years to produce a new
API for EFL that presents a unified look (in
16 matches
Mail list logo
