As mentioned in the Introduction chapter, it is advisable to read the Monterey overview document before using this User manual with intent to create new or manage existing Aurelia applications. This recommendation is the consequence of the fact that Monterey is a unique tool, that requires some familiarization.
For reader's convenience, here is a copy of the Monterey definition from the Monterey overview document:
Rather than creating yet another Integrated Development Environment (IDE) application, AureliaTools team's aproach is to "integrate all development tools, including various IDEs, CLI tools, File managers into a single top level "command center" (aka HUB) application. We named this application Monterey
Monterey acts as a hub with Graphical User Interface which allows activation of each integrated tool (often referred to as
tile). In this initial implementation, the application developer is in charge of "playing the tiles" in a meaningful sequence, in order to start from a blank slate and end with a working application.
Monterey's interactions with the integrated tools go beyond activation - monterey's mimics the human operator, and collects the information from one tile with the intent to pass it to the next.
As an example check the "selecting the application template" on Image 3 in the Creating the application article
The click on the drop-box item results with a several actions behind the scene:
- get the name of the selected item
- fetch the zip file with that name from GitHub and unzip it in the folder where the application will be stored
- unzip the file
All these actions would otherwise be done by using the browser to access the GitHub and the console application to run the command
git clone xxxx.git - and it is the application developer who uses the clipboard to transfer the information from the browse to the console