Skip to content

Bad Performance on handling big design document tree with consist render updates #1

@softmarshmallow

Description

@softmarshmallow
canvaskit-performance.mov

As you can see we’ll need to handle design document tree handling on a C++ Bridge
I’m not quite sure what causes this major performance down break

Write Design Document Tree Parser (IO) based on C++
On this level, React (App) will only provide full Design document tree initially, givving only the command events. (E.g. On Dragging, App will only provide the pointer event and everything else will be handled inside c++ bridge)

I've referenced this to README's roadmap

ref: design original from here

ref: reddit

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions