What Changed in May and June 2011
Sunday 1 May 2011
- Created and used a double arrow for the swap places feature on route entry
- Added a trap and error message for when you have set a waterway speed to zero (it was giving an apparently irrelevant error about internal costs)
→ Release 126.96.36.199
- Started work on a PDF generator for itineraries using wkhtmltopdf - which is really quite fantastic
Monday 2 May 2011
- Further work on PDF rendering. The temptation is to keep playing for ever until it is fantastic, and put photos and all sorts in, but I think I'll get it up to working and release later today if possible.
→ Release 9.14 *ADDS* PDF itineraries
To Saturday 11 June 2011
Two big new features - I bet I've broken tons of things.
- I've completely re-written the linear graphics. They are all now first generated in SVG format (and, in prototype, look absolutely wonderful on Firefox 4) but at the moment they are then converted to PNG for display. But they are crisper, more reliable, easier to upgrade (being generated from database items not hard coded into programs) and don't get confused sometimes with lock-flights and tunnels like the old ones.
- I've ported the "alternative routes" code from the last version, improving it along the way
→ Release 9.15 *ADDS* Alternative routes
Monday 13 June 2011
- Added a back-up of the database for Steve's blogging work
- Fixed graphics for starts of flights that didn't need a symbol (Walsall, Foxton)
- Added graphics for long aqueducts both part of issue 382
Tuesday 14 June 2011
- Create/delete structure never set the tunnel or aqueduct attributes which it needed the next time round! Made the code a lot more robust and fixed a couple of small bugs along the way issue 385
- Fixed, I hope, the bug that blew up the database when the River Tone was created yesterday issue 387
- Fixed a bug where miles of tidal waterway were reported as lakes (hadn't migrated to using "code" rather than index number in that bit of code) issue 388
Thursday 16 June 2011
- Fixed bug(part of issue 382) where the wrong graphics were appearing for some junctions. This turned out to be a bug that had been in the code since junction graphics were added last summer! This also fixed the problem in the 4th comment with the B&T
Friday 17 June 2011
- If you left a route hanging around for days in a browser, when you continued it died rather than carrying on with the session lost. Now fixed.
- Added a better - more user friendly - message about expired sessions
Saturday 18 June 2011
- Reorganised options and similar files in cgi directory
- Fixed bug where fact that a place was a change in lock direction wasn't displayed to be edited
- Completely re-wrote the lock direction graphics. I don't know what I was thinking when I wrote that code, but ...
- With that, all the points in issue 382 are fixed apart from general size in some browsers. That's on the list for later
→ Release 9.15.1 (it's too big a re-write to count as a patch release)
- Fixed missing dual towpaths (bad SVG data)
- This also fixed a bug where locks on canals with dual towpaths didn't display
- Fixed minor CSS error in linear maps - no obvious effect but page now validates
- Added necessary CSS to linear maps on gazetteer page to align names and graphics better (just as itineraries had always done)
- Fixed release number (I'd called the previous 9.12.1 in both this change log and the program, rather than 9.15.1 as it should have been) issue 390
- Fixed a bug where it didn't always know if a place had a tunnel or aqueduct in edit link - turned out to be a bug in the command caching code in the C/SQL interface: added an md5 hash to check
- Fixed a bug where unchecking that a place was an aqueduct failed (tunnels worked fine)
- Added narrows and wides - changing database, attributes, code to edit detail and generate graphics
→ Release 9.15.2
- Added code to globally stamp out ever spreading Bingbot problem (Bingbot seems to respond to a redirect/URL rewrite by adding the original query string to the new URL. So if the rewrite has a query string in it (as it often does), we get a duplicate. I now truncate all query_strings at the first internal '?' [pre-release]
- Removed stray ; from SQL in stats [pre-release]
- Steve managed, at some considerable pain, to get the server running new enough code to update the graphics (we run a "stable" release on the server but more cutting-edge stuff for development, and although SVG isn't particularly new, it's only really starting to take off now).
Sunday 19 June 2011
- Fixed bug where creating new waterways corrupts the database. I don't want to wake up to 2900 error messages. Added a few traps to prevent similar accidental (or deliberate!) damage in the future
- A few changes to the linear graphics generator, hoping to catch issue 391, some junctions graphics are missing.
→ Release 9.15.3
Tuesday 21 June & Wednesday 22 June 2011
- Created utility program to reopen a closed waterway.
- Tweaked code to put names and reasons for excluded waterways onto options screen
- Tested all combinations of new and existing session and open and closed waterways
- Together, this gives me a way to reopen closed waterways - ready for the Droitwich
Thursday 23 June 2011
- Completed work to allow editing of names, detail and size in "edit detail" page issue 361. Renamed this to "edit place"
- Changed code for local distance tables in gazetteer to implement issue 394 - don't break the main waterway at junctions.
Saturday 25 June 2011
- Trap to catch situations where variant route gives the wrong answer
- Rewrote data collapsing code to keep "anchor" points - improved the code at the same time
- Made route generation collect all the weighting element reliably, preventing strange alternatives being offered
- Fixed bug where if you used the browser refresh after choosing an an alternative route it crashed
→ Release 9.15.4
Sunday 26 June 2011
- Fixed bug where junctions along waterways were rarely shown (issue 375).
- Turned on the "avoid repeated places - no/somewhat/yes" - it turned out to work without any effort at all.
- Fixed - pre-release - a couple of bugs in api.can that were causing maps and other things to fail
- For furthest place, added boxes to select percentage flexibility to options screen, and associated code and defaults to support this, thereby delivering issue 51.
- Improved error messages from furthest place - now appear as pop-ups rather than on screen with nowhere to go from.
- Fixed (pre-release) other bug in API that previous one now revealed. These API things were a result of me re-organising the code before starting work on issue 395 and not getting it all quite right
- Added a blank line with just a graphic on it in itineraries after a junction.
- Added a user customisable CSV export format along the lines (actually significantly more sophisticated) discussed in issue 371.
→ Release 9.15.5 *ADDS* User definable CSV export
Monday 27 June 2011
- Worked through a couple of the trapped variant route oddities.
- Improved weighting for locks - collapsing data generated flights for rivers etc which didn't have them, now defaults to same time as that number of single locks
- Reworked the moveable/open bridge code which was messy and unreliable in other ways as well
- Fixed bug in API where polylines came with wrong content type, breaking waterway gazetteer maps
→ Release 188.8.131.52
Thursday 30 June 2011
- Another tweak to the weighting code to work better with strings of locks.
Saturday 2 July 2011
- Fixed a bug in detecting true alternative routes
- Removed duplicate alternative routes that were now being found
- Fixed display bug in text for shorter alternative routes
→ Release 184.108.40.206