On Tue, Feb 5, 2013 at 11:29 AM, David Given <d...@cowlark.com> wrote:
> The code doesn't look too complicated. I presume I'd just need to add an > extra URL parameter for the ticket id and then add another condition to > the SELECT statement. I'll have a look. > For tickets it's (unfortunately) more complicated than that because tickets can have custom fields, custom stati, etc. They are, in essence, completely configurable by the client, making generic code (like an RSS field or (*ahem*) a JSON API) more difficult than it would appear on the surface. A year or so ago i started diving into tkt.c to see how best to add a tickets API to the JSON interface, but was quickly undone by the ticket system's internal flexibility. That's not to say it's impossible, just that it's not simply a matter of copy/tweaking the existing RSS code (though there will of course be much of that going on, too ;). -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
