All of the lights …

Posted on Jan 11, 2013 - 17:32

… are not on, because then you wouldn’t be able to admire the dynamic lighting.

Guess who is back … ?

Posted on Jan 10, 2013 - 16:38

the end ;)

Posted on May 24, 2011 - 11:23

Dear all,

after being inactive for quite some time I decided that it is time to let go.

I was approached by the people from wetteronline.de, which kindly provided me the data for RegenRadar, asking me if they could take over the future development of RegenRadar. Since I stopped working on IPhone applications some time ago and I do not have the time to keep the app running, I decided to let them continue the work. I hope they will keep RegenRadar the nice and easy to use tool it was designed to be.

For any further inquiries please contact wetteronline directly.

All the best, m

427 vs 472

Posted on Feb 8, 2011 - 18:51

My recent attempt to fix a problem with Regenradar not displaying the correct location failed 😉 The problem occured due to a size change of the radar images provided by wetteronline. The displayed position is calculated from the longitude and latidue provided by the iphone GPS combined with the known longitude and latitude of two cities (Hamburg und Munich) and their position on the image (in pixels). When the size of the image changed, this pixel position of the cities needed to be udpated. While reading off the new positions from the image I introduced a typo, putting down 427px for Munich where it should have been 472px. So, while when being in Hamburg the position was correct, the further away the worse the position got.

tl;dr – new fixed version is on the way (1.3.6). I will test it today and will send it to Apple for review tomorrow.

[UPDATE] Update has been submitted to Apple, now we have to wait …

[UPDATE] Update is now available in the App Store. Please let me know about your experience (e.g. is the positioning now working as expected)

This time, they got me good

Posted on Apr 1, 2010 - 18:49

April 1, 2010 – Today, changes in the DB website again broke ZugInfo. After a first investigation it seems that this time they got me good. There is not a change in the html output delivered from the site, which could be adopted to quickly. There seems to be a change in the CGI scripts, which prevents to use the API via standard methods from the IPhone. URLs that work perfectly fine from the browser window are no longer accepted when send from the ZugInfo code. I will investigate this further of the weekend, but at the moment I am not positive that there will be a fix any time soon 🙁

I am terribly sorry for the inconvenience, since I really planned to end ZugInfo graceously (see previous post).

Dear ZugInfo user,

Posted on Apr 1, 2010 - 17:18

thank you very much for the enthusiasm and trust you showed for ZugInfo over the past one and a half years. It was a pleasure to work with and for you to create a product to satisfy our common need for an easy to use, fast and (mostly) reliable  timetable application.

The increasingly frequent changes in the layout of the website of the Deutsche Bahn and the resulting failure of ZugInfo have shown me that, for the moment, I  won’t be able to deliver on one of my goals for the App, reliability, which in my view is needed for such tool. The dependence on parsing the (ever changing) webpage also severely limits the development possibilities for the App: every new feature will add to the potential for failure.

I have, therefore, decided to cease the development of ZugInfo for the moment. This does not mean the end of ZugInfo on the App store. For some time I will provide updates for the App to adopt it to changes of the DB website layout, but I will not add new features. This also means that, following the coming update, I will remove the donation version from the App Store. Update: Unfortunately, todays (1.4.) changes of the website code are non-trivial to fix and I decided to remove ZugInfo and ZugInfo donation from the App store. Please read the next post for details. Thank you to all you donators, it really motivated me to keep going!

I hope the DB will deliver on their promise they made with DB Navigator.

I wish you all the best and always travel safe,

Yours M.

every 3 months …

Posted on Mar 6, 2010 - 22:17

.. there seems to be changes in the bahn website. At the moment the details view of ZugInfo is broken and I am looking into it. I keep you posted.

[Update] There we go, problem fixed (though I don’t quite understand why someone wanted to remove http from a hyperlink address). I will wait a little longer before submitting the fix, since you never know .. maybe there is more to come.

[Update] More changes, more updates. This time adressing an issue when quering a non-unique location resulting in an error. Technical detail: again a web address on the bahn website lost it’s http pre-fix. Will submit the fix later today (3/10/10). Sorry for the inconvenience.

one fixed, two new

Posted on Dec 31, 2009 - 13:06

The old programming rule still holds: you fix one bug and create two new ones. I (not so much proudly) present: ZugInfo 2.1.4 – fixing:

  • A bug introduced in ZugInfo 2.1.3, which wrongly grouped S-Bahn under the RE/RB button
  • Improved nearby services
  • Fixing a typo in the German disclaimer text

To avoid another quick fix, this time I will apply more rigorous test scenarios, so it might take a few more days before I will submit this version. Sorry for the inconvenience and a happy new year to all of you!

[Update:] Just submitted the new version. Let’s hope for the best, and that I have not introduce more bugs 😉

while i am at it …

Posted on Dec 19, 2009 - 11:34

Sometime next week I will release another bug fix version of ZugInfo, which addresses a few of the long standing minor annoyances and should re-enable nearby stations (though atm only real train station seem to work anymore, sorry you public transport people). Here is the full list of fixes for ZugInfo 2.1.3:

  • Adresses an issues, which cause ZugInfo to incorrectly display all connection when queried from the favorite tab, while only local connections had been selected in the Favorite (only happened after first startup).
  • Fixed an issue with train type selection (now all ME connections from Goettingen to Hamburg should be displayed correctly)
  • Re-enabled nearby station (though atm only DB train station seem to work)
  • [Update:] Re-enabled via location
  • [Update:] Improved fare display

On a completely different note: I had quite a nice chat with the people from DB. Maybe I can convince them to include a save connection feature into DB Navigator (and ticket purchase, which would be the killer feature for me).

[Update:] The update has been submitted to Apple (Dec 23). Happy holidays to all of you!

and .. again

Posted on Dec 13, 2009 - 17:05

yep, increasing the prices goes hand in hand with changing the mobile website. Today the DB decided to again change their webinterface (which is browsed by ZugInfo). This means for the moment ZugInfo is broken and we are working on a fix. Sorry for the inconvenience.

[Update:] Alrighty then! Bugfix version finished, just needs some polishing (i.e. testing). Hope to submit it tomorrow. If I find the time over Christmas, I will try to implement a more sustainable solution for the website change problem.

[Updated:] Just submitted the bugfix to Apple (ZugInfo 2.1.2, Dec 13, 10pm). Keep you posted.

[Update:] Thanks to the swift work of the guys and girls of the Apple App review team ZugInfo 2.1.2 is now available in the App Store (Dec 18).