Something funny happening with this patch during enlightenment window resize animations, I need to investigate.
This patch doesn't stand alone, and can't be landed without another patch in the series I'm reworking.
Update after Vitor comments.
Fixed compilation with autotools
About the <value> tag on properties. Should we create a new task or it would be a new item here?
Well, since there is a agreement about the <value> tag now, I think I can proceed and land this commit.
The factory doesn't technically need to know anything about the item at all, like in Edje, we can create Efl_Part on the fly and resolve them later. Still, I think the way I would implement this is :
- Enforce Item class to be set at finalize time.
- Create an item on standby for internal use of the class only.
- Every BindProperty call is shadowed to the internal item, if it fails to apply on it, we should fail the call on the factory too.
- The factory remember all the successful call and is ready to replicate them on every item being created.
Wouldn't it make sense to go with an Eina_Inarray structure then ? Would avoid the addition of all the expansion logic.
Minor orthographic fixes. If you don't fix them now, I'll have to do it later :)
Man, I have absolutely no idea what this patch does ("make all view use of it"???) and the commit has no description :(
Will do soon. Phab was dead so I could not review
revert unnecessary changes.
Thu, Dec 13
This ticket has been closed as spam because it lacks a description. If this ticket is not spam, please reopen it after adding a description.
This seems to work like this. Feel free to reopen when not :)