[Grok-dev] Graphs and Plots

Sebastian Ware sebastian at urbantalk.se
Tue Jun 16 12:13:25 EDT 2009


You could use reportlab

   http://www.reportlab.org/

It will generate any chart you need and you can output it as an image  
or PDF.

Mvh Sebastian

16 jun 2009 kl. 16.52 skrev modiadi:

> Hi,
>
> I am doing a stok trader site and I also want to use graphs in the  
> site.
>
> At this point I am using a specialized view with a flash charting
> component inside.
>
> I also need a simple solution for about 6 mini stock charts displayed
> on the entire site.
> For this I made a couple of experiments with flot http://code.google.com/p/flot/
>  (which may be the same as http://solutoire.com/flotr/docs/). My
> problem with this library is that it is drawing the charts directly in
> the browser. It loads from the server the chart data.
> I am interested to replace it with something wich can produce an image
> file. It should be a server side solution without using a remote
> server like Google Chart. Probably in the next couple of weeks I will
> start working on it.
> If you wish we can work on something together and after that share it
> with other grok users (if it will worth something ...)
>
> Please let me know if you want to do that.
>
> Anyway, I can show you what I did with flot, which is basically view
> based.  In this case the caching part is solved by the web server. The
> chart data is a simple file and with a clever configuration it can be
> cached.
>
>
> Regards,
>
> On 16 juin 09, at 15:56, Jeroen Michiel wrote:
>
>>
>> Hi all,
>>
>> For the project I'm working on, I need to draw lots of graphs and
>> plots of
>> statistical data.
>> I was thinking about matplotlib, but I don't find anything about it
>> combined
>> with Zope3/Grok.
>> Is there anything like that available somewhere?
>>
>> If not, I'll have to do it myself, but I'm not sure what would be
>> the best
>> way to tackle this?
>> * Easiest would be to make separate views for each chart that I pass
>> in the
>> HTML img src attribute. However, that might incur extra overload, as
>> I might
>> have to do the same calculations twice or more: once for the main
>> page and
>> once for each graph or plot. I could try to cache the data somehow
>> (session
>> data or memcached), but that might complicate things. You could
>> refer to a
>> single graph by it's url, however, without ever needing the main
>> HTML page.
>>
>> * Another approach would be like the Google Chart API, that the
>> graph data
>> is encoded in the url, and that I have one generic view that can
>> render any
>> chart by changing the url GET params.
>> That, however, would force one to go to the main html page to get
>> the right
>> GET params to go with the graphs.
>>
>> What would you guys suggest?
>> I personally think the view per chart with memcached as a possible
>> later
>> optimization would be best, but I'd like a 'second opinion' on this
>> one.
>>
>> Thanks!
>> -- 
>> View this message in context: http://www.nabble.com/Graphs-and-Plots-tp24054863p24054863.html
>> Sent from the Grok mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> Grok-dev mailing list
>> Grok-dev at zope.org
>> http://mail.zope.org/mailman/listinfo/grok-dev
>>
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev



More information about the Grok-dev mailing list