| |interface Efl.Ui.Scrollable @beta | |├ (E) scroll,start | |├ (E) scroll | |├ (E) scroll,stop | |├ (E) scroll,up | |├ (E) scroll,down | |├ (E) scroll,left | |├ (E) scroll,right | |├ (E) edge,up | |├ (E) edge,down | |├ (E) edge,left | |├ (E) edge,right | |├ (E) scroll,anim,start | |├ (E) scroll,anim,stop | |├ (E) scroll,drag,start | |├ (E) scroll,drag,stop
Description
Description
Details
Details
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T7510 evaluate stabilization potential of efl.ui classes and dependencies | ||
| Resolved | cedric | T7885 efl.ui.list_view | ||
| Resolved | None | T7891 efl.ui.scroller | ||
| Resolved | bu5hm4n | T8096 efl.ui.collection | ||
| Resolved | None | T7870 efl.ui.grid | ||
| Resolved | None | T7881 efl.ui.list | ||
| Wontfix | bu5hm4n | T7882 efl.ui.scrollable_interactive | ||
| Resolved | None | T7883 efl.ui.scrollable | ||
| Resolved | None | T7921 enum Efl.Ui.Scroll_Block | ||
| Resolved | cedric | T8266 efl.ui.item_clickable |
Comment Actions
Any opinions on this task ?
I think those are the set of events which have been used well in legacy scroller.
So, I feel ok with this.
Comment Actions
I think all events should be in the past tense: scroll, started, scroll, stopped...
But I do not know what to do with scroll, up and company :/
Comment Actions
Ok - let's make a patch for "start->started" and "stop->stopped" ~
Any other opinions ~ then, please inform me of that :)
Comment Actions
I have to admit that i do not like the name of this interface. It seems it is very connected to scroll_manager and scrollable interactive, what do you think of moving this to use:
- Efl.Ui.Scrollable.User (Efl.Ui.Scrollable)
- Efl.Ui.Scrollable.Interactive (Efl.Ui.Scrollable_Interactive)
- Efl.Ui.Scrollable.Manager (Efl.Ui.Scroll_Manager)
- Efl.Ui.Scrollable.Bar (Efl.Ui.Scrollbar
This would clean things up a little bit, and have related things in one namespace.
Comment Actions
How about Efl.Ui.Scroll for the namespace? it's simpler (and shorter).
I understand Efl.Ui.Scroll.User is a widget which uses scroll, but I don't like it. The word User is linked too strongly to the user of the computer.
How about Efl.Ui.Scroll.Scrollable?
Comment Actions
I am fine with Scroll, I am not so fine with Scroll.Scrollable, how about Active ? (So we have Interactive & Active).
Comment Actions
Also, how about merging Scrollable and Scrollable_Interactive?
The first only provides events, and the second is the only user of it.
Comment Actions
So you are proposing to merge T7882 with this? Seems sensible, I can't imagine having one without the other...
Comment Actions
So, which one is better between them ?
As a parent interface, I think Scrollable looks better.
After the discussion ~ @eagleeye and I would do the merging work immediately.
Comment Actions
I agree that Scrollable is the better name for the combined interface. I think this should be fine.
Comment Actions
Is it ok to remove "Efl.Ui.Scrollable" from "Elm.Interface.Scrollable" -
and declare needed events by itself (instead of using events in "Efl.Ui.Scrollable") ?
After merging, some properties , such as "content_size" or "step_size", are conflicted with different value types.
So, we need to cut off the dependency between old "Efl.Ui.Scrollable_Interactive" and "Elm_Interface_Scrollable" first.
And I want to know what is the proper and best way to do this.
Comment Actions
@woohyun It appears that no event of Efl.Ui.Scrollable is used in Elm.Interface.Scrollable. I think we can just remove it from its inheritance ?
Comment Actions
I will double check ~ and if there is no use of those events, I'll remove it from "Elm.Interface.Scrollable".
Thank you :)