Personal tools
The Open Lighting Project has moved!

We've launched our new site at This wiki will remain and be updated with more technical information.

OLP SOC Ideas Page


Revision as of 09:43, 13 February 2014 by Nightrune (talk | contribs) (Web Based Configuration of Preferences)
Jump to: navigation, search

This page lists some ideas for Google Summer of Code 2014 projects for the Open Lighting Project. You can use these ideas as a basis for your application, or come up with something different. Please see the Google SOC site for the 2014 timeline. If you would like to discuss any of these ideas, or are thinking of applying to work with us, please send an email to the Open Lighting List introducing yourself.

Please also see the GSOC Challenge page. You should complete this before applying.


The current API that the website uses is a bit old and needs updated to allow full use of OLA's inner working in a general RESTful way. This would allow third parties to easily build new web based apps that could connect to RDM and DMX devices.

This project would include:

  • Writing and testing the new API
  • Modifying our current Web app to use the new web api

Skills Required: C++, Javascript, HTML, JSON
Estimated Difficulty: Easy

Port to Android

Android is an obvious target for OLA. Not only does it make perfect sense to use phones & tablets as lighting control interfaces but the Android platform could be used to build embedded lighting control devices. A small amount of this has been done, see OLA on Android. Bug #221 covers this work.

This project would include:

  • Building OLA as a Android Application
  • Adding a Java client or wrapping the C++ client with a Java library.
  • Writing a frontend in Java to demonstrate the capabilities of OLA.

Skills Required: C++, Java, Android
Estimated Difficulty: Hard

Port to Windows

This is the most requested 'feature' and would significantly expand the reach of the project especially as we approach v1.0. The current supported method of running OLA on Windows is using VMWare (instructions). This is sub optimal, since it requires the use of non-free software, is challenging for users without unix command line experience, and doesn't allow Windows applications to communicate with OLA. Work on a Windows port commenced in mid 2011 (see these Notes), but was postponed due to lack of resources.

This project would include:

A Windows port would enable lighting controller applications like QLC and D::Light to move to OLA entirely, and not have to maintain their own plugins.

Skills Required: C++, Windows Network Programming & Windows Event Handling
Estimated Difficulty: Hard

Asynchronous Web Notification of RDM Messages

Thanks to sites like GMail and Facebook, users have come to expect asynchronous notification of events in their web browser. RDM enabled lighting devices can generate events such as Over Temperature and Lamp Faulty so it would be nice to alert the users to this. This project would involve work with two Open Source efforts. The student would need to work with libmicrohttpd to add WebSocket support (see the email thread).

The second step would involve using WebSockets to deliver events to the browser, and building a UI to notify the user. The OLA UI is built with Google Closure.

Skills Required: C++, Network Programming, Javascript, HTML, Google Closure
Estimated Difficulty: Medium

Web Based Configuration of Preferences

User Preferences for OLA are stored in text files but the web UI provides no method for changing any preferences beyond port patchings. At the moment the user is required to stop the OLA Daemon, exit the text files and restart if settings are to be changed. This project would involve building a generic preference store and exposing it through the web UI. Changing preferences on the fly is likely to expose bugs in some of the OLA plugins. These will need to be fixed.

Skills Required: C++, Javascript, HTML
Estimated Difficulty: Easy

Patcher v2

Patcher v2 is one of the next big projects for OLA it requires a rewrite of our current daemon to allow users to patch a specific channel:universe to a different channel:universe. It would most likely not be entirely up to the student but would be a small team effort as this touches all major points of our system. This would also require a change in the web interface to possibly allow drag and drop of patching. Depending on the students knowledge they may help with the web interface, web backend or the OLA daemon.

Skills Required: C++, Javascript, HTML
Estimated Difficulty: Hard