Updates

[BrainBacon]

This issue will serve as a mailing list for important updates. Feel free to subscribe for notifications.

[BrainBacon]

The docs are now fairly content-complete check them out on the website. Styling and example links are still in-progress. Stay tuned for when the quality-of-life improvements come to the documentation website.

Call for contributors

If you would like to contribute to the plugin, a good place to start is by creating an example and filing bug reports if issues pop up or add a pull request for documentation if the information is not clear. See CONTRIBUTING.md for details and instructions.

[BrainBacon]

Significant update time!

If you haven't seen it already, the documentation website has received a lot of attention. Additionally, since the updates that happened to Babylon.js in 3.3.0 I went ahead and added experimental support for ES Modules and included the dependencies that became optional in the update in a built version of the library. You can pick the new version up on npm as vue-babylonjs@1.0.0-beta.5. Also, since the library is now built there is an option to install via the jsDelivr CDN.

See the documentation website for more details

Contributions are still welcome! Specifically right now I am trying to put together a comprehensive plan for testing. There are some challenges to overcome with getting proper testing implemented since the library is now built with ES Modules and testing graphics-based visual libraries is not straightforward. Please send me an issue or pull-request if you have solutions to constructing a testing infrastructure!

Thanks for all the support and feedback!

[BrainBacon]

Hi all, A new version of the plugin, vue-babylonjs@1.0.0-beta.6, is now live. This includes a complete Observable system that will allow you to attach listeners to your components that are triggered by BabylonJS Observables! See the Observable documentation for details!

Additionally I have noticed a common pattern emerging within some of the issues on this repository. When attempting to modify the scene some developers are expecting that components from this library are initialized in BabylonJS already. Previously I recommended that you use a watcher to check when the model has been bound, but in the event that there were multiple components needed this would become complex to reason about when all components were ready. Now I have implemented a series of custom vue events to alleviate this issue. The most significant of these is the complete event which will fire when all children of that component are initialized and ready to be modified. Documentation for these events can be found at
the Scene and Entity docs with a full example of using complete on the previously mentioned Observable documentation page.

In other news, I will be attending VueConf Toronto this November where I will be delivering a lightning talk about this library! Come say hi if you happen to be attending as well!

[BrainBacon]

I've released a new version vue-babylonjs@1.0.0-beta.7 which brings support for the highly requested loaders implementation. Please see the Asset documentation for details!

This also brings support for Babylon.js 4.0! Along with that Babylon.js and the loaders package are now peer dependencies, so if you are planning on using the npm package, please don't forget to install @babylonjs/core and @babylonjs/loaders alongside Vue-BabylonJS.

For those of you that haven't seen it, I gave a talk back in November about Vue-BabylonJS at VueConf Toronto. If you are looking to share this project with someone unfamiliar that can be a great video to get started. You can check it out on Vue Mastery.

I've recently started a new job which is why there has been a bit of a delay in updates, but I'm excited about adding some new stuff to the project now that I'm settled in and the major issues have been taken care of. Additionally I'm considering setting up a donation page, if you think this is a good or bad idea please let me know by tweeting me @brain_bacon.