(my) Best Practices for Aurelia - Application Structure. We get a lot of questions in the official Aurelia gitter regarding some basic best practices so I wanted to share a few quick thoughts and examples that are my own - One of the first things that comes up when structuring an application with an intention of later using it in production is How should I structure my application to scale?

The truth is at first, it doesn't matter. Start simple by putting everything in the src folder until you have the need to break things out. Once yhou hit that point then check back here, read my ramblings, and let me know what you think in the comments. Breaking our App into functional areas First things first - we have a few basic common pieces of functionality that no matter what kind of application you are using you will need. Services Models Templates (Widgets) Configs (optional) Services Sample structure - - /app | -- /services | -- /dataservices | -- session.js | -- datacontext.js | -- /models | -- /templates | -- /configs Models.

Best Parts of Aurelia Part 1 – Composing custom elements / templates. In a renewal of a previous set of posts that I did around Durandal.js, I wanted to start a new series on Aurelia, the successor to Durandal.js and Caliburn.Micro.

Aurelia is an awesome collection of libraries that make up an amazing framework that is focused on future specs of the JavaScript language while still supporting a large set of current browsers. Code For this quick highlight of the features we will use this repo, which is a basic layout out with multiple columns which contain some widgets – It is a basic fork of the Aurelia skeleton-navigation. For any questions please visit the official gitter – Composing templates and custom elements What’s the difference between using the compose element vs a custom elements? Compose: Can be used to dynamically compose templates (not forced to define the template type)Can use same view model but different view for each item in an arrayYou can separate your views and view models into the smallest bits of (re-usable) code needed. Custom element:
QuiestJ-leBlog - Veille techno d'un étudiant en informatique.