I am French so I love cheese, baguette and croissant, but not quite wine. I have been kidnapped a year or so by Samsung ninja team in Korea. I am also know as The borker will see if that survive our move to git !
- User Since
- Jan 25 2013, 3:13 AM (355 w, 4 d)
Sun, Nov 17
Fri, Nov 15
Thu, Nov 14
efl_ui_list_view_example_3 still has some issue with focus, but I am not sure where it is coming from. Maybe it is a different task.
Wed, Nov 13
rebase and fix assert.
Mon, Nov 11
As I said the patch looks good and should go on, but not without addressing the past behavior in a way that application that might rely on it would be broken. I have proposed two possible path. If you have other idea to fix it, I will be fine. As long as the application can still have that feature in some way.
Sun, Nov 10
This is the test you're looking for.
There is a test in phab somewhere waiting for you to review it. I forgot the number will try to find later.
Because their wasn't a test for it until now 😓
Fri, Nov 8
rebase and improve logic to reduce over fetching model/entity.
Before all that kind of optimization, I think we will need to revise the API of the position manager and its internal a bit. Main issue I am seeing:
- The collection needs to throttle position manager sizing information request and make sure batch request are not overwhelming the main loop.
- Any change on the item size is currently throwing all cache out from the position manager (and in general the position manager give up on its cache way to easily).
- There is no way for the collection view to inform the position manager of information like item average size or total view port size which would avoid batching size request unnecessarily.
This isn't an ideal patch, but I don't really have a better idea on how to make this happen on theme apply otherwise as scrollable is an interface :-(
Thu, Nov 7
After some more back and forth with @bu5hm4n discussion on IRC, it seems very hard to actually merge those two multiselect interface as they do have different constraint.