smurfy / fahrplan Goto Github PK

After adding the new hafas binary interface for bahn.de the interface works again, but its still a bit buggy.

We need to fix that sometime

• station stops are a bit strange, use the id instead (related to #24)
• if there are to many results (after pressing later or earlier to often) something gets confused and the binary parsing breaks
• there is a general issue with parsing the binary file. and the offset thing. its related to ourparsing, the data itself is fine.
• get realtime parsing working again
• try to combine or reduce to train type instead of the full train code in the main list. if you have a local only trip the list of used traintypes in main results looks quite ugly.
• ....

Add support for booster:

http://kunalmaemo.blogspot.de/2011/10/enabling-booster-support-for-qml.html

We should combine the About text to one file or get the text from resources/text file,
for easier updating.

@leppa
i also want to add you as one of main authors because you contributed the most (you surpassed me in changed lines/commits), if you like of course.

What shall we do, i could host updates on my site or we host them on github.

.deb files for meego should be no problem, but whats with symbian and signing?

Phil

Dear Nokia Developer,

With the growing business opportunities available on the Asha and
Windows Phone platforms, we have been reviewing our developer content
programs to see how we can maximize our support to you, our
developers. As a result of this review, we have decided to focus our
support and investment in new content toward Asha and Windows Phone.
Over the next few months we will be transitioning our active developer
support away from Symbian and MeeGo.

If you have Symbian and MeeGo content in the Nokia Store, it will
continue to be available for download to customers, and you will
continue to receive download and revenue reports as well as payouts
for downloaded content. However, starting January 1, 2014, you will no
longer be able to publish any new content or update existing content
for Symbian and MeeGo.

We are very excited about the opportunities available with Asha and
Windows Phone, and hope that you will bring your talents to these
platforms. We believe that these changes will help improve our ability
to support you as you develop fantastic apps for your customers.

Best regards,

The Nokia Developer Team

if you looked up a later connection, and changed the departure time back then, the time remains as it is. If you want to find a connection departing from "now", you have to manually change the time to the current time. It would be nice if there would be a button "now" somewhere, that sets the time and date to the current conditions.

Add support for more resolutions in symbian, it could be also nessesary to expose the screen dimentions to qml.

Would be nice if one could share connections in plain text format via Whatsapp/Mail/SMS.

http://www.labs.skanetrafiken.se/

http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&eotf=1&u=http%3A%2F%2Fwww.labs.skanetrafiken.se%2F&act=url

Samples:
http://www.labs.skanetrafiken.se/api.asp

After looking at the documentation and the samples, most suff can be implemented.
But i either missed or they missing gps support at least for quering

Search of Stations doesn't return anything. bahn.de works just fine so i think the sbb.ch api may has changed.

If you need to switch trains at a station it would be nice to know the arrival time of the first train that you can estimate the time to reach the next train.

Some backends (mainly öbb and possible bahn.de binary) could cause a application hang.

Possible Reasons:

• Parsing of the response (c++)
• Converting response object to listmodel (qml)

Possible Fixes:

• Move parsing code to thread (c++, maybe in parsermanager)
• Create listmodels in c++ (also parsermanager)

• Update QML for new models
• Figure out whats the deal with ToolbarActions
• Test QTLocation support
• Backends with no Timetable support seams to break the ui (test after qml is adapted to new models)
• Find a way to implement search/favorites switching in station select
  ....

The ubuntu touch sdk did not support location and calendar support in the past but support is in the making.

If the sdk supports it we should add both too.

As of Belle FP1 Qt Components have changed a little. Some elements have changed sizes or parenting resulting in broken UIs in many QML apps.

See these images: https://www.dropbox.com/sh/ea23g2atdrlj4qh/gedkG1O3f8

The issues are present in both landscape and portrait. I'm using the 808 PureView and N8 in comparison. The images provided are from the 808.

In bahn.de the duration (Dauer) between Start and Arrival counts one hour to much. If I test it in öbb.at and sbb.ch the duration between start and end station is calculated properly.
Is this just an error just on my Device (N9)? I doesn't have this error with Version 2.0.9, this error appears since Update to Version 2.0.10.

I would like to open a discussion about managing settings within fahrplan and the different guis.

@leppa @mzanetti

Currently there are methods to read and write settings from qml as string. it basically works, but has limitations.
Like the settings getter method is not notifyable (i read up on this topic and this is currently not possible)

There are some workaround available.

• make a property settings which is an instance of a wrapper which provides a get and set method. we can't a value individually but the whole settings property. this allows us to add setString, setInt... if we want
• make for all possible setting different methods with notifyable properties. which allows invidual notifies but we loose flexibility
• ... something else?

Also some platforms (like harmattan) normale don't use in app settings but settings in a global settings menu. (don't really know how that is implemented.) If more systems use this behavior we should think about moving the settings to the global settings menu if possible.

