I'm curious, what are the design considerations that make this specifically targeted at web and mobile? That is, what is different here than existing engines?
- Alon On Wed, Apr 9, 2014 at 12:05 PM, Floh <[email protected]> wrote: > Hi, > > just wanted to let you guys know that I started a new "weekend-engine" a > couple months ago, mainly as a sort of experimentation testbed of what a > small C++11 3D-engine mainly built for web and mobile could look like: > https://github.com/floooh/oryol > > Progress will be slow since it's a spare-time project, but one thing that > will be useful (IMHO) in the short term is a growing list of samples which > demonstrate and test specific, isolated features: > http://floooh.github.io/oryol/ > > I think these samples will be useful for reporting, testing and tracking > regression bugs in various browsers in the future (I learned that this is a > bit complicated with relatively big engine demos like the Nebula3 demos, > because it's hard to create isolated test cases). > > Cheers, > -Floh. > > > -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
