Case Study: Ivee 3D Editor - Aurelia+Azure+ASP.NET+Redux+ThreeJS




Case Study: Ivee 3D Editor - Aurelia+Azure+ASP.NET+Redux+ThreeJS

Posted by Aurelia on .

Case Study: Ivee 3D Editor - Aurelia+Azure+ASP.NET+Redux+ThreeJS

Posted by Aurelia on .

Today, I'm pleased to introduce you to Daniel Radu. Dan is a member of our Aurelia community who has been building some pretty awesome stuff by combining Aurelia with Microsoft Azure. I'll let Dan tell you about his experiences, in his own words...

Ivee 3d Editor is an online editor which allows the creation of beautiful 3D presentations. It provides features like adding various 3D objects - cubes, spheres, torus, etc., configuring materials, textures, shaders, providing animations, tweening etc.

Ivee 3D Editor

In the following article I'm going to explain a bit about the internals of the editor and my journey of building Ivee using Aurelia and ThreeJS.

On the server-side, Ivee 3D Editor uses a .NET Web API with a SQL Server database to store user authentication information. The editor output is stored as a JSON file on the server, in a dedicated user space. The database and web application is hosted on Microsoft Azure.

Why Aurelia?

I started working on Ivee on Dec 2016. It was a pet project, and I couldn't afford to dedicate a lot of time, only nights and weekends. My regular job is full stack .NET developer and the frontend framework I'm using at work is Angular. That means I didn't have much experience (even knowledge, to be honest) with Aurelia.

I came across Aurelia by talking to my friend Dragos, who was disappointed by Angular and its awkward syntax - which I never liked myself. He started exploring Aurelia and I was interested to learn how to use it as well. I thought learning another framework would be beneficial to my technical knowledge.

At that time, my thought was that if things are not working well with Aurelia, I can always go back to Angular.

Choosing Aurelia CLI

So I started looking at Rob's video on and from the first go I was impressed with the simplicity and naturalness of Aurelia. I installed Aurelia CLI and in 10 minutes I had a fully running application, with routing, components, data binding and output events. From that point, I had no doubt about my choice, even though I had a little fear that along the way I will encounter difficulties. With this in mind, I set my expectation that my plans to integrate legacy or non-Aurelia libraries might not work as smoothly as I would like.

Later on, it turned out that this is one of the features that sets Aurelia apart - the ease of integrating almost everything with Aurelia without spending hours and hours of research and bug chasing.

Integrating ThreeJS (and other libraries)

After setting up the app component and the routes, which was a breeze, I must say, my next concern was how I could integrate ThreeJS. I was pretty familar with the library, as I had tried various JavaScript experiments, but never using TypeScript and Aurelia. After digging a little bit, I found that there was already an npm package for ThreeJS. I installed it and I checked the Aurelia documentation about how to configure libraries. In no time, I learned how to modify the aurelia.json file to include the client libraries and I had my little three js scene up and running - the little rotating cube at the XYZ axis that's on the Ivee 3D Editor home page.

The configuration for ThreeJS in my aurelia.json file looks like this:

  "name": "three",
  "path": "../node_modules/three/build",
  "main": "three"

Note: The Aurelia CLI can automatically install and configure most libraries, but you can always do it manually, as shown above.

The usage in the component is trivial:

import * as THREE from 'three';

export class Viewer {  
  private selectedObj: THREE.Object3D = null;
  protected w: WglUtil = new WglUtil();
  private clock: THREE.Clock = new THREE.Clock();

