Widgets from elm or efl_ui
the mouse drags never used the step variable, slider can get values that are outside the n*step and i think that is normal ?
Like scaling something, you might want to have a step of 0.1 but still want to reach 0.95.
Yeah, you removed the check for 0 < step < 1 in the slider.
Sun, Jul 14
I think i accidentally fixed that in the past when i removed that error?
Fri, Jul 12
Thu, Jul 11
Tue, Jul 9
Revisiting, i think this is an evas bug, in case you do Clear -> Pack without the Back inbetween, you get the same geometries. However, the item does show up. Is it possible that evas forgets to mark something dirty ?
Mon, Jul 8
Sun, Jun 30
@cedric you can find my current implementation in https://git.enlightenment.org/core/efl.git/log/?h=devs/bu5hm4n/work_container
Fri, Jun 28
So we will be going with @bu5hm4n solution. He has already build more code around it and I don't see anything wrong with it.
Hum, I was going for a very different approach actually. I was thinking of having a function to call on a object with something like :
@cedric do you think this could work ?
Thu, Jun 27
InfiniteView is a View. Efl.Io.Model, Efl.CompositeModel are Model. Efl.Core.ViewModel is an helper ViewModel. The discussion here is about the List/Grid View part of MVVM and how to organize and name them.
I'm a bit lost now, are we talking about the name of the widget? I know nothing of MVVM but I expected View to be one of the components?
The important bit is to have the View suffix as that is what the MVVM nomenclature use.
I was more interested in deciding now the prefix. As you say, later we'll add the List, or the Manager or whatever.
Do you people like the prefixes I propose above? Do they make you think of other (better) prefixes?
Besides "Layouter" which I agree we should not use, I also don't like "Infinite". Regular list widgets are also potentially infinite so this word has very little meaning.
Position_Manager ? Positioner ? Active_Positioner ?
I'm throwing a yellow card here. If anyone ever names something layouter I will actually explode.
Wed, Jun 26
On that same note, the caching and efficient scheduling of the computation is also the job of the InfiniteView.
- Add an Efl.Ui.Layouter interface that provide:
- A function that layout a given set of realized items and request more items if there isn't enough
Thinking on this as I start working on cleaning Efl.Ui.ListView. My idea is to go in the following direction :
remove theme too
Tue, Jun 25
Mon, Jun 24
User error - sorry.
It gets unset at the point of being swallowed:
Mhm - the theme does not specify this property ... and as far as breakpoints tell, this is not set to false after this call...
It's planned, but I'm doing something else right now.
Can you add the same for the unified widget ?