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

Interfacing with react.js #147

Open
janat08 opened this issue Jun 29, 2017 · 6 comments
Open

Interfacing with react.js #147

janat08 opened this issue Jun 29, 2017 · 6 comments

Comments

@janat08
Copy link
Contributor

janat08 commented Jun 29, 2017

Would it possible to try and interface with react.js, since the idea with OOP components is that they're shareable where react.js has more popularity.

@janat08
Copy link
Contributor Author

janat08 commented Jun 29, 2017

this belongs in common package supposedly.

@janat08
Copy link
Contributor Author

janat08 commented Jun 29, 2017

is that something that could even be well done, where you use react for boiler plate that would come with writing a widget avoiding react.js easily.

@mitar
Copy link
Member

mitar commented Jun 29, 2017

I do not understand what you have in mind here?

@janat08
Copy link
Contributor Author

janat08 commented Jun 29, 2017

I suppose mapping api calls between each other such that you can override them and etc, so that importing react component doesn't mean that it's alien or that you have to write in react.js further down the chain. I hardly know react.js.

@janat08
Copy link
Contributor Author

janat08 commented Jun 30, 2017

edited

class convertedWidget extends ReactConverter
mixin(){return [reactWidget]}

They say react.js constantly breaks it API and has no computed property or if for that matter. So basically you take it's render() method and create a template out of it that you then pass into convertedWidget template() method. With like 3 state management packages for react and it being able to compile to native mobile, it should be easy to recompile to blaze-components.

@mitar
Copy link
Member

mitar commented Jun 30, 2017

Yes. That was somehow planned with the whole idea of base component which would then be extended into react and blaze component. But then, somehow I never got to do it.

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