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:

• Is it okay if i add some sort of idler that frees all the not displayed items after some time ? (we have creation right now implemented, but not removal ... :( ) @cedric

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:

• working creation of items and models
• working deletion of elements that are not on the screen
• grid works

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.

Oh okay, I see. Thank you!

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...

I have tested the collection view now for several hours, it is working quite okayish. Here an there are bugs, but overall it looks and works nice!

• efl_ui_list_view_example_3
  • bringing in a new item does not get visible / positioned correctly.
  • Deleting a element does not work
  • Select a item, click Select None item selection is kind of borked.
• efl_ui_list_view_example_2
  • dead locks for me because it is trying to open a file which is a named pipe. We should check for the file type there ?
• efl_ui_list_view_example_1
  • Drag the mover in the dragbar very fast to the bottom. You will see that no items are placed anymore.

In general the scroller buttom scrollbar is displayed even if it is disabled, this is weird.

I think we should keep this task for tracking mvvm related work after 1.23 released, so remove 1.23 tag as I see we finished all 1.23 related task on this.