John Hampton wrote: > Christian Boos wrote: > >> Eli Carter wrote: >> >>> Something else to think about here: making the query module the default >>> while >>> keeping the report module enabled. If you make 'view tickets' point to the >>> default report explicitly, it's a simple step from there to make it also >>> allow the default to point to the query module. >>> >>> Examples: >>> default_report = report (The default value) >>> default_report = report/4 >>> default_report = query >>> default_report = query?status=new&status=reopened >>> >>> I think that approach would be more flexible, wouldn't introduce the "-1" >>> magic, and wouldn't change urls. (Further, if someone wrote a completely >>> different report module as a plugin, they could set that as the default >>> with "default_report = advancedquery" or the like.) >>> Yes, this could be "abused" with an entry like "default_report = >>> wiki/CommonQueries", but maybe that would be useful too, come to think of >>> it... >>> >>> Thoughts? >>> >> That's interesting, before I jump on implementing that, if anyone >> disagrees, please speak now ... >> > > I actually think that this is a good idea. It gives the flexibility > needed at a very low cost. So +1 from me. >
Just a small follow-up to mention I finally got around fixing this: the problematic changeset that started this all was reverted and a much more general solution has been implemented in http://trac.edgewall.org/changeset/5251, enjoy! -- Christian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