Both points are open for discussion.

I'm using Fahrplan on the Nokia E6 (Belle Refresh) and am quite sure that it's impossible there to delete an intermediate stop. I tried all ways known to mankind and symbian to get rid of a previously entered stop but have been unsuccessful. I am able to switch stations via the menue but removing the 'Zwischenhalt' seems to be impossible.

(Great program anyway, thanks a lot!)

Currently the Gui is not statless and has lots of logic shared in all different Gui implementations.

Makeing the Gui and Backend code stateless reduces this logic and probably makeing the Gui faster.
Also porting to other Gui frameworks / devices would be easier.

More infos can be found here #52.

But basically this are the bulitpoints:

• Use QAbstractListModel
• Use getter/setter in the gui
• Methods for search etc, should use no parameters and access data set by the setters
• Improve qml performance by using createObject instead of creating them on startup

When searching for a connection, then going into one of them to check the details, then using the back-arrow to go back, it is quite possible (since it just happened to me) to accidentally press the back-arrow twice.
This then requires another lookup, whereas there's no big reason that would be necessary.

The cached results could be shown again, there could be a forward arrow, etc.
This for those on a data budget, or without a data subscription.

Furthermore, it would be good if those connections that are cached could remain available when selecting the same begin and end station/stop, for instance by showing the aforementioned forward arrow. Or just by indicating there are cached results for a specific time window on a specific connection.

Or, allow the user to save the results explicitly, using a button.

Hi,
when I'm trying to search connections containing small railway stations on my Nokia 808 I'm getting this message: "Ein Stationsname ist leider nicht eindeutig". Afterwards there are no results and the circle is endlessly spinning.
When I try to view all connections from the same station I'm getting this error and no result: "Backend hat einen Fehler geworfen: Your input is not valid"

I am using fahrplan for Nokia N9 app.
It seems there is a bug in treating time set. The app sometimes treats the time input as an arrival time though the departure button is highlighted... Would post printscreens as example if this would be possible.
Otherwise great, fast app!
Thanx in advance, xlivio

how to reproduce: look up a Connection (a->b), Show Details, leave application open in Background for half an hour. go back, and look up different Details of the same Connection (by going back once).

result: "verbindungsfehler"

you have to go back to the start Screen, look up the Connection again and then you can view different Details. probably some Kind of a timeout on the DB side. if it occurs, Fahrplan should probably rerun the whole request and not just a part of it.

Edit smurfy:

Bahn.de broken

Query is wrong, either uses a cached station ID or none at all.
To see fault use SBB parser, search for timetable for Zürich and then change to Bern and the results for Zürich are returned again.

When you have received a list of connections tap (multiple times) on "later" until connections for the next day appear.

Result:
Connections for the next day appear on top of the list and not at the bottom.

Tested with version 2.0.11 and the bahn.de backend.

Thanks a lot for this app! I use it on the N9.

