For patches which should not yet be merged
Tue, Aug 20
This is a tentative patch with the C# syntax changes for factory binding static parts that are based on Efl.IContent.
Sun, Aug 18
fix invalid item placement
Fri, Aug 16
This needs rethinking.
Okay i think we need to overthink this patch. It decreases the cache efficiancy a lot, and makes everything ... slower.
Wed, Aug 14
Update the test after updates in the C binding process
Tue, Aug 13
Added the DO NOT MERGE tag so we can start reviewing this while we fix an issue regarding getting the part from the binder.
Mon, Aug 5
Sorry i forgot about this, i ironically redid the same, and just found your ticket, and this revision. I could kick my own ass for that ... :|
Tue, Jul 30
this is irrelevant.
Oh I forgot about this.
Mon, Jul 29
What the state of this one?
Wed, Jul 24
I think this is good enough for landing and we can iterate from there.
- update docs
I've added a few more comments but this has become unmanageable. I'd rather wait until this lands and then I'll update the docs.
Jul 24 2019
rebase + updates to docs
Jul 23 2019
- update docs
Jul 22 2019
- fixup benchmarks, improve output of the binary
Jul 21 2019
- fix lookup cache of the accessor
update docs and all the marked comments.
Jul 19 2019
Jul 18 2019
Also a number of lines need wrapping because they go off screen even in my 160col editor.
One issue I have with this is the bool: animation param for various methods. Typically we provide some options for this kind of thing like linear, accelerate, decelerate, ...
I've made quite a few comments on the API and the docs... make sure to mark them as done so none is forgotten!
Jul 17 2019
I would like to merge this widget at the latest on the 27.07.
add multiselect radio
fix scroller bouncing
Jul 16 2019
more fixes better tests in elm_test
Jul 14 2019
forgot a few files
The widget meanwhile is feature complete, there are tests for the grid position manager and list position manager. The tests for now are only plain copies. Given the complexity of this widget, there will 100% be more bugs to find, and things to clarify, so I would be very happy if people could write examples for that, play with the API, do things that i did not think of. Or simply play around in the tests. Thank you :)
- more tests