On Wed, Jan 19, 2011 at 1:58 PM, Chris Cormack wrote:
> On 20 January 2011 05:45, Tomas Cohen Arazi wrote:
>> On Wed, Jan 19, 2011 at 1:39 PM, Chris Nighswonger
>> wrote:
>>>
>>> So what are the pros/cons for server-side/client-side processing of charts?
>>
>> If you used google chart API you wi
On 20 January 2011 05:45, Tomas Cohen Arazi wrote:
> On Wed, Jan 19, 2011 at 1:39 PM, Chris Nighswonger
> wrote:
>>
>> So what are the pros/cons for server-side/client-side processing of charts?
>
> If you used google chart API you will see you can enjoy several
> features like zooming, region se
On Wed, Jan 19, 2011 at 1:39 PM, Chris Nighswonger
wrote:
>
> So what are the pros/cons for server-side/client-side processing of charts?
If you used google chart API you will see you can enjoy several
features like zooming, region selection, etc that are nice. The same
for pie charts where you c
On Wed, Jan 19, 2011 at 10:04 AM, Tomas Cohen Arazi
wrote:
> On Wed, Jan 19, 2011 at 11:34 AM, Colin Campbell
> wrote:
>> On 19/01/11 12:50, Chris Nighswonger wrote:
>>> On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi
>>> wrote:
Folks, I am looking for suggestions on the best long term,
>>>
2011/1/19 Salvador Zaragoza Rubio :
> El 19/01/2011 16:34, Paul Poulain escribió:
>> Le 19/01/2011 16:04, Tomas Cohen Arazi a écrit :
>>> I'ts server-side. I'd prefer sending the client all the data inside a
>>> json and a javacsript library to render everything ono the client
>>> side.
>> shouldn'
El 19/01/2011 16:34, Paul Poulain escribió:
> Le 19/01/2011 16:04, Tomas Cohen Arazi a écrit :
>> I'ts server-side. I'd prefer sending the client all the data inside a
>> json and a javacsript library to render everything ono the client
>> side.
> shouldn't we just wait for html5 support then (isn'
Le 19/01/2011 16:04, Tomas Cohen Arazi a écrit :
> I'ts server-side. I'd prefer sending the client all the data inside a
> json and a javacsript library to render everything ono the client
> side.
shouldn't we just wait for html5 support then (isn't this in html5. Not
sure at all, if someone want t
On Wed, Jan 19, 2011 at 11:34 AM, Colin Campbell
wrote:
> On 19/01/11 12:50, Chris Nighswonger wrote:
>> On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi
>> wrote:
>>> Folks, I am looking for suggestions on the best long term,
>>> architectural solution to add charting for Koha reports.
>>>
>>> Do
On 19/01/11 12:50, Chris Nighswonger wrote:
> On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi
> wrote:
>> Folks, I am looking for suggestions on the best long term,
>> architectural solution to add charting for Koha reports.
>>
>> Do we use:
>> - Google visualization API
>> - Perl module Chart
>>
On Wed, Jan 19, 2011 at 1:15 AM, savitra sirohi
wrote:
> Folks, I am looking for suggestions on the best long term,
> architectural solution to add charting for Koha reports.
>
> Do we use:
> - Google visualization API
> - Perl module Chart
> - Perl module GD
GD is already a Koha dependency, so g
On Wed, Jan 19, 2011 at 3:15 AM, savitra sirohi
wrote:
> Folks, I am looking for suggestions on the best long term,
> architectural solution to add charting for Koha reports.
>
> Do we use:
> - Google visualization API
> - Perl module Chart
> - Perl module GD
> - something else?
We used JQplot fo
savitra sirohi wrote:
> Folks, I am looking for suggestions on the best long term,
> architectural solution to add charting for Koha reports.
>
> Do we use:
> - Google visualization API
> - Perl module Chart
> - Perl module GD
> - something else?
I'd prefer a Perl module to a closed-source cloud
Folks, I am looking for suggestions on the best long term,
architectural solution to add charting for Koha reports.
Do we use:
- Google visualization API
- Perl module Chart
- Perl module GD
- something else?
Also any input on adding Business Intelligence capabilities?
- Perl module Business::Int
13 matches
Mail list logo
