Received: by 10.52.64.141 with SMTP id o13mr2314512vds.1.1348866696370;
        Fri, 28 Sep 2012 14:11:36 -0700 (PDT)
X-BeenThere: trac-dev@googlegroups.com
Received: by 10.220.154.5 with SMTP id m5ls3932283vcw.2.gmail; Fri, 28 Sep
 2012 14:11:34 -0700 (PDT)
Received: by 10.58.92.9 with SMTP id ci9mr2729081veb.40.1348866694523;
        Fri, 28 Sep 2012 14:11:34 -0700 (PDT)
Received: by 10.58.92.9 with SMTP id ci9mr2729080veb.40.1348866694514;
        Fri, 28 Sep 2012 14:11:34 -0700 (PDT)
Return-Path: <ole...@gmail.com>
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178])
        by gmr-mx.google.com with ESMTPS id bn19si581973vdb.0.2012.09.28.14.11.34
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 28 Sep 2012 14:11:34 -0700 (PDT)
Received-SPF: pass (google.com: domain of ole...@gmail.com designates 209.85.220.178 as permitted sender) client-ip=209.85.220.178;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of ole...@gmail.com designates 209.85.220.178 as permitted sender) smtp.mail=ole...@gmail.com; dkim=pass header...@gmail.com
Received: by mail-vc0-f178.google.com with SMTP id gb30so4018207vcb.9
        for <trac-dev@googlegroups.com>; Fri, 28 Sep 2012 14:11:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=Et88VG9cLKq55OsHYhTCoJ/rv9sE4H1DspiUZqLIoB0=;
        b=oCI8SBlpKSCfPcz7iNvIEYdbB0phpyWvjt/Mrh+JMHNjht3ivdQqskqtM2vIEZ4Mnv
         i7VDkJW4RCsDlQauRxNkVsI/fi/Zi8d4ghHxsmvOF6a8m3NvTAcB770C51XX+08P7H9k
         hjekFSMwrAkzfSrdTQznt9ZANqQ49gInfgnoLQ6hgM/5BOLrMg8naSqh7QpjyioOlGxB
         xF1r4ZwRqhSoqYVtk8L0UTUtuNNyWzaZAZZgviFvmAor7dtLDtQOdR7IMxD4Ckwo3ho1
         /243R1Vxe10TcKFZ78n1/OAtY6mnwNqtNtYX7cgocSTl4VBRCm5+0HRaVEjgFjjue/EE
         ivbg==
MIME-Version: 1.0
Received: by 10.58.114.194 with SMTP id ji2mr4875215veb.22.1348866694360; Fri,
 28 Sep 2012 14:11:34 -0700 (PDT)
Received: by 10.58.79.177 with HTTP; Fri, 28 Sep 2012 14:11:34 -0700 (PDT)
In-Reply-To: <5065E198.60...@web.de>
References: <CAFFqYiBPE9tgM3sMFQJzuDzcxuS8tZb83fJNPmf9g3vDhwi...@mail.gmail.com>
	<CAGMZAuMTMh2QEv_dyqQuD_WbpBMjxhiufHnCOJ-oo2vDzbu...@mail.gmail.com>
	<5065E198.60...@web.de>
Date: Fri, 28 Sep 2012 16:11:34 -0500
Message-ID: <CAGMZAuOrTRCfDbe25Vzm0toRA2qYggAGGC3pTbAG86CLR1N...@mail.gmail.com>
Subject: Re: [Trac-dev] A plugin idea
From: Olemis Lang <ole...@gmail.com>
To: trac-dev@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1

On 9/28/12, Steffen Hoffmann <hoff...@web.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 27.09.2012 22:33, Olemis Lang wrote:
>> On 9/27/12, Christopher Nelson <chris.nelson.1...@gmail.com> wrote:
>>> > Am I crazy or would it be useful to be able to embed the tabular
>>> > output of a report in a wiki page?
>> You are not ... or maybe we both are
>> :P
>
> No comments to your ability to read in trac-hacks.org hack listings,

yes I have seen those ... but ...

> but
> I see at least two likely candidates to check:
>
> SqlQueryMacro
>
> Execute an SQL Query against a configured database displaying a
> formatted table of results.
>

with all respect ... afaics I'd not use this because it seems to me
that they do not respect Trac permissions and other access control
mechanisms . Saved reports are the way to go because they are under
the umbrella of some permission checks afaicr REPORT_CREATE ,
REPORT_SQL_EDIT . Hence only privileged users decide what will be
repots contents and what not .

> WikiTableMacro
>
> This is a simple macro that enables you to place tables resulting from
> SQL queries into a wiki page.
>
> It is similar to, but simpler than, SqlQueryMacro. The main differences
> are that it has fewer dependencies and always queries the Trac database,
> rather than letting you set up a separate data connection.
>

IDEM ... cmiiw
nonetheless if the OP still wants to use those , no objections afaict

> Bear with us and improve one of these instead of re-inventing the wheel,
> please.
>

jftr ...

<OT>
we didn't reinvent the wheel , we just reuse TracReports code under
the hood and make it ready-to-use in another environment . In the end
, Bloodhound widgets are kind of macros with more meta-data . Hence
they can be reused in many more ways not seen in Trac at the moment
e.g. embedded in Genshi templates using custom markup ...
</OT>

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: