I say again, this is virtually identical to the logic in roundup-summary.<br><br><div><span class="gmail_quote">On 6/5/07, <b class="gmail_sendername">"Martin v. Löwis"</b> <<a href="mailto:martin@v.loewis.de">
martin@v.loewis.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> What I need is a list of<br>> recent tracker activities, a timeline starting at some fixed date
<br>> (like 7 days back from now), including all ticker updates, e.g. status<br>> change, adding file attachments, new comments, etc. To put it another<br>> way, I don't want a mere list of recently changed tickets, but a list
<br>> of changes, with some details about each of them (old and new status,<br>> attached file name, first words of a comment, etc).<br>><br>> I could program my way around this, by taking the list of all tickets
<br>> in CSV format, choosing those which were recently updated and then<br>> asking Roundup for details about each of them (BTW, I don't see CSV<br>> download option for a single issue). This will be ugly and
<br>> complicated, not to say inefficient. One RSS feed with recent updates<br>> generated on the Roundup side will be simply a better fit for my<br>> needs.<br><br>Ok. I think this would be a rather specific RSS feed, as including
<br>the nature of the specific change in the RSS feed is nothing that<br>any of the existing RSS solutions for roundup provide; it would<br>be interesting to see whether the xmlrpc interface recently mentioned<br>provides it (I'd be mildly surprised if it did).
<br><br>I don't think it needs to be RSS, and I would expect that making<br>it RSS makes things actually difficult (how do you encode what<br>specifically changed?). However, generating it on the server<br>side is certainly simpler.
<br><br>I'd encourage you to check out the tracker installation, and<br>propose a solution. There are two ways for report generation<br>in roundup: you can either update it whenever a change is made.<br>This is efficient, but also fixed with respect to the
<br>information available in the report. OTOH, generating the report<br>dynamically allows customization, but is also more<br>compute-expensive.<br><br>Regards,<br>Martin<br>_______________________________________________
<br>Tracker-discuss mailing list<br><a href="mailto:Tracker-discuss@python.org">Tracker-discuss@python.org</a><br><a href="http://mail.python.org/mailman/listinfo/tracker-discuss">http://mail.python.org/mailman/listinfo/tracker-discuss
</a><br></blockquote></div><br>