maybe this repo: review.tizen.org:29418/platform/core/uifw/isf
On Mon, Apr 1, 2019 at 11:13 PM Carsten Haitzler
wrote:
> On Mon, 1 Apr 2019 17:26:55 +0800 (CST) 陈静 said:
>
> Actually this goes via ecore imf and thus via whatever input method
> handler you
> have. tizen has an scim based input m
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
On Mon, 1 Apr 2019 17:26:55 +0800 (CST) 陈静 said:
Actually this goes via ecore imf and thus via whatever input method handler you
have. tizen has an scim based input method system with a virtual keyboard that
handles this. nothing else does at this stage, so it's not going to work unless
you adopt
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 never ran this API or tryed to use it myself, i just looked at the
code a bit.
It seems that the API that you call is piped to ecore_imf, and ecore_imf
modules then pick up this property, and show / enable the virtual keyboard.
I was not able to get this to work with the xserver. However, a qui
The current build is old which is why I must manually update it. Once this
is done then it may become more worthwhile to spend time on since only
extant issues will be displayed.
On Mon, Apr 1, 2019 at 8:47 AM Christopher Michael
wrote:
> On 4/1/19 8:40 AM, Mike Blumenkrantz wrote:
>
> Hi,
>
> I
This is not a blocker as we are still shipping autotools as the "default"
build system for this release.
On Mon, Apr 1, 2019 at 8:46 AM Vincent Torri
wrote:
> On Mon, Apr 1, 2019 at 2:41 PM Mike Blumenkrantz
> wrote:
> >
> > Hi,
> >
> > I'd like to get an idea of what critical items remain for
On 4/1/19 8:40 AM, Mike Blumenkrantz wrote:
Hi,
I'd like to get an idea of what critical items remain for the 1.22 release,
ideally for the purpose of doing the release sometime this week. My current
items:
* [1]https://git.enlightenment.org/core/efl.git
We're doing some work on this and I'm
On Mon, Apr 1, 2019 at 2:41 PM Mike Blumenkrantz
wrote:
>
> Hi,
>
> I'd like to get an idea of what critical items remain for the 1.22 release,
> ideally for the purpose of doing the release sometime this week. My current
> items:
>
> * https://git.enlightenment.org/core/efl.git
> We're doing some
Hi,
I'd like to get an idea of what critical items remain for the 1.22 release,
ideally for the purpose of doing the release sometime this week. My current
items:
* https://git.enlightenment.org/core/efl.git
We're doing some work on this and I'm not considering it a release blocker
even though it
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
Hi,
Thank you so much for your reply. Window manager ? Did you mean enlightenment ?
I also download enlightenment-0.22.4 and run ./configure->make->make install on
my ubuntu.
In fact,I don't know what is the relationship between efl and enlightment. I
just follow the instruction in https://ww
22 matches
Mail list logo
