Earlier quoted context omitted.
I was hoping that this would be a maintained fork of http://dashing.io/
Well, there is the official fork - https://github.com/SmashingDashboard/smashing - Last commit 20th Nov 2016
Cyclotron: A web application for constructing dashboards
101–110 of 120 posts
Re: Cyclotron: A web application for constructing dashboards
#102Earlier quoted context omitted.
You are mistaken. Grafana has RBAC and datasource isolation.
I wasnt entirely clear in my previous comment, grafana allowed clients to issue full queries against all datasources the user has access to. So if you have one datasource with metrics of all your users and want to give them access to dashboards that only display their own data, that is not secure.
Re: Cyclotron: A web application for constructing dashboards
#103Earlier quoted context omitted.
I disagree 100% with you. I love comments like GP. Any new tool should be considered in comparison to the other tools one might use for the same job. Is Grafana "barely related even tangentially"? No it is quite related. Have the creators of Cyclotron considered how it compares to existing tools? Probably, and they should come forward and be open about it.
> Probably, and they should come forward and be open about it. No software developer is obligated to do anything for any of us. It's on US to figure things out and share them as we see fit. Nobody cares if you are willing to invest serious time looking into it or not. Asking a leading question and linking to something most of us have already seen is pointless. Defending it when a good argument was presented is also p…
Further, there are always new people looking to learn and grow. They shouldn't be looked down upon simply because others got there first.
What makes you think the question was a leading question rather than a genuine one? There isn't enough there to definitively determine the intent in any case, so it's up to whoever responds to decide which way of reading the question they will respond to, and that's an opportunity for the larger software community and for the developers of the projects in question to nurture thier communities. Just because it doesn't have value to you doesn't mean it doesn't have value to others.
Re: Cyclotron: A web application for constructing dashboards
#104Earlier quoted context omitted.
Can I just take a moment, and I apologise up front for singling you out for this one, to say how much I hate comments like this, even more that they get upvoted. There's always some arbitrary software mentioned that is often barely related even tangentially and expect someone else to reply with the info. If you want to know how it differs, YOU look it up and if the outcome of that research is interesting enough YOU p…
Well, I for one I'm with weego. The way I read it anyway, he's not against "How it compares" posts, he's against "How does it compare?" ones. Quite frankly, if you want to know it takes five minutes to head over to the respective docs and get a rough idea, as I just did. If you're super-motivated you can even then share your conclusions and tell us "How does it compare: like this, this, and that" (which I won't). But…
And lazy? Since when is asking questions is lazy?
People are reading a lot of intent from what was a very plain and straightforward question. What I think would be valuable would be if someone shared why the mere presence of such questions is somehow detrimental to the point that they can't simply be ignored, which I don't think has yet been explained.
Re: Cyclotron: A web application for constructing dashboards
#105There's also http://atlasboard.bitbucket.org/
Seriously now I wonder how Cyclotron compares.
Re: Cyclotron: A web application for constructing dashboards
#106Re: Cyclotron: A web application for constructing dashboards
#107Re: Cyclotron: A web application for constructing dashboards
#108How does this compare to something like Grafana? https://github.com/grafana/grafana
I like Grafana. I use Grafana. I've got Grafana open in another tab right now. For all that, Grafana ain't all that and a bag of chips. Grafana is very hard to extend with new visualizations. It uses "flot", a JavaScript library that hasn't seen a commit in Github in 2 and a half years. The documentation is poor. There is definitely a need for dashboard software that allows for more complex custom visualizations -- I…
Re: Cyclotron: A web application for constructing dashboards
#109I would like to share some thoughts on this based on experience of being a crusty old enterprise developer. The dashboard problem keeps coming back. I think the time might be finally coming for some dashboard framework to actually succeed. A dashboard framework has been tried many many times. Here are some old ones just on the top of my head: * Shindig aka OpenSocial aka Google Gadgets * J2EE portlets * OpenUSS I'm n…
I think the biggest issue is no one in our organisation has a clear idea what a 'dashboard' is exactly and how people are supposed to use them.
For some people a dashboard is a static page that gets refreshed periodically. I.E. "Lets show the current line speed in big bold 48pt font size and auto-refresh the webpage every 15 seconds."
For other people a dashboard is something interactive (drill down, selectively trend values, modify trend scales on the fly etc).
So there has always been this tension between the two use cases and we always end up with these halfhearted things (usually built using some BI package like COGNOS) which are the worst of both worlds.
At the same time a dashboard has never really been in high demand. So I think people like my manager have really failed to articulate the value a dashboard would supply.
The most promising thing I have seen recently is "Coresight" by OSISOFT (we use their PI plant historian system pretty extensively). They gave a demo that integrated control system type information (Conveyor status's, Flow meter readings, Tank levels etc) with location derived GIS data to show realtime updating maps etc which I thought was pretty cool.
Re: Cyclotron: A web application for constructing dashboards
#110Earlier quoted context omitted.
If you 'incorporate' a piece of GPL code into your program, you're either dynamically or statically linking to it - which the FSF considers to be make your work 'derivative' and thus you would be required to license your own work under the GPL, regardless of whether you had made any changes to the original GPL code you make use of or not.
Of course - that's a feature of the GPL - not a bug.