#5240 new enhancement

Expose Trac timeline data as JSON(P)

Reported by:	oyasumi+trac.edgewall.org@…	Owned by:
Priority:	normal	Milestone:	unscheduled
Component:	timeline	Version:
Severity:	normal	Keywords:
Cc:	Thijs Triemstra, leho@…	Branch:
Release Notes:
API Changes:
Internal Changes:

Description

I would want the option of exporting Timelines not only in HTML format, but in raw JSON (and JSONP, with a javascript padding callback) data format, too. The same goes for the Search view (but that's another ticket, really).

Given that, people can make their own uncoupled interfaces for the data set, such as this cool view, built solely from this JSON data set.

Change History (12)

comment:1 by sid, 17 years ago

Seems like something that should go into a plugin..

comment:2 by Christian Boos, 17 years ago

See also #3332 - convert the timeline data to some other arbitrary format.

comment:3 by Remy Blank, 16 years ago

Milestone:	→ 1.0
Priority:	high → normal

This could be implemented in a plugin, but the timeline currently lacks an adequate interface. It should probably grow an IContentConverter implementation.

comment:4 by Christian Boos, 15 years ago

Milestone:	1.0 → unscheduled

Milestone 1.0 deleted

comment:5 by Thijs Triemstra <lists@…>, 14 years ago

Cc:	lists@… added
Owner:	changed from Christian Boos to osimons
Summary:	Expose Trac timeline data as JSONP → Expose Trac timeline data as JSON(P)

osimons, this is now part of the xml-rpc plugin right?

comment:6 by osimons, 14 years ago

Almost… JSON is now supported by th:XmlRpcPlugin. And, it does provide an interface to Search. However, Timeline support is not yet added - see th:ticket:5527

I'll get around to completing this at some stage. Promise…

follow-up: 8 comment:7 by Thijs Triemstra, 14 years ago

So it's a plugin issue?

in reply to: 7 ; follow-up: 9 comment:8 by osimons, 14 years ago

Replying to thijstriemstra:

So it's a plugin issue?

No, not only a plugin issue. The Timeline API pre-supposes HTML-based output, which makes reuse in other formats more difficult than it needs to. Content can arrive in any form as plugins are free to at will. And output may differ depending on project and user/session settings.

This complexity is the main reason why the RPC plugin does not support Timeline. There are other discussions of this elsewhere… :-)

in reply to: 8 comment:9 by Christian Boos, 14 years ago

Replying to osimons:

Replying to thijstriemstra:

So it's a plugin issue?

… elsewhere…

i.e. #6492, in particular Simon's comment:31 and my reply in comment:34.

comment:10 by lkraav <leho@…>, 12 years ago

Cc:	leho@… added

comment:11 by Thijs Triemstra, 12 years ago

Cc:	Thijs Triemstra added; lists@… removed

comment:12 by Ryan J Ollos, 9 years ago

Owner:	osimons removed

Modify Ticket

Change Properties

Summary:
Description:	I would want the option of exporting Timelines not only in HTML format, but in raw JSON (and JSONP, with a javascript padding callback) data format, too. The same goes for the Search view (but that's another ticket, really). Given that, people can make their own uncoupled interfaces for the data set, such as [http://exhibit.ecmanaut.googlepages.com/cvsview.html?f=2007-01-21&t=2007-01-31 this cool view], built solely from [http://pike.ida.liu.se/_/cvsview/commits?f=2007-01-21&t=2007-01-31&callback=Exhibit.JSONPImporter._callbacks.cb1 this JSON data set]. You may use WikiFormatting here.
Type:		Priority:
Milestone:		Component:
Version:		Severity:
Keywords:		Cc:	Set your email in Preferences
Branch:
Release Notes:
API Changes:
Internal Changes:

Action

leave as new The ticket will remain with no owner.

unassign The ticket will be disowned.

resolve as The resolution will be set. Next status will be 'closed'.

assign The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Your email or username:

E-mail address and name can be saved in the Preferences .

You may use WikiFormatting here.

Download in other formats:

Context Navigation