I am doing some enhancements to the ticket-links branch (http:// trac.edgewall.org/browser/ticket-links) on behalf of Logica. Namely to add the features:
- 'Blocking/blocked by' link type - Display of linked issues on the ticket page as shown in the RedMine screenshot http://trac.edgewall.org/ticket/31#comment:147 - 'Create linked ticket' user interface - Links to tickets in remote Trac installations, fetching remote status over the XML-RPC interface (with some kind of caching.) I have a couple of questions regarding the current branch: 1. In http://trac.edgewall.org/browser/ticket-links/trac/ticket/api.py ITicketLinkController is defined with get_links(), but the implementation calls get_ends() instead. Is one or the other named wrongly? 2. The Ticket object currently only exposes that ticket's links in a string (e.g. Ticket(env, 1).values['dependants'] == '#2, #3'), which is not ideal when rendering the linked tickets in a different form (e.g an ordered list or table). Rather than split this string repeatedly with ticket_system.parse_links() I would like to hold the links read from the database as an attribute of the ticket e.g. Ticket(env, 1).ends['dependants'] == [2, 3] or Ticket(env, 1).links['dependants'] == [2, 3]). Is this a bad idea? Thank you for your time, if anyone has questions for me I'll do my best to answer them. Regards, Alex -- Alex Willmer <a...@moreati.org.uk> http://moreati.org.uk/blog http://twitter.com/moreati -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-...@googlegroups.com. To unsubscribe from this group, send email to trac-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
