Why did we build Aria Templates
On one hand, our support standards were based, and are still based, on many factors including usage stats and the upgrade paths available for our customers in term of resources (computers, browsers, ...). For instance, we still have a significant number of users on Internet Explorer 6. On the other hand our professional applications are more and more complex, involving 100+ different available screens.
All these events prompted us, back in 2009, to start thinking at a more adapted and powerful solution for our technical stack: Aria Templates was born.
Seriously, a new framework ?
The first question to ask is « Why not use an existing library? »
The core idea that led us to the create Aria Templates is the advanced client side template engine. With such an engine :
- We can manage in the DOM at one point in time only what is visible on screen.
- We can also benefit of bidirectional data bindings.
- We can have automatic refreshes.
- We can hide browsers hacks behind CSS templating.
- Efficiency and performances are finally here! In other words, « yes, we can ! »
Why open source Aria Templates?
Amadeus has a strong tradition of using a lot of different open source softwares. We use it widely across many of our platforms. Unfortunately we are less used to contribute.
The first release available is version 1.2, as we think it is now quite stable. It has been used for more than 2 years internally. More importantly, we already started thinking about what changes to commit for next version 2.0.
Trying to create a wider community around AT, gather feedback, and help us building the future of Aria Templates was an opportunity we couldn't miss.