Page MenuHomePhabricator

efl: apiProject
ActivePublic

Members

  • This project does not have any members.

Watchers

  • This project does not have any watchers.

Recent Activity

Today

segfaultxavi added a comment to T7898: efl.ui.format.

Agreed. This is confusing. This is how it works (after examining the code):

Tue, Jun 18, 2:47 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n moved T7894: efl.ui.range_interactive from Backlog to Stabilized on the efl: api board.
Tue, Jun 18, 2:33 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7897: efl.ui.spin.

OK, I think the special_value property is redundant if we use the Efl.Ui.Format mixin. Probably a leftover from older times.

Tue, Jun 18, 2:32 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7894: efl.ui.range_interactive.

Yep, just verified. Looks good to me.

Tue, Jun 18, 2:26 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n added a comment to T7894: efl.ui.range_interactive.

@segfaultxavi this is then also looking good ?

Tue, Jun 18, 2:20 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n moved T7895: efl.ui.range_display from Backlog to Stabilized on the efl: api board.
Tue, Jun 18, 2:20 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7895: efl.ui.range_display.

This looks OK to me too. Docs need polishing, as usual.

Tue, Jun 18, 2:17 AM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7895: efl.ui.range_display.

Woops. I missed the extension relation between two interfaces.
That is, "Efl.Ui.Range_Interactive extends Efl.Ui.Range_Display"

Tue, Jun 18, 1:31 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n added a comment to T7895: efl.ui.range_display.

A few interfaces are only implementing efl.ui.range_display, others are implementing efl.ui.range_interactive. If we would not have this split, we would have a lot of unimplemented API.

Tue, Jun 18, 1:27 AM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7847: efl.ui.clickable.

I also feel good with "efl.input.clickable" :)
It should be better than a name with gfx.

Tue, Jun 18, 1:19 AM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7895: efl.ui.range_display.

Except the wondering why this interface needs to be separated with efl.ui.range_interactive (T7894),
this looks ok for me.

Tue, Jun 18, 1:10 AM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7894: efl.ui.range_interactive.
Tue, Jun 18, 1:10 AM · efl: api, efl (efl-1.23), efl: language bindings

Yesterday

woohyun updated subscribers of T7898: efl.ui.format.
Mon, Jun 17, 10:43 PM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7898: efl.ui.format.

I also think that the only way to give better understanding is "adding simple example or some basic functionalities".
Without any example, nobody could not easily understand what this class is for.

Mon, Jun 17, 8:58 PM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n added a comment to T7847: efl.ui.clickable.

efl.input.clickable sounds reasonable, same for the new event names. @woohyun, also okay for you ?

Mon, Jun 17, 10:23 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7866: efl.ui.nstate.

Okay, so can we remove the code for this entirely or what?

Mon, Jun 17, 10:13 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7847: efl.ui.clickable.

Hm I suppose it makes sense to move it, but then why not have it be efl.input.clickable to go with efl.input.interface?

Mon, Jun 17, 10:12 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7858: efl.text_markup.

Same as efl.text, seems okay?

Mon, Jun 17, 10:11 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7854: efl.text.

Seems good?

Mon, Jun 17, 10:10 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7964: Efl.Input.Key.

Sorry, I am not familiar with X11 so I do not see the difference between a key name and a raw key name... example?

Mon, Jun 17, 10:08 AM · efl (efl-1.23), efl: api
zmike added a comment to T7900: efl.pack_table.

Looking at this again, it seems like this is somewhat similar to how on gfx.entity objects we have position, size, and geometry. It's nice to be able to set/access both axes in one call, so I think we should leave it.

Mon, Jun 17, 10:06 AM · efl: api, efl (efl-1.23), efl: language bindings
SanghyeonLee added a comment to T7905: efl.ui.item.

in MVVM case, as cedric pointed,
child of Efl.Model will be the invariable value for specific item,
but in view object, numeric index can be accessible.

Mon, Jun 17, 3:52 AM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7866: efl.ui.nstate.

We don't need this one. There has been no requests for this widget.

Mon, Jun 17, 2:56 AM · efl: api, efl (efl-1.23), efl: language bindings

Sat, Jun 15

bu5hm4n added a comment to T7905: efl.ui.item.

@SanghyeonLee Can you verify that all usages of the Efl.Ui.Item class do only require a numeric index as parent, never something like an object ?

Sat, Jun 15, 3:18 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n added a comment to T7847: efl.ui.clickable.

It was also brought up that it is confusing to have this in the ui namespace, we should probebly move this to the gfx namespace ...

