Moblin + digital signage: features, roadmap and hardware

Brainstorming of features, roadmap and interesting hardware for building a digital signage player based on Moblin and Clutter.

Translation of the original in Catalan. Read it in: CatalàCastellano

Part 3 of 5Moblin notes
  1. moblin: Why do I use Fedora Core 10?
  2. Moblin: system installation and configuration
  3. Moblin + digital signage: features, roadmap and hardware
  4. Moblin: desktop customisation
  5. Developing with Moblin

This page was on the oriolrius.cat wiki (2009–2012). I recover it here as it was.

Feature brainstorming

  • Always boots
  • Secure remote access:
    • periodic connections to a server (reserverse access)
    • dial-up schedules
    • connections to vpns
    • unencrypted vpns
    • bot
    • callback via 3G and RTB
    • email (auto-collect the email from a website and if it has a specific xml the system saves your arse)
  • Alarms:
    • SMS
    • email
    • bot
  • Simplify networking configuration (dbus), conman
  • python and c/c++ languages
  • gtk, glib, clutter, qt, etc. libraries
  • Monitoring:
    • bot
    • nagios
    • zabbix
  • Watchdog (monit)
  • External devices
    • touch, multi-touch and gestures
    • coin selector
    • change giver
    • GPIO
    • temp
    • wiimote
    • remote control
    • etc
  • Operating system support
    • HD
    • PenDrive
    • DOM
  • Power
    • UPS monitoring
    • auto-wakeup
      • timer
      • SMS
      • callback
  • Boot modes
    • Normal
    • Rescue Mode
    • Re-install mode (PXE, USB, etc)
    • Assisted (remote-control)
  • Remote control
    • synaptics (client and server)
    • vinagre
    • ssh
    • reverse vinagre
    • vinagre via XMPP
  • Graphics
    • nVidia
    • intel
  • Comply with the SMIL for DS standard

Roadmap: moblin+ds

Version 0.1 (February 2010)

  • moblin:
    • gst-plugins (many image, audio and video formats supported)
    • VINO (VNC server)
    • monit
    • screenshots (via xwd)
    • suspend/resume/standby display
    • player management integrated with moblin
      • network configuration
      • media monitoring
      • access to the player management web
      • simple access to logs
  • player: 1 week
    • playlist based on clutterscripts (very easy to convert mcp xml to clutterscripts, also easy to make compatible with SMIL DS)
    • supported actors: video, images and basic tickers
    • DBUS command interface
    • integrated with the moblin environment 1 week

Version 0.2 (April 2010)

  • moblin:
    • moblin support on a read-only system on cow fs (robustness against abrupt power-offs)
    • passive access to VINO, without needing to forward router ports
  • player: 7 weeks
    • plug-in support 1 week
      • basic plug-ins to work with complex scenarios 2 weeks
    • actors: web and flash 4 weeks

Version 0.3 (June 2010)

  • moblin:
    • different boot modes
      • local support mode, for repairs by a technician on site
      • remote support mode, for repairs by a technician remotely
      • automatic reinstallation of the player over the network
  • player: 11 weeks
    • plug-ins: development of more plug-ins to give power to the player the widgets
    • capture of user signals or other sensors 2 weeks
    • interactivity support 2 weeks
    • widgets: clutterscripts + plug-ins 2 weeks (duplicate of v0.2?)
      • widget: clock and calendar 2 weeks
      • widget: the weather 1 weeks
      • widget: twitter 1 weeks
      • widget: facebook 1 weeks

Version 0.3 -> 1.0 (July-August 2010)

  • player: 2 weeks

Continuous integration

More detail in Player in Clutter: continuous integration.

  1. Build a basic performance testsuite for the application. 1 week
  2. Validate whether the information we can get from the testsuite seems interesting enough to carry out the implementation of a continuous integration system
  3. Implement/test buildbot 2 weeks
  4. Connect the results of the basic testsuite with buildbot 1 week
  5. Create a jhbuild module for the player 1 week
  6. Implement the continuous integration system on a machine equivalent to the production one 1 week
  7. Create several environments with different versions of clutter/pyclutter (stable, unstable, etc.) to be able to evaluate whether a change in performance is due to clutter or to the player 2 weeks?
  8. Complete the testsuite for the player 3 weeks
  9. Implement 1 week

TOTAL: 11 weeks

Others

  1. Software release 1 week
  2. Creating mailing lists? 1 week
  3. Code management 1 week?

TOTAL: 3 weeks

TOTAL

TOTAL PROJECT: 1 + 7 + 3 + 11 + 2 + 11 + 3 = 38 weeks -> 9 months

Hardware

PCs

Motherboards

I think they would work...

The following list of boards is very interesting but I can't guarantee they would work without trying them first.