| Commit message (Collapse) | Author | Files | Lines |
|
I do not really like either option, but at least the second one seems
more likely to be maintained (and a little less clunky to use, too, for
what it's worth).
|
|
|
|
these are just enough to send train positions to tracktrain with the
current API, but are somewhat brittle (e.g. will fail if not restarted
between trips, etc.)
|
|
|
|
(what was that about doing the realtime stuff somewhere else and /not/
in this monolithic server thingie? oh well …)
|
|
(for a leaflet map view or sth which isn't implemented yet)
|
|
|
|
|
|
|
|
works kinda well, but doesn't complain about unknown config values in
json, which is kinda hmpf tbh
|
|
most of it deals with timezones, and all the weird implications that has
|
|
(also some database schema changes, for good measure)
|
|
still basic, but works pretty well overall
|
|
aka use something meant for webapps to write the webapp
|
|
tbh i've kinda lost track at what has all been changed in this, but the
control room form handling now works, and i can write announcements into
the database. Now on to making it do useful things!
|
|
just causes pain and isn't really useful for anything since it's a
webform API meant to be used by the web frontend, not by other
applications.
|
|
|
|
|
|
(tough mostly untested)
|
|
|
|
(kinda barebones, but the important things should be there)
|
|
this adds a package for protobuf stuff, generated via hprotoc. Seems to
work kinda fine?
(the generated API is horrible though, will have to write some wrappers
for that)
|
|
(mostly to make debugging easier, but also more generially useful i guess)
|
|
(and they can be useful, too!)
Also, documentation & deleting imports / extensions that aren't used.
|
|
(at least for a few simple things)
Also, more modules!
|