A ticket for managing development of collection_view.
Overall missing features:
Overall bugs on devs/bu5hm4n/cv-finalize:
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T8177 Collection_View Tracking ticket | ||
| Resolved | bu5hm4n | T8178 efl.ui.collection_view crashes when scrolling | ||
| Resolved | bu5hm4n | T8179 Adjust position_manager | ||
| Open | None | T8180 Efl.Ui.Factory problem | ||
| Open | None | T8197 Invalid sizes | ||
| Resolved | bu5hm4n | T8200 RFC: Selection in CV |
So - i have updated https://git.enlightenment.org/core/efl.git/log/?h=devs/bu5hm4n/cv
I have done something a bit radical, i disabled the complete viewport logic. That helped me finding various problems. The version in there is now able to create the views correctly add them correctly. A sizing bug is still in there which is fixed with a ugly hack, i think i need the help of mike there. @cedric would it be okay, if i bugfix this version more, and try to finize this, *without* viewport, but only the cache, so we have a running basic version, where we can implement the selection and so on ?
Open questions for the above version:
Yes, going with a simpler version should help. I was planning to run an idler for removing things from the cache with some time constraint to not completely clog the main loop during a cleanup cycle, but all of that can be done later.
Okay, let me try to push hard into that direction. I will add my personal tasks to this tasks.
check out devs/bu5hm4n/cv-finalize
I have seperated there all the fixes that are required in other domains from collection view, and documented them a bit. The factory problem also has its fix now, however, that cannot be merged until the rest of cedrics commit in this branch are going into review. With the state that is currently in this branch, we have:
Most of the problems from above are still there.
See my comment in the subtask regarding the 0x0 sizing. afaik @cedric was doing this intentionally so the sizing could be completely disabled (e.g., manually unsetting need_recalc) if the parent model provided sizing info. I didn't do any work to hook up using size calcs, but it isn't particularly difficult if we want to add it.
A perf note from another ticket I just saw: if the item is a layout object then probably we also want to do efl_canvas_layout_animation_set(item, false) (and even efl_object_freeze) any time the item object is not expected to be visible to block callbacks and improve performance.
There's something strange going on when I scroll up quickly; it's like it starts trying to do the bounce animation before reaching the top of the scroller...