Xibo contains a WSDL that explains the interactions between the player and CMS, and should also provide a Schema for the XLF (the layout XML sent to the player).
I totally agree with you that everyone should be able to make their own client - that would be great. However 99% of the user base have no interest in making their own client, all they want to do is download and use a solution that works and is free (cheap).
That is the ethos Xibo was born with and why we have developed the .NET and Pyclient players - unfortunately the Pyclient player didn't work out and the .NET player is built on ageing technology (I started coding it in 2006!).
What we want is a new client that can run cross platform and has an understanding of XMDS and XLF that rivals the current offerings.
I take your points about building signage that runs within a web page - Xibo started out as a .HTA application in 2004, which we of course abandoned due to all the problems you mentioned. However, Chrome Packaged Apps is a long way from a simple webpage and I have yet to see a better proposition for a client that could integrate well with the way Xibo functions (native content augmented with web content).
We have looked at:
- Air
- Python-QT
- C++
- WPF
I am happy to work with you on the XMDS specification (the WSDL is a great starting point) and the XLF schema. We will be looking to enhance both XMDS and the XLF schema to support things like monitor control, interactivity, etc, so we will need a detailed map of the current situation before we start anyway.
No comments:
Post a Comment