-
Notifications
You must be signed in to change notification settings - Fork 15
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
Meteor+React #16
Comments
@pilwon I've finished the first usable version of rocket:module yesterday. I'll be using it this week to import react-famous into Meteor and I'll post an example of that for the Meteor community to benefit from. :D I'd like to help update react-famous to Famous Engine 0.6+. |
I'd like to make a package for Meteor: rocket:react-famous (unless you want to, if you use Meteor). It'll showcase the use of rocket:module, which will showcase the use of react-famous. 😊😀 |
@trusktr Great to hear you made some great progress on |
For sure! The rocket:module package in Meteor is using npm to get deps and Webpack to compile stuff. Basically, we just need to work on #17 to clean up package.json and it'll work really well. |
Hi @pilwon ! ALright, so I've got react-famous working nicely in Meteor now. I'm going to start developing and will make some PRs soon. For now, check out my branch of react-famous. You'll notice that it's as minimal as possible. Check out the build scripts in I'm testing all of this in the reacfamo package, for now, until we can get react-famous updated. It's working great. I'm gonna post an example of it in Meteor in my example app, although it'd also be nice to update your react-famous-seed project with the bare minimal things: webpack, react, react-famous, and famous. Looking forward to getting this all running. Cheers mate! 😃 |
Hello @pilwon! I want to finish
rocket:module
then use it to import this into Famous.I tried to make a basic wrapper for Famous
Node
in my Meteor project to see how it might be, and I love the imperative nature of React; it'll be awesome to use React with Famous. It seems that to make the Node work, I have to return a React.Component from the render function of my componentNode
that also extends React.Component, so it creates a virtual DOM and a real DOM. Did you ever find a way around this? Maybe there's a way to make React have a virtual DOM for our Famous components but not output that to real DOM so it doesn't slow things down?Famous Engine is getting a lot better. In 0.7 (coming out soon) they have the new Element Cache life cycle with an official way to get a DOMElement's DOM element!
The text was updated successfully, but these errors were encountered: