Pyxley: Python Powered Dashboards • Hacker News Board

Re: Pyxley: Python Powered Dashboards

#11

Post by huac » Thu, Jul 16, 2015, 9:04 PM UTC

sshillo wrote: post #6

Will work great until you try to render 50,000 points and your browser crashes because it's build on d3.

D3 is pretty ok with large datasets but I understand your point.

What Shiny does to get around this is natively 'evaluate' the plots on the backend, creating a rasterized PNG file. A similar approach could work for Pyxley (using matplotlib or Seaborn to render the plot, and then sending that image file to the front end) but I fear with so much development time spent on d3 support such an approach would not be natively implemented.

Re: Pyxley: Python Powered Dashboards

#12

Post by huac » Thu, Jul 16, 2015, 9:12 PM UTC

How easy is it to integrate a chart or graph into a larger project? My biggest gripe with Shiny is how difficult is to use the R calculate and graphing functions in a larger project without using OpenCPU as an API.

My guess is that with Python being a more general purpose language, this should be easier..

Re: Pyxley: Python Powered Dashboards

#13

Post by ubernostrum » Thu, Jul 16, 2015, 9:17 PM UTC

jfe wrote: post #10

codemac wrote: post #9

Earlier quoted context omitted.

There is a big divide between interpreted and compiled resources though. If you have the original source in an interpreted language, it supports your ARM raspberry pi or chromebook just as well. With the C variation you need to build / package / install. I've kinda just come to accept that code re-use cross language has never been good except with the unix pipe.

haven't linux package managers (e.g. emerge, aptitude, yum, etc.) basically solved the packaging problem?

Not really.

The problem there is updates: you'll get bugfixes, maybe even backported bugfixes, but in order to get a new version with new features you either have to deal with installing/building from a non-OS-package-manager source, or upgrade your entire OS.

Re: Pyxley: Python Powered Dashboards

#14

Post by detaro » Thu, Jul 16, 2015, 9:20 PM UTC

jfe wrote: post #10

codemac wrote: post #9

Earlier quoted context omitted.

There is a big divide between interpreted and compiled resources though. If you have the original source in an interpreted language, it supports your ARM raspberry pi or chromebook just as well. With the C variation you need to build / package / install. I've kinda just come to accept that code re-use cross language has never been good except with the unix pipe.

haven't linux package managers (e.g. emerge, aptitude, yum, etc.) basically solved the packaging problem?

It's quite a bit of work to make sure that a project is available on all potentially relevant distros and always up-to-date, so that only works for popular projects, and even for those there are often alternative package sources to get current versions on older releases etc.

Re: Pyxley: Python Powered Dashboards

#15

Post by aeroevan » Thu, Jul 16, 2015, 9:27 PM UTC

ubernostrum wrote: post #13

jfe wrote: post #10

Earlier quoted context omitted.

haven't linux package managers (e.g. emerge, aptitude, yum, etc.) basically solved the packaging problem?

Not really. The problem there is updates: you'll get bugfixes, maybe even backported bugfixes, but in order to get a new version with new features you either have to deal with installing/building from a non-OS-package-manager source, or upgrade your entire OS.

Or add ppa/OBS/hosted repo that builds the latest version.

Re: Pyxley: Python Powered Dashboards

#16

Post by IndianAstronaut » Thu, Jul 16, 2015, 9:28 PM UTC

mistermaster wrote: post #2

looks cool. shiny is very neat, but has the limitation of having R behind it and debugging ain't fun. I very much look forward to testing pyxley!

Why is having R a limitation? R is a fantastic data language which arguably beats all others in terms of number of libraries and data manipulation tools.

Re: Pyxley: Python Powered Dashboards

#17

Post by nmkridler » Thu, Jul 16, 2015, 9:43 PM UTC

huac wrote: post #12

How easy is it to integrate a chart or graph into a larger project? My biggest gripe with Shiny is how difficult is to use the R calculate and graphing functions in a larger project without using OpenCPU as an API. My guess is that with Python being a more general purpose language, this should be easier..

It shouldn't be too bad. My goal was just to make it a little simpler to do the basic things like formatting the data as json for a particular charting library. The python helpers just set up the APIs. I made an example called custom_react that shows how I mixed some custom code with some pyxley stuff.

Re: Pyxley: Python Powered Dashboards

#18

Post by snowwindwaves » Thu, Jul 16, 2015, 10:02 PM UTC

sshillo wrote: post #6

Will work great until you try to render 50,000 points and your browser crashes because it's build on d3.

Unless you have a screen with 50,000 pixels you would need to downsample the data anyway, wouldn't you normally do that instead of handling a visualization library the full data set?

Re: Pyxley: Python Powered Dashboards

#19

Post by reverius42 » Thu, Jul 16, 2015, 10:11 PM UTC

snowwindwaves wrote: post #18

sshillo wrote: post #6

Will work great until you try to render 50,000 points and your browser crashes because it's build on d3.

Unless you have a screen with 50,000 pixels you would need to downsample the data anyway, wouldn't you normally do that instead of handling a visualization library the full data set?

You actually do have a screen with 50k pixels. Many more than that.

A continuous heat map over two dimensions, at 500x500 pixels, is 250,000 pixels. Of course, to generate the heat map, you have to aggregate (binning on two dimensions), but you don't have to downsample.

Re: Pyxley: Python Powered Dashboards

#20

Post by davewongillies » Thu, Jul 16, 2015, 10:14 PM UTC

njharman wrote: post #8

I've been looking for something to do this (below) in python at least on backend. Big screen on wall with 6 or so boxes. Each box displaying data which updates in real time. Such as - scrolling list of source control commits - graph of busy/idle slaves - single big number, pending builds - graph of open ticket counts - etc I can't tell if this is one of Pyxley's use cases?

I think Tipboard might be more what you're after:

  - https://github.com/allegro/tipboard
  - http://tipboard.readthedocs.org/