summaryrefslogtreecommitdiff
path: root/templates/_history_trains.html.ep
AgeCommit message (Collapse)AuthorLines
2024-02-01history: fix visual bugs with long station namesCassidy Dingenskirchen-29/+37
2024-01-31history: show destination in first line, origin in secondBirte Kristina Friesel-14/+14
This way, consecutive history entries have matching origin/destination pairs, and both the outer list and the inner origin/destination pair are sorted by descending date.
2024-01-30new history designCassidy Dingenskirchen-56/+52
(cherry picked from commit 8b3ff460b5845c4ec86466715fc054705b635c20) Signed-off-by: Birte Kristina Friesel <derf@finalrewind.org>
2024-01-29unified train farbtupferlCassidy Dingenskirchen-1/+5
(cherry picked from commit 20e8fd39851146eb4fb3cc8cb1f7ba7fc4086d8d) Signed-off-by: Birte Kristina Friesel <derf@finalrewind.org>
2023-08-14hafas preparations: Zug → FahrtBirte Kristina Friesel-1/+1
2020-09-03add public profile page and public journey detailsDaniel Friesel-0/+3
2019-04-26Add manual journey entryDaniel Friesel-1/+1
Closes #3
2019-04-23Use one row per journey instead of split checkin/checkout entriesDaniel Friesel-37/+35
Whether a user is in transit or not is now determined by an entry in the in_transit table instead of a dangling checkin. All completed journeys are stored in the "journeys" table. This does most of the work needed for automatic checkout. However, note that the corresponding worker process is not implemented yet.
2019-04-11decrease minimum history width by hiding train number if line is availableDaniel Friesel-1/+1
2019-04-10history: Show time next to stationDaniel Friesel-15/+22
2019-04-07Refactor history template, add yearly statsDaniel Friesel-0/+51