Source code for Helios is now available for people to look at and start working on extensions, mods and updates. You can find the code on github (https://github.com/Gadroc/helios). I would ask that we try and keep it centralized. Fork the repository and setup a pull request for your changes. I'd rather not see a bunch of distributions. Consider the master tree beta for 1.5 of helios. No new features but a few bug fixes and cleaned out all DRM and consolidated all the modules a little cleaner. There is still a decent amount of cruft.
I am working on a new website and thinking through how I would like to co-ordinate a roadmap for features / design changes. I have about 5 different source trees where I've started rewriting different sections of the code.
A few of the main lines of work that need to be done:
1) Revisit the configuration and plugin management systems. These could be cleaned up and streamlined a bit. Plug-ins should have an initialization routine and central interface to create things, instead of each control and interface being annotated. This is necessary for a few beta things I have around spurning saitek IPS modules.
2) Create a Helios rendering API instead of residing straight on top of WPF.
3) Implement rendering API on top of DirectDraw or Direct3D
4) Implement remote rendering into rendering API (to support remote screens like iOS, Android and Raspberry Pi rendering clients)
5) Create a gauge composer to allow anyone to create the graphics to create new gauges with out coding