Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Working towards component parity with React Native #210

Open
agg23 opened this issue May 24, 2020 · 0 comments
Open

Working towards component parity with React Native #210

agg23 opened this issue May 24, 2020 · 0 comments

Comments

@agg23
Copy link
Contributor

@agg23 agg23 commented May 24, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.