-
Notifications
You must be signed in to change notification settings - Fork 202
Coming from OSG (Desktop)
Work in progress...( feel free to change/add whatever you think it should be here)
If you are reading this, probably you already know what is OpenSceneGraph (OSG) and what kind of things you can do with it. You will find that OSG.js maybe is not that powerful, but definitely is not a toy.
If you also are a newcomer to modern web development you will need some effort to feel yourself comfortable while coding with osgj.js. I mean probably all of us did play with html, javascript, css, etc.. but coding libraries, class hierarchies, using dependencies, webGL and so on is a bit different. Think in the first time you took contact with OSG: tons of documentation, learn CMake, searching dependencies, running the examples, etc.
TODO explain a bit:
- You need a server
- Async Programming/ Promises
- More...
At the moment OSG.js documentation needs a bit of love, but we are on it ( if you're reading this is a good signal)
The first thing you need is to install Node.js. If you already know about grunt, webpack etc, you might want to start right now! Then follow the instructions in the Readme.md file. Be aware, you will need to use a command-line tool and also a git client.
If you prefer to know what's going on under the hoods:
- npm
- Grunt
- Webpack
Explain binaries, server, headers, etc. and link to convert models from OSG.
Even though OSG.js is pretty similar to OSG, there are some differences you should know before you get crazy: ( TODO:explain).
- Node is also a Group.
- Matrix multiplication.
- Shader construction
- State managing ( ON | OFF stuff)
- Text differences
- PagedLOD and DatabasePager.
- Reading files.
There are a lot of tools you can use to debug your javascript/webGL code. Here you have some of them that you will find essential:
- Chrome developer tools
- Shader Editor chrome extension
- WebGL insight chrome extension
Add more stuff