In its first release, Monterey addresses some of the tooling issues, trying to balance the usefulness with “time to market” (Aurelia Tools team is very small and needs to chose the features set for each subsequent release very carefully in order to create a steady stream of useful innovations). So it should not be a surprise that Monterey’s primary focus is on creating new applications – with special accent on using Aurelia-CLI tool. This decision was not made easy particularly because Aurelia-CLI is very new and because it supports only RequireJS module loader, at the time when most existing Aurelia applications are SystemJS module loader based. However, we are very committed to sharing Aurelia core team’s vision so providing full scaffolding based on Aurelia CLI was a good start.
Aurelia-CLI is not frozen in time (it is really just in Alpha stage) so we can all expect support for other module loaders and many features we do not know about – which is another reason why Monterey application scaffolding feature could be viewed as a visual shell on top of Aurelia-CLI.
In order to help developers with existing applications, Monterey offers graphical views of configuration data (NPM Package Manager, JSPM Package Manager), collection of plugins (aka features) that help with the integration of tools that developers use in their daily workflows and the support for creating new applications from the Aurelia application skeletons. In this context, Monterey reaches wider than supporting just the RequireJS module loader, following the same steps Aurelia introduced so far.
The important fact to remember is that Monterey is in its infancy and that we plan to make it as powerful / useful as our resources allow us and in order that our initial users will suggest to us. This is why it is important that you fill in the survey (at the end of the Introducing Monterey blog article) or share your opinions with us as either comments to this blog article or in this Gitter chat room.
Just a few days ago, Rob Eisenberg, Aurelia team leader and architect introduced Monterey to all Aurelia developers in his blog Introducing Monterey. Here are a few comments provided by users who took their time to answer the Monterey survey question “Any other thought you would like to share with us“, starting with critical and ending with very encouraging..
This GUI tool is absolutely no use to me in some development contexts, such as Unix/screen/SSH on remote servers.
We are really not sure how to address this user’s view 🙂
Skeleton’s seem to be difficult to get working at times. They need to be polished and rock solid.
We would very much like to fix this issue and if would be very helpful to know more about your experience
It’s handy, but I would prefer other features.
Such as …?
I’m a bit afraid that from outside aurelia community, this tool could prevent some people start using aurelia – “wow – do I need an application to manage my application development – aurelia must be really difficult to use”. I think it’s important to state the purpose of this tool.
A very good advice that we are trying to address immediately – see this article.
I would like to run a sequence of commands. E.g. build my project (au run –watch), open chrome, open visual studio for the front-end, open visual studio to my back-end project all with the click of one button.
Thank you for this suggestion which is completely in line with our plans.
Love NPM update module! Keep up the good work.
Configuration of existing applications is high on our list of Monterey features
Could this be a Lightswitch replacement?
Very interesting observation, given that providing Lightswitch-like tool was one of the ideas that made us thinking to create Monterey 🙂
Awesome framework, awesome tooling, its a joy being a developer.
Thank you, your opinion is a great reward for our work.
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:
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.
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.
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)
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.
Today, we are ready to share a brand new approach to Aurelia applications development: instead of creating yet another IDE, Aurelia Tools team’s approach was to “integrate all development tools, including various IDEs, CLI tools, File managers, Developer’s editors, Module loader managers into a single top level “command center” application. We named this application Monterey, hoping that will instill the same bliss as a visit to Monterey’s Fisherman Wharf did so many time to one our our members (Adriatic). At the moment, this name is just a code name and you will be given the chance to chose the real, meaningful name.
We had very little testing done on the Linux platform, so we would like to hear how you experience using Monterey on Linux
Very important: please stay in touch with Aurelia Tools team – as this tool can only be as good as the sum of all ideas we hope to get from the Aurelia Community. So, please respond to this survey below; as Monterey grows, we will be able to offer other, more specific surveys, allowing you to directly influence what will this tool be.
Aurelia-UI-Toolkits team is happy to present the completely re-architected bridge (interface to KendoUI SDK), which addresses a major performance improvement together with more convenient application configuration.
Briefly stated the new bridge supports the concept of user (application developer) installable KendoUI SDK. Instead of supporting just two KendoUI SDK configurations (KendoUI core and KendoUI PRO) this new bridge is completely agnostic to how many KendoUI widgets the application needs to use. This (code-breaking) change allows developers to use the bridge with any module loader – or not to use a module loader at all.
As a result, it is perfectly possible to use just a single Aurelia-KendoUI bridge component in your application, and only that component will be loaded at run time. This will result with the significant reduction in application’s load time.
We have added many more samples, rewritten the installation chapter and added the information about building your applications using SystemJS, Webpack and Aurelia-CLI.
Check the beta version of this new bridge catalog application for details on all these new features.
We are a group of Aurelia Community enthusiasts trying to do our best to help Aurelia framework adoption. While the Aurelia core team is in charge of the Aurelia framework we are working on its “outer ring” where Aurelia meets the rest of the world.
Organized as Aurelia Tools, we are focusing on development tools, first of which- Monterey, is just being announced