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

Suss out whether react-native can be a thing #70

Open
StoneCypher opened this issue May 21, 2015 · 3 comments
Open

Suss out whether react-native can be a thing #70

StoneCypher opened this issue May 21, 2015 · 3 comments

Comments

@StoneCypher
Copy link
Owner

Currently getting help at https://github.com/jrm2k6/hello-flocks/blob/master/index.ios.js from @jrm2k6

@jtremback
Copy link

Need to get rid of React.render. I suggest you base the new architecture on setting the state of a special flocks root component inheriting from <View/>. Might as well switch it in the html version as well, seems like it would be cleaner anyway.

<FlocksRoot>
  <Stuff/>
</FlocksRoot>

@StoneCypher
Copy link
Owner Author

That would mean that a user's component couldn't be the root, which poses problems of its own.

@StoneCypher
Copy link
Owner Author

I may do that in native, if there isn't another choice, however.

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

No branches or pull requests

2 participants