  private onDocumentMouseDown(e) {
    this.selectedObj = this.w.dndSelectedObject;

    if (this.selectedObj) {
      let obj: Iv3dObject = <Iv3dObject>this.selectedObj.userData;

  public animate() {
    let elapsedTime = this.clock.getElapsedTime();

Other libraries I'm using:


Authentication is a tricky part of single-page applications which use routes. You want to have authenticated pages, like user settings, as well as pages with anonymous access like home page, login, and signup pages. Aurelia helps a lot with its very own setRoot method which can be called conditionally:

let userSvc: UserService = aurelia.container.get(UserService);  
let url = window.location.href;  
let noAuthPages: string[] = ['home', 'editor', 'viewer', 'login', 'signup'];  
let isNoAuth = noAuthPages.filter(item => url.indexOf(item) >= 0).length > 0;

aurelia.start().then(() => {  
  if (userSvc.isAuthenticated || isNoAuth) {
  } else {

On the server side I use token authentication using ASP.NET Identity Framework. The token is passed with every authenticated call. On the client side, the token is stored in the browser's local storage, managed by the UserService service class.


Integrating data with Aurelia was really easy and I loved that there are options to either use Fetch API, using aurelia-fetch-client or XMLHttpRequest API using aurelia-http-client. Preferable is Fetch HttpClient, however, for compatibility reasons, you can use the xhr plugin.

Dependency Injection works nicely with Aurelia and you can easily swap one plugin with another. I started with xhr, but later on I moved to fetch client with minimal changes.

Here is a sample code from my data service:

@inject(HttpClient, UserService)
export class DataService {  
  constructor(private httpClient: HttpClient, private userSvc: UserService) { }

  loadData(url: string, addToken?: boolean) {
    let headers: Headers = new Headers();

    if (addToken) {
      headers.append('Authorization', `Bearer ${this.userSvc.token}`);

    return this.httpClient.fetch(url, {
      credentials: 'include',
      headers: headers
    }).then(response => {
      return this.handleResponse(response);


I use forms in for user authentication (login, signup) and user space management (a feature where user can upload, rename, delete, download files, create, rename, delete folders). The two-way binding for controls is natural in Aurelia and you don't need to do anything special.

How neat and tidy is this template, when you tell Aurelia to bind the userName property to your input and apply validation:

  <label for="user">Username</label>
  <input type="text" name="user" value.bind="userName & validate">

Validation, which is a must when working with forms, was very easy to integrate thanks to the aurelia-validation plugin.


The validation rules are simply added to the component early, somewhere in the constructor or attached hook. I really like the fluent validation API:

  .ensure((m: LoginPage) => m.userName).displayName("Username").required()
  .ensure((m: LoginPage) => m.password).displayName("Password").required()

Then use ValidationController to apply the rules by calling the validate method which returns a promise:

  .then(result => {
    if (result.valid) {
      this.loginError = false;
      this.loginErrorMessage = null;
    } else {
      this.loginError = true;
      this.loginErrorMessage = 'Validaton error(s):';

      for (let error of this.validationController.errors) {
        this.loginErrorMessage += error.message + ' ';

It can't be any cleaner than this.

Using Redux

Given the fact that most of the user work is performed on the client side, I wanted to have a proper way to manage state in Ivee 3D Editor. One great pattern for managing application state is Redux.

Having used Redux in Angular 2, I was familiar with the patterns: actions, reducers, state, stores, effects, etc. However, Angular 2 takes advantage of ngrx library which does a lot of heavy lifting and returns Observables ready to use by Angular components.

I couldn't find anything similar for Aurelia, however the standard Redux NPM packages works without any issue. I spent a bit of time - one user story, about the whole 2 week sprint - to integrate the packages and create my own functionality for loading and saving editor data as JSON files, but it was really worth it.

The Redux configuration in the aurelia.json file looks as follows (redux thunk is used for middleware associated with asynchronous calls, like Ajax or Fetch calls):

  "name": "redux",
  "path": "../node_modules/redux/dist",
  "main": "redux.min"
  "name": "redux-thunk",
  "path": "../node_modules/redux-thunk/dist",
  "main": "redux-thunk.min"

An example for load data actions:

export class DataMgrActions {  
  static actionTypes = {

  constructor(private dataSvc: DataService, private userSvc: UserService) { }

  // action creators
  loadData = (fileName: string) => {
    return {
      type: DataMgrActions.actionTypes.LOAD_DATA,
      payload: fileName

  loadDataSuccess = (data: DataModel) => {
    return {
      type: DataMgrActions.actionTypes.LOAD_DATA_SUCCESS,
      payload: data

  loadDataError = (error) => {
    return {
      type: DataMgrActions.actionTypes.LOAD_DATA_FAIL,
      payload: error

  loadDataSvc = (fileName: string) => {
    return (dispatch, getState) => {
      return dispatch(() => {
        return this.dataSvc.loadFile(fileName)
          .then((response: any) => {
            let result: SvcResponse = <SvcResponse>response;
            if (result.result) {
              return dispatch(this.loadDataSuccess(;
            } else {
              let error = new Error(result.message);
              return dispatch(this.loadDataError(error));
          }).catch((error) => {
            return dispatch(this.loadDataError(error))

The load data reducers:

export class DataMgrState {  
  data: DataModel = null;
  isError: boolean = false;
  error: any = null;
  actionState: ActionState = ActionState.none;

const initialState: DataMgrState = {  
  data: null, isError: false, error: null, actionState: ActionState.none

export function dataMgr(state: DataMgrState = initialState, action: IvAction) {  
  switch (action.type) {
    case actions.DataMgrActions.actionTypes.LOAD_DATA:
      return <DataMgrState>{
        actionState: ActionState.pending
    case actions.DataMgrActions.actionTypes.LOAD_DATA_SUCCESS:
      return <DataMgrState>{
        data: action.payload,
        actionState: ActionState.completed
    case actions.DataMgrActions.actionTypes.LOAD_DATA_FAIL:
      return <DataMgrState>{
        data: null,
        isError: true,
        error: action.payload,
        actionState: ActionState.completed
      return state;

I separated my components into container and presentation components. The containers are dealing with the store, despatching actions and handling responses, whereas the presentation components simply get data and output events to their parents, following the unbeatable one-way data flow pattern.

Here is an example of my editor-page component which is the parent of the main 3D editor:

export class EditorPage {  
  fileName: string;
  data: DataModel;

  store: Store<DataMgrState> = createStore(dataMgr,
      thunk // lets us dispatch() functions

  private dataMgrActions: DataMgrActions;
  private actionState: ActionState = ActionState.none;

  constructor(private ea: EventAggregator,
    private dialogService: DialogService,
    private router: Router,
    private dataSvc: DataService,
    private userSvc: UserService
    ) {
      this.dataMgrActions = new DataMgrActions(this.dataSvc, this.userSvc);

  activate(params) {
    this.fileName = params.fn; // from route

  private loadFile() {
    if (this.fileName) {
      this.actionState = ActionState.pending; => {
        let state: DataMgrState = <DataMgrState>;
        this.actionState = state.actionState;
        if (state.isError) {
        } else {

This is the corresponding HTML template, where the data property (of DataModel type) is passed as input to the presentation component editor:

  <require from="../../editor/editor"></require>
  <editor data.bind="data"

As usual, there are lots of shades of gray, and, depending on how complex your application is, soon you realise that input data and output events in a component structure of more than three levels is hard to follow, debug and maintain. But don't despair, the smart people behind Aurelia thought of that too and they introduced the Event Aggregator which is a beautiful implementation of a well-known pattern. Used wisely, the event aggregator is a powerful tool which can make your code really tidy and easy to understand and maintain.

For example, to manage errors in a central location in your app, you can use Redux and that works nicely. However, using the Event Agreggator you can publish a custom error (applicable at every component level) and let a central component (like App) handle it.

A quick example is how I check if WebGL is enabled:

if (!WglUtil.detectWebGL()) {  
  this.ea.publish(CustomEventNames.APP_ERROR, { message: 'Your browser doesn\'t support WebGL.' });

In the root component, app.ts, I subscribe to my error custom event. Then I use a simple dismissable popup component to display the error message to the user:

this.appErrorSubscr = this.eventAggregator.subscribe(CustomEventNames.APP_ERROR, payload => {  
  this.showError = true;
  this.errorMessage = payload.message;

The property errorMessage is passed in the template to the error component:

<require from="./components/error/error"></require>  
<iv-3d-error show-error.bind="showError" error-message.bind="errorMessage"></iv-3d-error>  

To avoid memory leaks, I always dispose the subscription in the detached hook:

detached() {  

Dynamic Content

Ivee 3D Editor is able to display HTML content in configurable panels. My intention was to leverage the power of HTML in the presentations created using the editor. To be honest, I was prepared to leave this feature out, thinking it might be difficult to integrate dynamic content in a component. Aurelia came to my rescue though, and this was an eye opener for how powerful Aurelia is. Behind its simplicity there are a lot of complex features which developers can reuse and take advantage of. After checking the documentation and after digging in a few Stack Overflow questions, I found that there is a neat way to override the view strategy of a component.

This is the code of my ContentPanel component which uses the ViewCompiler service to create the component view at runtime, based on content provided by a custom model (AdditionalContent). If you check the code, there is a binding context hooked into the view, which means that even after the initial creation, the view will be updated if the content changes, as it happens with a normal, static template. These features are out of the box, without installing any additional plugin, 3rd party library or framework! I love Aurelia, because things just work!

import {inject, noView, ViewCompiler, ViewSlot, Container, ViewResources, bindable} from 'aurelia-framework';

import { AdditionalContent } from '../../models/additional-content';

@inject(ViewCompiler, ViewSlot, Container, ViewResources)
export class ContentPanel {  
  private viewCompiler: ViewCompiler;
  private viewSlot: ViewSlot;
  private container: Container;
  private resources: ViewResources;
  private bindingContext = {
    content: new AdditionalContent()

  @bindable content: AdditionalContent;

  constructor(vc, vs, container, resources) {
    this.viewCompiler = vc;
    this.viewSlot = vs;
    this.container = container;
    this.resources = resources;

  reloadView(content: AdditionalContent) {
    let template = `
    <div class="panel panel-default" id.bind="" css.bind="content.css" show.bind="content.showFlag">
        <div class="panel-heading">
            <h3 class="panel-title pull-left" inner-text.bind="content.title"></h3>
            <button type="button" class="close" data-dismiss="alert" aria-label="Close" click.trigger="content.hide()"><span aria-hidden="true">&times;</span></button>
            <div class="clearfix"></div>
        <div class="panel-body iv-3d-content-panel-body" innerhtml.bind="content.content | sanitizeHTML">
    content.hide = () => {
      this.content.showFlag = false;
    }; = () => {
      this.content.showFlag = true;

    this.bindingContext = {
      content: content

    let viewFactory = this.viewCompiler.compile(template, this.resources);
    let view = viewFactory.create(this.container);

  contentChanged(newValue: AdditionalContent) {
    if (newValue) {

You can see the dynamic content panels in action in my Aurelia presentation, created using Ivee. Click on the topics on the left and you can see the coresponding panel opening.

Another win, I wanted to provide the user with a nice HTML editing experience and I looked for a nice HTML editor that I could integrate. I chose squire-rte. It almost goes without saying: to integrating the Squire editor was as easy as 1-2-3...

HTML Editor

Exposing Viewer API

I always liked extensibility. The thought of exposing your own object model to the developer is fascinating. With Aurelia and TypeScript / ES6, I found that this is actually possible, providing you have designed a nice component structure and a properly written API. Ivee 3D Editor has two major features: the editor and the viewer. The editor is the tool that allows the users to create presentations, by adding objects, setting properties, creating animation timelines, etc. and the viewer is the tool that puts all the presentation parts together and executes them.

But what if you want to interact with the presentation at runtime? No problem, Aurelia and TypeScript / ES6 work for you. The current instance of the Viewer type is available for scripting, using plain JavaScript:

private evaluateInitScripts() {  
  if (! {

  try {
    let scriptCode: string = `
var viewer;  
${ ? : ''}

  } catch (e) {
    console.log('Init script creation failed. Check the error: ', e);

  try {
  } catch (e) {
    console.log('Update script creation failed. Check the error: ', e);

  try {
    let scriptCode: string = `
viewer = this; // this line exposes the viewer for runtime use  
${ ? : ''}

    if (this.runExecInit) {
      let fn = new Function(scriptCode);;
  } catch (e) {
    console.log('Init script evaluation failed. Check the error: ', e);

Admittedly, exposing the API opens the door to vulnerabilities, but in my case, the Viewer only provides access to the presentation runtime objects. Examples of Viewer methods and properties that can be used at runtime:

  • data: DataModel - the presentation data object model;
  • w: WglUtil - an instance of the WglUtil class, which contains a set of helper functions for ThreeJS;
  • findObjectById(uuid: string) - finds a presentation object by its unique identifier;
  • findObjectByName(name: string) - finds a presentation object by its unique identifier;
  • find3dObjectById(uuid: string) - finds a 3D object by its unique identifier;
  • find3dObjectByName(name: string) - finds a 3D object by its name.

Just as a quick test, I used this feature to create a panoramic image for the Aurelia presentation (this code is executed at runtime, when the presentation is loaded):

function addSkyBox() {  
  var cfg = {
    srcFile: 'http://localhost/Iv3DEditorApi/data/ivusers/',
    size: 1024 

  viewer.w.addSkyBoxFromFile(cfg, viewer.mainGroup);


Presentation modified at runtime


The Ivee 3D Editor is still in alpha. It has many features, timelines, tweening, data sources, shaders, but it's still rough and needs a lot of refining. However, I think that for a one man job outside working hours, it is a pretty good achievement. All these features would have been much more painful to implement without Aurelia.

Aurelia is beautiful because it doesn't get in your way; it guides you to do things then goes on the side, admitting that you need to focus on your business. It helps and it doesn't ask for anything in return. It is your quiet and supportive friend always close to you during your journey, ensuring that you have all the resources necessary to climb the highest peaks.

We live in amazing times, where dreams get closer and closer to reality. Our job now is much simpler than before - we only need to learn and use these wonderful gems that people like the Aurelia team create. Aurelia is a gem that doesn't have a huge learning curve and the time invested to learn it is returned a thousandfold. If I had to add my own motto for Aurelia, it would be as simple as this: "Aurelia - let amazing things happen".

View Comments...