@vanmeeuwen I'm testing a 30-second timeout for attempting a MongoDB connection, following which Manticore would terminate gracefully. Which is necessary to have anyway in an environment where one runs Manticore directly without systemd.

So, the default behavior is to set 'Untitled Document' as the placeholder in the title widget. Just like the Manticore UI, you'd need to write your own placeholder logic in the Roundcube UI.

Do you mean that this works for you in your development setup, but not in the packaged version?

We also discussed a cleaner way to enable/disable apps, which is via the capabilities, hasMail, etc properties.

I've added a way for "routed" apps to register their "main" routes during app initialization so they show up in the top-level app list for navigation.

Good catch. On it (once I get the session closed event working).

I've added a simple Ember service that wraps Ember.Evented, which basically works - I can fire notification events in the Shell and the (separate) Notifications app picks it up and shows a popup.

We have a plugin 'structure' now, in the sense that you can create a Roundcube app in another repository and 'enable' it within the Shell.

We now have a styleguide! It looks like this:

Since we want embeddable apps, and Mail is going to be one, we should start with the notifications app, which is simple, and will let us establish a pattern for writing these.

One of my early tasks here should be to provide a styleguide. A styleguide is a page that will show you all the available reusable components rendered in one place.

Note that the proxy does provide a JMAP API for calendaring, but it is an interface layered on top of your CalDAV server.

The iframe API is done and the documentation is up at https://github.com/adityab/Manticore/blob/chwala/README-roundcube.md