Introducing SceneGraph 2.0

January 16, 2014

After an extensive review of our Python SceneGraph (the framework we provide for building standalone Fabric applications) we decided to take a step back and re-evaluate the core architecture of the SceneGraph. It was apparent that some design choices in the current approach could be revisited, and that alternative approaches would lead to significant improvement in the developer experience of the Fabric SceneGraph. We have been working hard on these changes, and are now ready to share with you some details on SceneGraph 2.0. This product will be released as part of Fabric Engine 2.0 in Spring 2014.

You can see a presentation deck on the new Scene Graph here.

The new Data-flow API will be much simpler to work with and will make building Fabric tools a simpler, easier process. We have focused on issues that can make Fabric development tedious in the current Scene Graph and have made them simpler and cleaner under the new API.

A key component of this work is the merging of  Fabric Splice and the Scene Graph into a common API. This means that Fabric developers will only need to understand one small API to build tools that run in the major DCC applications as well as in standalone Fabric applications.

The work on the Data flow API is well underway and we have been refactoring our own samples in order to validate the approach. This work has underlined how these changes greatly simplify the Fabric programming model and reduce the amount of code required to achieve sophisticated effects. We are confident that this will further reduce the barrier to entry for developers that want to build high-performance applications with Fabric.

If you would like to give feedback on this post, please join the conversation on our mailing list – you can sign up here.