New Concerto 2 Alpha Release: Frontend, Subscriptions, and More!

We’re excited to announce a new build of the Concerto 2 Alpha Release. Just in time for Christmas, this new build brings a working version of the v2 frontend used to display screen content, a new interface for managing screen subscriptions, a retooled administrator dashboard, and lots of other great additions!

View the 0.0.2.alphamoose tag on Github

Please note: this is an early software preview and a lot will still change from this version. The Concerto 2 Alpha is only for testing purposes and should NOT be used for actual deployments.

The Front End

We’ve put in a lot of work over the past few weeks to flesh out the software that displays Concerto content for all to see. Called the “frontend” in our technical lingo, this is the actual view that will appear on your screens. It’s organized by a template, which provides the screen layout and a background image. This build of the frontend includes some basic effects and can be used to view any screen that has been added by going to [concerto2]/frontend/[screen_id], where [concerto2] is the URL to your instance and [screen_id] is the numerical id for a screen you have added through the Concerto Panel.

Finally, A Proper Interface for Subscriptions

Screen subscriptions are the lifeblood of any Concerto display – they tell the screen which content feeds it should show, and how frequently. In the first build of the Concerto Alpha there wasn’t any nice way to manage these screen subscriptions. But in this build we’ve completely overhauled the entire interface. The interface is even simpler than in v1 – just click the “Add new feed” button to see a list of all feeds currently in your Concerto instance. You can start typing in the search box to filter the list. Click a feed to add it to your running list, where you can adjust screen frequencies with a series of sliders. These frequencies range from showing content in a subscribed feed very rarely to showing them often. When you’ve comfortable with your settings, just click the Save button lit up in blue to commit your changes to the database. When this is done, your screen will automatically pull down your preferences and assemble a fresh batch of content. It’s that simple.

Revamped Admin Dashboard

The Dashboard is your home base as a administrator to manage your Concerto instance and plugins. While we don’t have the entire plugin infrastructure in place yet, this will be where you go to activate and deactivate plugins, change settings, and view the status of admin utilities.

Other Changes…

We’ve increased the pace of development on Concerto 2 and have been making a huge number of tweaks and enhancements all over the application. Of note is a more accurate means of importing templates using XML descriptors. We are also putting bits of code in place to support our forthcoming plugin system, including view hooks that will allow plugin developers to expose settings and other views in the Concerto Panel.

We urgently need your help in testing this new build: please follow our new setup guide and post your feedback on our Google group. We hope you enjoy the new stuff and look forward to releasing another build with the full plugin infrastructure and other essential components within a few weeks. Enjoy the holiday and look forward to 2013 with us!

View the full list of changes between 0.0.1.alpha and 0.0.2.alphamoose here.

Concerto 2 on Github

We’ve decided to use Github Issues to track Concerto 2 development.  We’ll be using the issue tracker and milestone system on our Concerto 2 Issues page to log all defects that are found with the software as we continue to develop, and also to plan out and share strategic objectives of our Concerto 2 roadmap.  We hope that by organizing everything in one place, right next to the Concerto 2 codebase, it will be much easier to keep tabs on our forthcoming release.

To view the Concerto 2 Issues tracker, click here.  You can also peruse the codebase here.

Right now, we’re bringing together a Requirements wiki page to keep track of all of our high-level requirements for v2.  We’ll be gradually turning those requirements into issues within our Github tracker.