-
Notifications
You must be signed in to change notification settings - Fork 16
Proposed List View implementation styles
Various list implementations are possible in Blossom, ordered here top-to-bottom from best performance/memory usage to worst performance/memory usage.
-
Rows share canvas surface, renderRow() function, all rows rendered, non-incremental.
-
Rows share canvas surface, renderRow() function, some rows rendered, incremental.
-
Rows share canvas surface, layers rendered to shared canvas, all rows rendered, non-incremental,
-
Rows share canvas surface, layers rendered to shared canvas, some rows rendered, incremental.
-
Rows share canvas surface, layers rendered to own canvas, all rows rendered, non-incremental,
-
Rows share canvas surface, layers rendered to own canvas, some rows rendered, incremental.
-
Each row is an SC.View with a shared canvas, layers render to shared canvas, all rows rendered, non-incremental.
-
Each row is an SC.View with a shared canvas, layers render to shared canvas, some rows rendered, incremental.
-
Each row is an SC.View with a shared canvas, layers render to own canvas, all rows rendered, non-incremental.
-
Each row is an SC.View with a shared canvas, layers render to own canvas, some rows rendered, incremental.
-
Each row is an SC.View with own canvas, layers render to view's canvas, all rows rendered, non-incremental.
-
Each row is an SC.View with own canvas, layers render to view's canvas, some rows rendered, incremental.
-
Each row is an SC.View with own canvas, layers render to own canvas, all rows rendered, non-incremental.
-
Each row is an SC.View with own canvas, layers render to own canvas, some rows rendered, incremental.
- Each row is its own surface, can be any arbitrary surface type.