I have an issue with a the station called ,,Inningen''. Independent if arrival or departure station, the search never finishes.

I don't know to help tracking the error, but here are some of my observations:

• changing to öbb.at backend fixes the problem (but this workaround does include tram lines)
• it worked prior to the change made to the mobile site (nov/dec 2012) and you had to switch to the binary interface
• this station is also not working with HandyTicket (buy tickets online via mobile webbrowser). Here I'm still waiting for a callback from service...
• and last, but not least: this station is also tricky on http://reiseauskunft.bahn.de itself:
  First there's always the message, that this station is ambiguous. But the point is, all offered alternatives are wrong (those are bus stops, but not the railway station), don't do anything, just click again on the serach button and it works.

If I can assist furthe, please let me know!

For example Ireland:

http://www.journeyplanner.transportforireland.ie/nta/XML_DM_REQUEST?language=en&typeInfo_dm=stopID&coordOutputFormat=WGS84&nameInfo_dm=51010816&itdDateDay=25&itdDateYearMonth=201309&itdTimeHour=19&itdTimeMinute=10&itdTripDateTimeDepArr=dep&deleteAssignedStops_dm=1&useRealtime=1&mode=direct

First I would like to thank you so much for this application. Finally some good working application for public transportation. Thank you so much!

It would be nice if fahrplan would also have a function to calculate house to house connections, so that you just input two addresses and it calculates the best route for it. As part of it, there should then be an option to adjust the walking speed. And if you tap the walk to the station, it should offer the option to show the route / navigate you with Nokia Maps (pedestrian navigation).

Since the new update to version 2.0.11 the favourite stations do not show up. the list is empty. but when i klick on "search" and then back to the "favourites star" they appear again.

First of all, thanks a lot for adding Västtrafik support to this app. Works great.

One issue which I have noticed is that when adding a journey to the calendar (Västtrafik journey - don't know about others) the start and end time of the journey is swapped. This means the event is shown as starting at the time when the journey is actually expected to be over. Can be troublesome if one does not notice this beforehand.

Thanks for your work again!

Hello and Happy New Year!

I'm new here so I hope this is the right place to ask this please.

I really appreciate guys like you continuing to support Symbian in spite of Nokia’s best efforts to trash it.

I've recently downloaded Fahrplan on to my Nokia N8 running Belle Refresh.

The app looks great but sadly won’t work for my home town Sydney, Australia, either if I select 'Sydney' or '131500.com.au' in the drop down list.

(It will work really well for Melbourne in Australia).

Recently the Sydney transport information web site was moved to a new address and format www.transportnsw.info/ so I don’t know if that has anything to do with it.

Will it be possible to access Sydney public transport information in the future please ?

Thanks

Regards

Glen

If I plan a route with bahn.de database, the screen is displayed with the several options for the same route. The departure and arrival time are correct, but the column "dur." shows a time one hour too much!

for example:
Hamburg -> Bad Olderloe, Dec 25 2012, dep 13.05 arr 13.29, dur 1:24, trans 0 (RE21418)

(using 2.0.10 on 808 symbian FP2)

Details to available connections can not be retrieved, DB has probably changed something on their mobile website.
Sadly, Qtdebug does not really work for me, so I have no clue what is causing this.

can also be reproduced with the desktop application. getJourneyDetails returns "No Results"

sbb.ch interface seams broken

Please add late arrivals for DB.de data base like they are displayed at the db.de website

The Station is currently a String, which worked ok in the past but has its flaws.

This should be changed. Most backend support an ID field and GPS coordinates for a Station.

This means Backend and Frontend changes.

Hey, at first i have to say i love this app! Still the best Timetableapp for Germany. But in my actual Version (2.0.12 for N8 Symbian Belle) there´s a bug with the departuretime. If i choose "Actual Departures" at 1 pm. the list of connections starts at 2 pm. In fact the results start 1 hour later than i searched. The same if i search for connections with a later starttime.

Maybe its an error with summer- and wintertime?

Thanks for searching the Bug and sorry for my horrible Englishskills. ;)

