Closed TimLariviere closed 3 years ago
Introduced Registrar
and DynamicViewElementHandler
types.
Those will avoid having to store targetType
, create
, update
and updateAttachedProperties
inside each DynamicViewElement
instances, reducing the memory footprint of 1 DynamicViewElement
.
So this should have a great impact on the memory allocation due to the sheer numbers of DynamicViewElement
instantiated throughout the life of an application.
@TimLariviere I love what you're doing here
Thanks!
This PR also reworks the way we print some debug info to the console, by using a built-in tracing tooling. This will help fix #307
As part of the allocations reduction process, I'm reworking the
ViewElement
class to become an interfaceIViewElement
. This will allow for different implementation such asComponentViewElement
(see https://github.com/TimLariviere/Fabulous/issues/25 for more information).In this example,
ComponentViewElement
would drastically reduce the number of allocated ViewElement at each update.