Soletta Project v1

 dev  Comments Off on Soletta Project v1
Jul 222016
 

Soletta (TM) Project finally had its V1 release announced this week.

I’ve been working in this project for almost an year now and I’m very excited with all we got so far.

Soletta Project is a framework for making IoT devices. From day zero it was designed to be used by developers without an embedded systems background. So web developers and smartphone app developers would be able to get IoT products out there more easily. In order to accomplish this goal, we packed all the low level stuff in components that could be just re-used, be it via C API or as nodes in a flow based programming layer. And it works fine on top of the most relevant OSes used for IoT: Linux, Zephyr (TM) Project, RIOT OS, and Contiki.

Between the major features for this first stable release I could highlight:

  • Communication protocols (HTTP, OIC, MQTT, LWMWM and CoAP)
  • Input / Output (GPIO, AIO, I2C, SPI, UART, PWM and IIO)
  • Services and system update
  • Flow based programming layer

Full release note can be seen here.

There are also two side projects that totally worth to be checked too. A machine learning component, focused on client side AI and a web-based IDE for flow based programming. They’re both on experimental stage but seem promising.

Dec 142012
 

Michael Blumenkrantz, the very acclaimed e17 release manager, and I have been working on Etrophy, and it’s ready for a 0.5 release.

Etrophy is a library that manages scores, trophies and unlockables. It will store them and provide views to display them. It could be used by games based on EFL and any other application where such a thing could make sense.

It’s already in use by Escape From Booty Bay, Econcentration and Echo. And who knows what else is coming ?

Etrophy can be checked out from E Project’s svn repository:

$ svn co http://svn.enlightenment.org/svn/e/trunk/PROTO/etrophy

or downloaded in release tarball form.

Online documentation isn’t in E server yet, but can be accessed here.

There are still a lot of tasks to be concluded before the 1.0 release, including adding a remote backend, adding more views, creating some examples and improving  docs. Since we are developing it mostly in our free time, between many other projects, anyone willing to help to speed up things a bit will be very, very welcome.