Got a error report via mail.

Updated today from 2.0.9 to 2.0.10, discovering that new version does not close.
I click the X to close it, but it restarts after 1-2 seconds...
Even closing it from task manager does not work.

Fahrplan 2.0.11 Release faild QA for Harmatten and probably also fail for Symbian because of new stupid nokia store rules.

It seams i'm not the only one who is pissed off:

http://notyetthere.org/?p=148

I got the same complains.

• Donate button (i replyed to that complaint and waiting for an answer)
• Privacy Police crap (i will write a simple page here at the wiki and link to it)
• Opt out for location (which is crap like the other ones, because the user has to click at the location button in the station search, but i guess i will add some kind of disable feature aswell)

I'm really pissed of about nokia so i probably wait until i get word about the symbian release and the donate button.

Öbb.at has problems with station wörgl

After choosing a "via Station" for one connection, there's no way to remove that station again - it can only be replaced by another.

Hi. Fahrplan on my N9 is not connecting to sbb.ch anymore. Would be grate to get this fixed again. Thanks

http://wiki.maemo.org/QtComponents

With the bahn.de backend change the fremantle version of fahrplan is broken.
We need a working frontend (i prefer qml) for fremantle.

On a BlackBerry Q10 device the fahrplan app is unavailable.

When using Fahrplan left-handed, trying to select a favourite station often inadvertently "de-favourises" that station instead.
An option to move the favourite star to the right side of the screen, or moving the de-favourisation to a context menu, would help (me) a lot.

After these nice patches addressing issues with HAFAS binary backend (thanks a ton!) I installed the latest version (commit dcab4ec) and noticed the following problem on Nokia N9 Harmattan:

1. None of the ,,Switch with {Arrival, Via, Departure} Station'' items in the context menu works; all stations keep their current value.
2. Almost certainly related is the following behavior:
   • Departure Station -> ,,Clear Station'' -> works as expected
   • Via Station -> ,,Clear Station'' -> clears Departure Station
   • Arrival Station -> ,,Clear Station'' -> clears Departure Station

The last version I used was that one from Ovi Store, so I'm really sorry that I can't narrow down that problematic better to a specific commit.

It would be nice to keep a list of previous searches or store favourites

I'm planning to port fahrplan to Sailfish OS too.

https://sailfishos.org/index.html

I'm already support jolla with 100€ and will buy the phone as soon its out.

I've been planning my trip to Berlin today and found a new format of calendar entries rather unreadable.

This is a request for discussion.

Before the a844397 change we've had the following formatting in the calendar:

Section 1 transportation type & number
Date time departure station 1 - Pl. #
Date time arrival station 1 - Pl. #
--
Section 2 transportation type & number
Date time departure station 2 - Pl. #
Date time arrival station 2 - Pl. #
--
...

Might not be ideal, but quite readable.
Now we have the following formatting:

Date time departure station 1/#
--- Section 1 transportation type & number ---
Date time arrival station 1/#
Date time departure station 2/#
--- Section 2 transportation type & number ---
Date time arrival station 2/#
...

While departure - train - arrival order seems more logical, I find it quite hard to find distinguish separate journey sections. Mainly, due to the absence of any separation indicator between them. Adding just a line break between the entries makes text a lot more readable.

Also, those who got used to the old format will, most probably, read Date time arrival station 1/# as departure station of section 1 and Date time departure station 2/# as arrival station of section 1

Regarding the date format (see my comments in a844397). While following regional settings is a good practice, there are also different date presentation formats (i.e., short format, long format, dd.mm.yyyy format, etc.). I would say I like dd.mm.yyyy date format more than Qt::TextDate that was used before. However, other people might prefer long date instead. Best solution here would be to add format selection to Fahrplan settings and use the same format across all application.