Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3085D9E07 for ; Mon, 20 Feb 2012 23:03:17 +0000 (UTC) Received: (qmail 23107 invoked by uid 500); 20 Feb 2012 23:03:17 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 23089 invoked by uid 500); 20 Feb 2012 23:03:17 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 23081 invoked by uid 99); 20 Feb 2012 23:03:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 23:03:17 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of robert.w.rose@gmail.com designates 209.85.160.47 as permitted sender) Received: from [209.85.160.47] (HELO mail-pw0-f47.google.com) (209.85.160.47) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Feb 2012 23:03:10 +0000 Received: by pbcum15 with SMTP id um15so1104695pbc.6 for ; Mon, 20 Feb 2012 15:02:50 -0800 (PST) Received-SPF: pass (google.com: domain of robert.w.rose@gmail.com designates 10.68.219.10 as permitted sender) client-ip=10.68.219.10; Authentication-Results: mr.google.com; spf=pass (google.com: domain of robert.w.rose@gmail.com designates 10.68.219.10 as permitted sender) smtp.mail=robert.w.rose@gmail.com; dkim=pass header.i=robert.w.rose@gmail.com Received: from mr.google.com ([10.68.219.10]) by 10.68.219.10 with SMTP id pk10mr49355712pbc.87.1329778970472 (num_hops = 1); Mon, 20 Feb 2012 15:02:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mkux6k3kYzHERVv1Enn6GYZQtwwZDFSN68doOnBluB8=; b=VrEYs5Zn6n74UWdeasoiIFWGPe5sQCOH3gSaCv/3FeFfN9BRiMC0DzxasvUuxA0YXb cZaZ4TyWmFkbC0NjLgkze+kfQgELauwfbg0HzmXOCOpNQyMo3+gI/KNBDLitWuFCUOUi zqKmB4j+P4YXyK1YL1wEWUpwqnhJVn85n9lak= MIME-Version: 1.0 Received: by 10.68.219.10 with SMTP id pk10mr40719749pbc.87.1329778970438; Mon, 20 Feb 2012 15:02:50 -0800 (PST) Received: by 10.68.222.33 with HTTP; Mon, 20 Feb 2012 15:02:50 -0800 (PST) In-Reply-To: References: Date: Mon, 20 Feb 2012 15:02:50 -0800 Message-ID: Subject: Re: Bloodhound thoughts From: Robert Rose To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Mon, Feb 20, 2012 at 1:41 PM, Olemis Lang wrote: >>>+1 for looking further into GoogleChartAPI, although doesn't it >>>require data to 'leave the premises' for Google to return the chart? >>>Some companies may not be comfortable with this, whether on reasonable >>>grounds or not. >> >> That's a profound truth. I'd like to have a more contained (??) >> implementation of that. >> > > That's a big subject ... Google Chart and Google Visualization API , > they both have these particular terms of usage . > BTW , I'm making (on my own) some (kind of yet experimental) > development for TracGViz and the goal is to render data in local > server . This will make it suitable to be used in e.g. intranets . > Nonetheless for more serious efforts in this direction and > distribution as part of ASF code IMO , there's much more to figure out > yet. We also use the flot API internally http://code.google.com/p/flot/ with great success. This is a free[-er] charting package, renders completely client-side and doesn't require access to google's servers.