Dashing - A dashboard framework • Hacker News Board

Re: Dashing - A dashboard framework

#51

Post by jonahx » Wed, Mar 27, 2013, 1:50 PM UTC

pushmatrix wrote: post #30

jonahx wrote: post #25

Is batman.js supposed to be an alternative to angular? If so, what advantages does it have?

Disclaimer: I work on the batman.js team 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 extra…

hey pushmatrix, thanks for replying.

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?

Re: Dashing - A dashboard framework

#52

Post by thibaut_barrere » Wed, Mar 27, 2013, 1:57 PM UTC

masukomi wrote: post #14

k__ wrote: post #10

Earlier quoted context omitted.

dafuq?

I would not be surprised if spinning up on CoffeeScript was easier for beginners without real JavaScript experience.

It was much easier to get started to CoffeeScript for me, and learning it made me much more comfortable with writing JavaScript directly straight after.

Re: Dashing - A dashboard framework

#53

Post by davefp » Wed, Mar 27, 2013, 1:58 PM UTC

fidz wrote: post #44

This is great demo. But i really don't know, do everyone have the same use case? There is so many library that work great in demo, but doesn't suit my use case. I hate to build my own library (if i am able to use existing lib, why creating new?), but i must do this because some library/framework isn't really customizable. The time cost between customizing existing lib and creating new lib is the same, so i prefer to…

I think that you'll find Dashing very flexible. You can fetch whatever data you need, and display it however you like.

At its core, Dashing is just a promise that all your data makes it to all your dashboards.

Re: Dashing - A dashboard framework

#54

Post by davefp » Wed, Mar 27, 2013, 2:02 PM UTC

DoubleCluster wrote: post #36

Exceptionally handsome if you like Windows 8 perhaps. I don't like the big rectangles with bright colors. A good dashboard should be almost invisible until something important happens.

Dashing contributor here: That's great, the default style isn't supposed to be a one-size-fits-all solution, and it's definitely not trying to dictate design decisions.

The real meat of the project is the underlying messaging that passes your data from the server to multiple clients.

You write a job that calls send_data, and Dashing takes care of the rest. There's room for as much customization as you like on the front end.

Re: Dashing - A dashboard framework

#55

Post by louthy » Wed, Mar 27, 2013, 2:21 PM UTC

DoubleCluster wrote: post #36

Exceptionally handsome if you like Windows 8 perhaps. I don't like the big rectangles with bright colors. A good dashboard should be almost invisible until something important happens.

Ironically it doesn't work on IE10 on Win8.

Re: Dashing - A dashboard framework

#56

Post by biznickman » Wed, Mar 27, 2013, 2:54 PM UTC

Where's documentation of how to use the graph widget?

Re: Dashing - A dashboard framework

#57

Post by richoffrails » Wed, Mar 27, 2013, 3:07 PM UTC

I don't get it. Why is something at the UI level coupled to a server-side framework?

Re: Dashing - A dashboard framework

#58

Post by mnicole » Wed, Mar 27, 2013, 3:10 PM UTC

pestaa wrote: post #49

kgosser wrote: post #48

Earlier quoted context omitted.

What terrible trolling. Just change the CSS template! Gah.

Is it trolling, though? Why should I see the potential in this dashboarding utility when there are dozens out there understanding the benefits of good visualizations, using proper colors for different situations?

Because it takes a few minutes of time you're already going to spend implementing it for a someone to change it?

Re: Dashing - A dashboard framework

#59

Post by szalansky » Wed, Mar 27, 2013, 3:16 PM UTC

richoffrails wrote: post #57

I don't get it. Why is something at the UI level coupled to a server-side framework?

Me neither and this is somehow scary. I'd prefer just an UI kit with guidelines for integration with backend.

Re: Dashing - A dashboard framework

#60

Post by pushmatrix » Wed, Mar 27, 2013, 3:46 PM UTC

szalansky wrote: post #59

richoffrails wrote: post #57

I don't get it. Why is something at the UI level coupled to a server-side framework?

Me neither and this is somehow scary. I'd prefer just an UI kit with guidelines for integration with backend.

Because it is meant to be a full stack framework.

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.