Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upWorking towards component parity with React Native #210
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 ofQListVieworQTableView. I'm honestly not even sure what this translation would look like, given thatQtdoesn't like widgets to be children of theQList*likes, so there would have to be some sort of React component toQStyleOption*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.