tigefa4u projects Trac

PermissionPolicy: Merged log:trunk@...

Follow-up to r5397, change the diff_div template in order to keep the unit tests going.

Follow-up to r5399, fix unit tests accordingly.

Follow-up to r5396, more robust way to retrieve the links (fixes an error in a test case)

TracTimeline API: the other timeline event providers were adapted to the updated API

Additional API changes:
- more documentation
- new `href_fragment` property added
- `ITimelineEventProvider.event_formatter` now also takes the `event` itself as argument. This will enable customization of the formatting based on the event kind, for example.

Also, the ticket open events now have the description in their event body, as the summary is anyway present in the title.

There are two new configuration settings for the timeline, here shown with their defaults:
{{{
[timeline]
newticket_formatter = oneliner
abbreviated_messages = true
}}}

- `newticket_formatter` enables one to specify which formatter to use for the description now shown for the new tickets events.
- `abbreviated_messages` is used to decide if by default the 'body' of the events has to be truncated or not when rendered using the 'oneliner' formatter. This will fix #2360.

Ticket #2821: remove old development branch

(setup merge tracking)

TracTimeline API: in 0.10, the changeset events in RSS where including a summary of the commit message.

After the initial refactoring of the Timeline API in 0.11dev, there was only the changeset number left, and this was not acceptable.

So while looking for a somewhat clean solution to the issue, I ended up modifying the !TimelineEvent class a lot. Instead of a fixed "markup" and "wikitext" field, one can associate multiple named markup and wikitext fragments to the event. This is more flexible and allows to build different styles of timelines.

For example, the standard HTML timeline shows for each event its markup 'title', then the markup 'header', followed by the wikitext 'body', followed by the markup 'footer'.
The standard RSS timeline uses the markup 'summary' if present in preference to the 'title', for its <title> element.

For determining the way the wiki formatting of a wikitext is done, the event's provider is queried using the new `event_formatter` interface method.

Finally, the `href` corresponding to the event should in the end be the one of its associated resource descriptor (context for now).

Ticket #2821: Merge to trunk

Ticket #2821: prepare for merge