Putting timeline events in the DB is probably a first step for this; at the moment they're in a static XML file. Other solutions could include generating the XML file with a template (like we do with statistics/view.js and with text.js) but I think the database is the better option.
Ian McEwen added a comment - 02/Feb/12 04:08 AM Putting timeline events in the DB is probably a first step for this; at the moment they're in a static XML file. Other solutions could include generating the XML file with a template (like we do with statistics/view.js and with text.js) but I think the database is the better option.
Oliver Charles added a comment - 25/Jun/12 10:50 AM This is in beta testing with the origin/split-domains branch (one merge conflict addressed since Ian's branch).
Sub-task
Closed
Normal
Putting timeline events in the DB is probably a first step for this; at the moment they're in a static XML file. Other solutions could include generating the XML file with a template (like we do with statistics/view.js and with text.js) but I think the database is the better option.