Maybe it would be possible to write some sort of text in the comments
(before the actual SQL) telling Trac which fields should be showed to
the user so he could fill them in before the query would be executed.
Something like this:
<report definition>
-- ## 1: Active Tickets ## --
--
-- * List all active tickets by priority.
-- * Color each row based on priority.
-- * If a ticket has been accepted, a '*' is appended after the
owner's name
{{{
INITIAL_DATE.label = Start from
INITIAL_DATE.type = DATE
END_DATE.label = Until
END_DATE.type = DATE
}}}
SELECT ...
FROM ticket t ...
WHERE ...
AND t.some_field BETWEEN $START_DATE AND $END_DATE;
</report definition>
When the user select this report, Trac identifies the special section
and asks for the "Start from" and "Until" dates before executing the
query.
On May 29, 10:41 am, Robert C Corsaro <[EMAIL PROTECTED]> wrote:
> Christian Boos wrote:
> > Culapov Andrei wrote:
> >> Hi Richard,
> >> we implemented something exactly like this. Take a look
> >>https://projects.optaros.com/trac/oforge/report/9
>
> > 401 :-)
>
> > Other than that, the code looks interesting and even more so the OForge
> > project.
>
> If you would like to try implementing OForge we would give you a ton of
> support.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" 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/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
