I suggest to separate the application from the back ends.
As the backends will have to be updated once in a while (sadly), it is almost impossible to get them stable.
If the application itself does not have to be changed, we could move it to stable.
The application then could have a function to go and look for backend updates and download them.
Also, if the back ends (configuration) is held very basic, other users could easily adjust them to the new service requirements.
This would take a big maintaining load from the author and we could respond quicker.
Just a note to all SBB users. While its interface is brocken currently, you can instead use the german DB one.It interacts with the SBB one and also knows all the swiss trains.
despite of that I request to add another swiss train system interface. the one from ZVV. (fahrplan.zvv.ch). Maybe this one changes less.
Just a note to all SBB users. While its interface is brocken currently, you can instead use the german DB one.It interacts with the SBB one and also knows all the swiss trains.
despite of that I request to add another swiss train system interface. the one from ZVV. (fahrplan.zvv.ch). Maybe this one changes less.
DB knows only the regional trains' schedule, but not the local ones e.g. trams within Zurich city.
DB knows only the regional trains' schedule, but not the local ones e.g. trams within Zurich city.
Affirmative!
I just figured that out myself.
DB seems not to know all trains. Especially it doesn't always know the quickest route
How ever as Smurfy just said, there are 2 SBB backends, and one of them (not the legacy one) works fine.
To me, the SBB thing is the only not correctly working thing. Also there are some possible improvements for the future. Despite of that I see it as a version which should go into stable repo.
We removed the broken SBB backend and fixed the mobile DB one.
Beside of that, also some other changes happened:
* Added busy indications
* Added timeouts
* Journeys can now be added directly to default calendar
* Journey can now be added to a calendar, even the start time is in the past
* Minor UI changes
I'd like to see another backend - for Czech website idos (idos.cz or mobile.idos.cz) that deals with bus, metro, tram and train transportation. I think I could try to make it myself, but I don't know what is the proper way of making Fahrplan backends. So, is there any documentation for that?
(if this isn't the right thread to ask for this, please at least PM me, thank you)
