Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parser for "Transport for London" #268

Closed
wants to merge 97 commits into from
Closed

Parser for "Transport for London" #268

wants to merge 97 commits into from

Conversation

balcy
Copy link

@balcy balcy commented Mar 1, 2018

  • add Transport For London (TFL) parser
  • add color support for route parts, currently only used for TFL on Ubuntu touch, ignored for other backends and devices.

412b and others added 30 commits May 21, 2015 01:09
Due to returning QObject* in calls to C++ objects from QML (e.g.
getItem(i)), those objects were changing ownership to QML and were
subject to gc. That could've been noticed during switching between
journey results and journey details results (instantly switch back and
forth to create enough garbage).
`var item = result.getItem(i);`
`item` would be null after some time. So it was ending up in page
showing loader and not doing anything or in a bit more rare cases with
segfault.
Due to returning QObject* in calls to C++ objects from QML (e.g.
getItem(i)), those objects were changing ownership to QML and were
subject to gc. That could've been noticed during switching between
journey results and journey details results (instantly switch back and
forth to create enough garbage).
`var item = result.getItem(i);`
`item` would be null after some time. So it was ending up in page
showing loader and not doing anything or in a bit more rare cases with
segfault.
@Thaodan
Copy link

Thaodan commented Apr 14, 2019

Can you clean that PR up? It contains my other commits not relating to this.

@balcy
Copy link
Author

balcy commented Apr 14, 2019

would it be OK to rebase it after the following PRs are merged ?
#201
#244

@Thaodan
Copy link

Thaodan commented Apr 14, 2019

I'm not the one to decide that but its easier to merge and this pr looks very dirty.

@balcy
Copy link
Author

balcy commented Apr 15, 2019

Ok let's keep it on hold for now.
[edit: I did not create a feature branch back then, and rebased it it to the ownership and rmv PR. But you cannot add new parsers indepedently anyway]

@balcy
Copy link
Author

balcy commented Apr 15, 2019

Another possibility would be merging #269 instead. That contains the currently released and tested fahrplan version on the Open Store for ubuntu touch. That already does contain this PR.

@balcy balcy closed this Aug 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants