What is the App launcher?

Monterey is designed to be (user) extensible and that feature is facilitated by the App Launcher Monterey utility (we use the name “features” to reference utilities – see more about features here). You can find a lot more about App Launcher on this ¬†user manual page.

Here are a couple of screenshots illustrating App launcher user interface:

image-1
Image 1: How to integrate the console with Monterey

Aurelia Tools maintains the registry of all “user added features” as shown below (this view is rendered by a click on ‘Share this app launcher’ button on Image 1 above.

image-2
Image 2: registering your new ‘feature’ with Monterey features registry with the intent to share it with other users.

Do not like to read manuals?

If so, we provided an easier method that will keep you from getting lost. Check just this small section of the Monterey user manual for details – here are a couple of screenshots for enticement ūüôā

image-1
Image 1: First step into live help system, which provides the brief descriptions of the key user interface elements on Monterey’s main view
image-2
Image 2: Hovering the cursor above ‘App launcher’ tile results with a tooltip that provides the link into the relevant page of the Monterey user manual.

What can Monterey do?

This initial preview is very limited when compared with our plans for Monterey. It is also quite capable already, when used to replace the most likely Aurelia application development workflow which is based on the Sublime-like text editor, console and a browser, starting from skeleton-esnext template. As explained in the related README.md¬†document, you would start by creating the local copy of the that template and issue a series of commands in the console, invoking CLI tools like ‘npm’, jspm’ and ‘gulp’ and using tools like BrowserSync¬†invoked by Gulp scripts.

Monterey does this same job in a lot more user friendly way, via modern GUI as shown next using the skeleton-esnext template. These screenshots and their sequence should be self-explanatory. There are some added comments where that is not true.

image-1
Image 1: First page of the Monterey app creation wizard
image-2
Image 2: Second page of the Monterey app creation wizard
image-3
Image 3: Third page of the Monterey app creation wizard, presenting the project configuration FYI
image-4
Image 4:¬†Monterey shows its “understanding of the project structure by presenting this automatically created build in run workflow
image-5
Image 5: Task manager running stage (executing the ‘npm install’ task).
image-6
Image 6: Application building workflow reached the ‘gulp watch” task and Monterey presents the URL that will invoke the browser and render the app.
image-7
Image 7: Stopping the ‘gulp watch’ task using the Task manager

While the above 7 screenshots illustrate the full “create, build and run” cycle, this is a small fraction of Monterey’s abilities. We have built already some of the tools like NPM and JSPM manager, which can be used in many different scenarios (yet to be implemented, though)

image-8
Image 8: Monterey’s built in NPM package manager
image-9
Image 9: Monterey’s built in JSPM package manager

Subsequent versions will add more package managers and module loaders and the workflows needed to support tasks like

  • upgrade an Aurelia app to the next version of the Aurelia framework
  • convert an aurelia app from using JSPM loader to use Webpack loader
  • analyze compatibility of Aurelia framework modules version with third party modules.

All these projections of the future (see possible future plans for Monterey for more details) are just that – projections.


Did you like this article? Would you like to see any other ‚Äúbrief story‚ÄĚ about Monterey? Give us your feedback here¬†or in the comments form below.

First encounter

This post¬†shows how to build and run the Aurelia Contact Manager Tutorial¬†using Monterey as the development tool. The complete process is described with all details in the “Creating new application from Github” chapter of the Monterey user manual¬†– here we will just show the sequence of screenshots, with minimum comments.

image-1
Image 1: ¬†Create new application wizard – define template “type”
image-2
Image 2:  Create new application wizard Рdefine source code location
image-3
Image 3:  Create new application wizard Рdefine location for the new application folder
image-4
Image 4:  New project configuration summary
image-5
Image 5: ¬†Create new application wizard – generated project’s build and run workflow default
image-6
Image 6: ¬†Task manager screenshot showing the ‘au-run –watch’ task running
image-7
Image 7:  Contact manager running (started by a click on Start button on image 6)

Did you like this article? Would you like to see any other “brief story” about Monterey? Give us your feedback here¬†or in the comments form below.