I had some spare time, so I decided to put together some code to make a PoC integration between our Lightstreamer JavaScript client library and Google's AngularJS.
The integration went smoothly: simply prepare the view using AngularJS syntax, then populate the associated model object with the data flowing in from the Lightstreamer subscription. At each update, ask AngularJS to refresh the view and you're done!
Let me show it to you right here through a simple recipe.
Friday, November 29, 2013
Wednesday, November 27, 2013
Visual Layer of the JavaScript Client Library Is Now Open Source
A few weeks ago, we released part of our Lightstreamer JavaScript Client library as an open source project on GitHub (actually, four projects).
The initial idea was to release our visual layer as an open source addon to our client library. It was 2011 and at that time the latest release of our client library was still version 5. Unfortunately, the visual layer of that lib was quite entangled with the subscription layer, so that such separation was unlikely. We also had in mind to completely revise our client APIs and planned to full embrace the AMD philosophy. So, we decided to wait. Fast-forward to 2012, with client version 6 we finally had a modular library and an independent visual layer, and the separation was finally possible. Other priorities took our time though, so the release had to wait until last summer.
Before we could release the visual layer, we had to release a common layer of utilities we shared across our whole library. The idea of a second project, to host the various utilities, was born... Following closer, came the idea to isolate the logging infrastructure in its own project and to also publish our testing framework. In the end, we had 4 projects to publish.
The initial idea was to release our visual layer as an open source addon to our client library. It was 2011 and at that time the latest release of our client library was still version 5. Unfortunately, the visual layer of that lib was quite entangled with the subscription layer, so that such separation was unlikely. We also had in mind to completely revise our client APIs and planned to full embrace the AMD philosophy. So, we decided to wait. Fast-forward to 2012, with client version 6 we finally had a modular library and an independent visual layer, and the separation was finally possible. Other priorities took our time though, so the release had to wait until last summer.
Before we could release the visual layer, we had to release a common layer of utilities we shared across our whole library. The idea of a second project, to host the various utilities, was born... Following closer, came the idea to isolate the logging infrastructure in its own project and to also publish our testing framework. In the end, we had 4 projects to publish.
Subscribe to:
Posts (Atom)