The Aurelia Story
Aurelia is project created by Rob Eisenberg, a former member of the Angular 2.0 team and creator of Durandal and Caliburn. In his own words…
After reading through an example of porting a simple app from angular 2 to Aurelia I was intrigued and felt it was worth giving it a go to find out what it was like, how different it was and how close it was to being production ready.
The less2css site allows you to try out less and see the resultant css. Its been a great learning and testing tool, but has been out of date a while (version 2 not available) and it’s been frustrating that its not hosted on github pages (it hasn’t been that reliable) and that it requires a server-side component. I thought this would be a good project to try Aurelia out on.
Creating the Skeleton
First I created the repo..
Then, following the getting started guide…
I can see there is a
gulp serve command and when I run that I get a web server and an Aurelia site that works.
A single text editor
The first thing I’m going to do is try removing all the pages but one.
index.html is just a bootstrapper and the rest of the files are in src. I’ll keep the router for now, but remove the nav bar.
Which downloads the files and puts them into the jspm_packages folder. A google for codemirror jspm had shown that I need an extra bit of configuration in package.json, so I add that..
You might recognise the syntax as being close to requirejs and that may be because there are some familiar faces involved in jspm that contributed to requirejs.
Then I add some code to see if I can get at the library now…
And when I run the site, I see it is available!
The next thing I need is a DOM element, to give to code mirror in order for it to create its editor. After a little searching I see I can use the
ref attribute to get an element to be assigned to my view model. Unlike angular this doesn’t require any prefixing, but the attribute is used in polymer too, so it may be also in a spec associated with web components and that may protect it against future additions to the HTML spec.
At this point you might reel back in horror at getting a reference to an element inside your code. In Angular you might be using directives for a layer of dom manipulation and controllers for manipulating those directives and containing the model. Or you might not be using any controllers at all, treating directives as your controllers and abstracting as much logic as possible to services. This second approach fits better with what Aurelia does (it has no controllers, just a view model which can interact in both directions with the dom), but it also fits with what Angular 2 has planned. The reasoning ties into web components, because a native element/web component exposes an API that might not be so low level. For instance the video element has a play function on it, if you want to play that video when an event is raised, you need to access the element and writing another piece of code that mirrors the API may not be worth it.
So, my first attempt was to use a property setter. I had the following html template in
And view model in
and I could use it in my main view…
Which gives me a text editor on the page.
You can see that it seems to be missing some styling, so next I add gulp-less to the skeleton and get it set up as part of the build. However I need a way of including the code mirror css file, downloaded by jspm. From the skeleton project I see bootstrap is using
! (familiar to require js users), so I looked up the path to the css by finding where jspm downloaded the file to and added…
And I can do the same thing to include the CSS/Less language highlighting plugin and a cobalt theme…
But I found I was getting some strange styles from CodeMirror, supposedly caused by code mirror being initiated when the element is not visible. The problem was that code mirror was being initiated when hidden and I realised that instead of using an element setter, I need to add a function called
attached to my view model and that will get called at the right time.
And below is shown my now working text editor…
Multiple text editors
Next, I want to try having two editors, one of which is read only - the left hand side will be the less editor and the right hand side the resultant css editor which will be read only. Strangely I found that having the two elements be the children of a single parent didn’t work, but everything went okay when I added sub div’s which will probably be needed anyway.
Next, I need to get hold of the readonly attribute I set above inside my element. I tried seeing if it was just put on the viewmodel, but it wasn’t. However, a short ‘ES7 attribute’ later and it worked..
I also added a custom element attribute
@customElement("cmeditor") though it seemed to be fine without.
The next risky thing is browser support - as it seems IE9 support is a new thing. So I followed the instructions and hit problems. I solved it and sent a PR to update their instructions. Hopefully it should be easier for the next person!
I want to set up the bindings and have less compile source code as the user types, so I write a utility class that loads less from our CDN and a static gulp task that generates a list of less versions (since the CDN has no directory listing we can scan). If you are coming from Angular 1, you might expect Aurelia to want to know about services, but it doesn’t have its own module system (it uses jspm), you just create a new ES6 module that does what you want.
I add another
@bindable value; to the editor, meaning I can bind to it from outside. Then I update the value when code mirror changes…
Now, I need to bind to this
value from outside my code mirror editor element. A one-way binding means data flows from the view model to the element, but I can also use a two-way binding, so data flows both ways, which means I can pick up changes to the editor in my main view model..
Now my view model updates a
css property when the Less source code is edited. So, I bind this to my 2nd editor..
Then I need to make my editor update its contents when the value changes. I got a bit stuck here, because I initially tried a property setter like lessSrc, but that doesn’t work because the
@bindable annotation adds a getter and setter as part of its implementation. The solution is that when you have a
@bindable, a function (if it exists)
xChanged will be called when the field changes. So I add one…
And now I have 2 editors, when I edit Less code in one, the CSS code in the right changes!
Saving to the URL
I want the less code to be saved on the URL so that you can link to code examples and while playing with setting
location.hash, I find you get a routing exception even when routing isn’t configured. So, I decided to start removing routing. Aurelia is built as a very small core framework with plugins for everything (from templating to routing to http). Aurelia is generally started with Aurelia bootstrapper which imports all the modules and then you choose which ones you want to initialise. From the documentation, here is a setup example…
However, it seems that modules are always imported, you can only choose which ones are started and I don’t want the source on my page at all, so I forked the bootstrapper file and adjusted it to remove dependencies to the router and history. This seems to work well and I can now load the app without including any router code. Once bundling is announced I may re-visit this as it seems there should be a simpler solution.
To get the URL to contain the current state I first need to get the data on to the URL. So, in the app element (which you might think of as the main controller), I just need to update the URL when the lessSrc value changes.
Now I’ll look at loading - I need to set the lessSrc variable from the constructor for when the page loads..
And I need to add a line to the editor element so that it picks up the value on startup..
And that works!
I also took the styling from the existing site, so now it is looking more familiar.
On an external server without bundling, the site takes 12 seconds to load - please see my next post for how I tackled bundling and how it effected performance.
In later posts I will look at binding the options panel and evaluating what I think of Aurelia.