It does. The original version didn't, but I decided to throw it in in the end to see what the fuss was all about. It gave nice resize responsiveness which is cool, but pretext is not a requirement for this effect
Are the obvious reasons that there is so much more activity in GB and RU than other parts in europe others than one can assume (brexit, sanctions)?
I would love to read about changing patterns because of real life events. (Like the rumour that american water plants have problems during superbowl commercials because of toilet flushing but in a larger scale)
Also, it's not really a UI kit. Although it comes with premise widgets and styles, these are just suggestions. The real meat is how the data gets to your widgets, letting you do whatever you want with it. That structure is the core of Dashing.
However, there is a decoupled version in the works with the integration guidelines you mention.
I've used other dashboards before, and I found that they are really limiting. For the most part it's because you can't customize the look that much, or it's because you're limited to a list of predefined widgets.
At Dashing's core, it's just a really simple way to fetch data and send it to the client. What you do with that data, and how you display it is up to you. Hopefully the default layout and widgets act as a good starting point.
Actually it does run on SmartTVs :). All of our displays at Shopify run this way.
The browser on SmartTVs really suck, and also don't support 1080p for some reason. Since the tv SDK is html/js, I built a super simple app that can point to any Dashing instance, and even use the remote control to switch between dashboards! Super handy.
I will be releasing that functionality soon as a plugin for Dashing.
It's an alternative to ember, angular, knockout, backbone, and all those other client side MVC frameworks.
Its main advantage is that it should be very familiar to a Rails developer. The APIs are very close to what you'd find in Rails, so it should be quick to get into it. Shopify, which is built in RoR, now is completely client-side powered by Batman.js. The project was extracted from that.
does batman.js have anything like angular's custom directives? are there any other features/advantages a possible adopter should know about besides the similarity to a Rails API?
EDIT: or perhaps phrased a slightly different way: why did you guys decide to create this instead of just using angular or one of the other existing options? or was this created before those options existed or had reached a mature state?
reply