Some experiments with Ar.js, THREEAR.js, React.js and Three.js. In a Future i will add other examples tests...
You can find the react-threear-example a simple example to show the THREEAR lib in action with React.js. This is the basic setup to start a project with the two libs.
This project was bootstrapped with Create React App.
There is also the basic AR.js and React example as discussed in this issue
This is a AR.js feature under development. You can test an example with THREEx API in the react-threex-example folder.
-
Start a project with the create React app with the command:
npx create-react-app your-project-name
-
Install Three.js and THEEAR.js with npm
npm install three threear
-
Check if in package.json are installed the two libs.
-
In App.js import the two libs (with const require)
-
In the
render()
method of the App Component inject THREE renderer and camera into theTHREEAR.source()
:var source = new THREEAR.Source({ renderer, camera });
-
Initialize the tracking process:
THREEAR.initialize({ source: source }).then((controller) => {
/* Three.js code here (mesh, materials... to be attached to the marker)*/
var path = './data/patt.hiro';
var patternMarker = new THREEAR.PatternMarker({
patternUrl: path,
markerObject: markerGroup
});
controller.trackMarker(patternMarker);
)};
- Remember to update the controller in the
requestAnimationFrame
:
requestAnimationFrame(function animate(nowMsec){
// measure time
// your measure time code here
renderer.render( scene, camera );
controller.update( source.domElement );
// keep looping
requestAnimationFrame( animate );
});
- In
return()
create a simple div:
return(
<div></div>
)
One important thing: resources (patterns, images, video...) must be in the public folder.
In every project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify