Heh,

Sounds like someone needs to put a little veneer on the current google  
charts apis. (there are a bunch of them out there)

gruff-googlecharts gem

:)


On Feb 22, 2009, at 1:01 PM, Paul Leader wrote:

>
> Hi,
>
> Yes I have been looking at using google charts.  However it seems
> rather more work to get them looking decent.  I've tried some of the
> various gems/plugins for it but none of them seem to have the nice,
> clean interface of Gruff, which looks good straight out of the box and
> just seems to do the right thing.
>
> I may take a look at using Flot for interactive javascript graphs.
> Seems like the same amount of work as getting google charts looking
> nice, but with the added benefit of looking very nice and being
> interactive.
>
> Paul
>
>
>
> On Feb 22, 12:03 pm, Ben Lovell <[email protected]> wrote:
>> Although this doesn't answer your question directly I admit... Did  
>> you
>> consider using google graphs:http://code.google.com/apis/chart/
>>
>> I've used these in several large-scale projects.
>>
>> Ben
>>
>> On Sun, Feb 22, 2009 at 6:38 AM, Paul Leader  
>> <[email protected]> wrote:
>>
>>> I'm dynamically generating graphs using gruff as a major part of my
>>> application.
>>
>>> I've played around with caching the images to disk, which gives me a
>>> significant speed boost, but I was wondering if there is a better  
>>> (or
>>> indeed a "right") way to do this which I am missing.
>>
>>> I considered storing the graphs in the db as blogs, but all my db
>>> instincts tell me that is a bad idea.  Is this an old prejudice  
>>> that's
>>> no longer true, or should you still avoid database blobs?
>>
>>> Paul
>>
>>
> >


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to