Sat, Jun 15, 3:16 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n removed parent tasks for T7866: efl.ui.nstate: T7510: evaluate stabilization potential of efl.ui classes and dependencies, T7865: efl.ui.check.
Sat, Jun 15, 3:15 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n removed a subtask for T7865: efl.ui.check: T7866: efl.ui.nstate.
Sat, Jun 15, 3:15 AM · efl: api, efl (efl-1.23), efl: language bindings
bu5hm4n added a comment to T7866: efl.ui.nstate.

Undependend from this, we do not need this widget, lets remove it from the list.

Sat, Jun 15, 3:15 AM · efl: api, efl (efl-1.23), efl: language bindings

Fri, Jun 14

zmike added a comment to T7898: efl.ui.format.

https://i.imgur.com/m4vDHwO.gifv

Fri, Jun 14, 10:10 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7898: efl.ui.format.

https://media.giphy.com/media/oOX5qIDkzDjeo/giphy.gif

Fri, Jun 14, 9:45 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7898: efl.ui.format.

We try to leave some functionality to the imagination of the user; no docs can possibly hope to capture the gestalt of efl's splendor.

Fri, Jun 14, 9:18 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7897: efl.ui.spin.

I've written my concerns in T7898.

Fri, Jun 14, 9:18 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7898: efl.ui.format.

This class needs serious doc love. I do not understand how format_cb and format_string are supposed to interact. Also, Format_Func_Cb only has input parameters, no output, where is the formatted string supposed to be written?

Fri, Jun 14, 9:17 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7897: efl.ui.spin.

I think you would use the callback?

Fri, Jun 14, 9:07 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7900: efl.pack_table.

Future me.

Fri, Jun 14, 9:04 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7897: efl.ui.spin.

And I still don't know how would you implement the special values with a format string.

Fri, Jun 14, 8:25 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7900: efl.pack_table.

When you say "Let us cut it"... who exactly is us? 😁

Fri, Jun 14, 8:22 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7897: efl.ui.spin.

I agree with both of the above ideas.

Fri, Jun 14, 7:15 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7873: efl.ui.image.

I am wondering if we could not get rid of Efl.Ui.Image_Error and just use Eina_Error.

As for total percentage, if I remember correctly it is to reflect the multiple step of loading the image. You could be on a 50% of the downloading, but there is still decompressing, uploading texture and so on, so total percentage might be 25% with no indication on time that it would take to do the other percent.

Fri, Jun 14, 7:14 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7847: efl.ui.clickable.

I like "primary" more than "any", yep.

Fri, Jun 14, 7:11 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7847: efl.ui.clickable.

After some thought, I think maybe an improvement on this could be using changed and changed,primary, where the latter indicates the left button has been pressed on a standard mouse configuration. This more definitively handles the case of e.g., left-handed mouse configuration for Xorg/Wayland and we can mention that the primary event will continue to work for right-handed configurations.

Fri, Jun 14, 7:10 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike moved T7866: efl.ui.nstate from Backlog to Evaluating on the efl: api board.
Fri, Jun 14, 7:01 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7866: efl.ui.nstate.

Does this class need to exist?

Fri, Jun 14, 7:01 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7900: efl.pack_table.

This is a good point. Let's cut it.

Fri, Jun 14, 6:59 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike moved T7976: Efl.Ui.Clickable_Clicked from Backlog to trivial on the efl: api board.
Fri, Jun 14, 6:57 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7976: Efl.Ui.Clickable_Clicked.

This seems pretty straightforward?

Fri, Jun 14, 6:57 AM · efl: api, efl (efl-1.23), efl: language bindings
zmike added a comment to T7893: efl.ui.slider.

I think that's also not quite what we want either?

Fri, Jun 14, 6:48 AM · efl: api, efl (efl-1.23), efl: language bindings
woohyun added a comment to T7849: efl.ui.text.

I also think it is very meaningful to discuss Error things for EFL.
However, this task has a purpose to define text related interfaces.
Error things need to be discussed over EFL, so that kind of things can be talked in another channel such as irc or mailing thread.
Interface related tasks are normally urgent if we think about the due date (i.e. next release).

Fri, Jun 14, 1:51 AM · efl: api, efl (efl-1.23), efl: language bindings
segfaultxavi added a comment to T7893: efl.ui.slider.

So just steady? How about that?

Fri, Jun 14, 1:02 AM · efl: api, efl (efl-1.23), efl: language bindings

Thu, Jun 13

zmike added a comment to T7893: efl.ui.slider.

I think the issue for me is that changed is still in the signal name, and changed implies that a change was completed. Having changed,stable or similar is weird because it implies that regular changed events are not "complete".

Thu, Jun 13, 9:35 AM · efl: api, efl (efl-1.23), efl: language bindings