In Aptugo, we believe programming should be quick and simple, so even extending Aptugo is a simple thing, can be done in minutes, and can be done either inside Aptugo or using your old text editor without installing anything extra.
A regular element is split into two parts:
And they're clearly defined inside the same file!
The template file starts with the definition enclosed in a multiline comment /* ...contents */ and anything after that is considered the source of your document.
Let's work with a sample:
/*
path: pieChart.tpl
icon: ico-pie-chart
sourceType: javascript
unique_id: oOgmBJJQ
*/
That's the definition of an element named "pieChart", with a "ico-pie-chart" icon, the source is set to javascript, and it has an obscure unique_id
That's the basic definition for any element in Aptugo. You can always check the full reference for Aptugo elements definitions
Anything below the definition is considered Source code, as Aptugo doesn't interfere with your code then it can be in any programming language, heck! it can even be binary content.
Now, if you define properties, that's another history: You're instructing Aptugo to go and update your source with the property value.