The information contained on this page is now archived. Please see our website and documentation for current information
2.0.0-alpha Development Preview Released
We are proud to announce the release of our first development preview for the 2.0 version of Xibo. The codename for this version is “Swift”.
Originally discovered on November 27, 1869 by Tempel (the codename for our 1.8 release), the 11P/Tempel–Swift–LINEAR comet was rediscovered by Swift on October 11, 1880, lost and rediscovered again by LINEAR on December 7, 2001.
2.0.0-alpha is a development preview only and should not be used in production. You can upgrade to this release from 1.8 series.
We have had 4 focus points for this version:
- Improved Layout Design experience
- Draft/Published Layouts
- Database Schema migrations for Upgrades
This alpha is a CMS only release - Player releases will follow in due course and you can use a 1.8 Player against a 2.0.0-alpha CMS.
We've redesigned our Layout Designer from the ground up, with the new design being based on feedback from thousands of users with years of experience. The 'key brief' to bring about a simplified process for designing a Layout and to make that experience flow without interruption.
There is a new Toolbox, located at the bottom of the screen for adding Widgets and Library Media which includes tabs for searching in the Library. We've also given the toolbar a memory so that when you next open Xibo, you can pick up right where you left off.
We've enhanced how you position and size Regions on a Layout by using a Layout Navigator, located in the top left and made the Region timeline always visible. We've also included smarts to estimate when items will be shown in time with each other.
Xibo has always had Playlists, but they've been single-use and hidden away inside Regions, making them inflexible.
We've extracted this concept out into its own Playlists Page accessible from the Library. You can now name and reuse these Playlists across multiple Layouts and Regions. Each Playlist you create has a timeline which can hold all Xibo's Widgets, even Sub-Playlists, which are assigned using the Toolbox. With the use of search criteria, Playlists can also be pre-populated on creation or dynamically kept up to date.
To assign a Playlist to a Layout you simply use the Sub-Playlist Widget. This Widget allows one or more Playlists to be selected and, if more than one is selected, you can decide how the Widgets on that Playlist are combined in the Region.
We've all been there - you have a Layout playing across your inventory and notice a typo, wrong logo being used, or that the date isn't quite correct. Currently, you need to go into Xibo to change it, make an adjustment and all Displays immediately download and play the Layout while you are still making changes...
We've solved that problem with Draft/Published on Layouts!
Before you can make any change to a Layout in 2.0 you need to Checkout to change the Layout to a Draft Layout. Changes made to a Draft Layout are never sent automatically to Displays, so you can take your time with edits. When you're done you can either Publish to make those changes permanent, at which point the Layout will be sent, or Discard to go back to the original Published version.
We have adopted a tool called Phinx to help us manage database schema changes between versions. 1.8 and earlier had a tool developed in-house, which grew complex over time. Phinx gives us a strong framework to author and test migrations so that we can improve our database updates moving forward.
We're making this alpha available for people to try using our recommended installation method, Docker. We will be providing release files for the stable 2.0.0 release for those of you running without Docker in due course.
Our immediate development work will be to prepare a 2.0.0-beta release which will add more polish to all the features we've put in 2.0 so far. We will also be responding to your feedback and any bug reports.
Beyond 2.0 we've begun working on 2.1, which will focus on improvements to Proof of Play statistics.
We're improving our release cycle - you can read about that here.
Read more from the blog
Read more from the blog