Skip to content

Working towards component parity with React Native #210

@agg23

Description

@agg23

From a project management perspective, what is the plan for working towards component parity with React Native? Is the idea to just keep this library as a React wrapper around NodeGUI (and therefore a wrapper around Qt itself), or is there room for adding more "complicated" components? Should core RN components be implemented as a plugin instead?

From my research, there's a lot that needs to happen to implement something like FlatList, especially if based off of QListView or QTableView. I'm honestly not even sure what this translation would look like, given that Qt doesn't like widgets to be children of the QList* likes, so there would have to be some sort of React component to QStyleOption* translation. I view this as a large blocker to adoption, as it's difficult to do much in the way of complicated UI without lists.

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