What changed in June 2009
Tuesday 9 June 2009
- Added missing error message when you don't set coordinates for a place (thanks Steve)
- Fixed a bug there where Google Maps weren't being unloaded (typo in mode name)
Saturday 13 June 2009
- Added a "setup" command to the language to allow changes when executing. Used to prevent the tarpit from timing out!
- Separated out the concept of characters used in IDs from that of characters used in base conversions. This has saved about 2Meg of working memory (not much by modern standards, but I grew up with systems where 16k was a luxury!)
- Added a new "find a new ID" function. This tries to fill in gaps in the ID space
- Prevented deformed queries breaking the waterways gazetteer (actually a bug in that the place, rather than waterway, name space was being searched - so fixing it should help waterway matches as well) - well spotted Steve
- Made unknown ID's to the waterways gazetteer produce a placefinder screen, rather than a wonderful page about the mysterious NOT FOUND waterway. This next level fails if you carry on from there, but that will get picked up when the placefinder is made able to cope with waterways.
- Fixed a rare Segfault in FOR LINK
- Fixed a bug in Delete Place introduced when queued actions added
- Made recalculation of deeleygrams into a queued action
→ Release 9.3.9
- Extended API functionality to take starting place from blogs
- Added a UTF-8 content-type to all output, which means that you can use accented characters in place names (essential if I want to start adding France). Tested by manually adding a silly text to the database as a place detail string, and it copied all the way to the browser successfully.
Sunday 14 June 2009
- Restored interactive editing of place name, detail and size
- Removed debugging database name from message sent when a database change was made
- Removed pointless wiki editing help tab from simple text editing fields
- Fixed a bug where if you cancelled editing of a place name etc it altered the layout slightly and went bonkers if you moused over it again.
- Tested UTF-8 characters. Can type them into edit boxes, get them saved and regenerated. Big step towards adding non-British placenames
- Added a function to encode coordinates into a Google Maps polyline
- Improved the HTML in the empty gazetteer page
- Added a polylines table to the master database
- Fixed a bug introduced in release 8.3.8 that had killed photograph display in gazetteers
- Fixed two instances of zero distances - meaning that the Gower Branch and the Thames were both impassible (and, typically, it was the first of these that someone spotted!). Fixed the code bug that caused this to happen, which should make all the distance calculations better. This fixes issue 14.
- Fixed a bug where you couldn't follow wiki links if logged on or had planned a route in this session
→ Release 9.3.10
Monday 15 June 2009
- Upped the timeout on database locking to see if I could avoid the occasional "database locked" errors that were happening
- Fixed a bug issue 15 where the "Id to Id" link code was going the wrong way if there was a single link that bypassed it (such as the IRPW loop). Changed the distances on the loop slightly to agree with Bradshaw.
- Added a trap for a bug in photo adding that had occurred.
→ Release 22.214.171.124
- Reorganised the code in the options (session) handler to try to reduce the time spent with the database open, and so the database locked errors that are occurring. Moved the "purge old sessions" code into the queued events handler (nothing triggers it yet).
→ Release 126.96.36.199
Tuesday 16 June 2009
- Rewrote the session handler - each user gets their own scratch database now, which (since SQLite uses file-level locking) should reduce (elimiate I hope) the database locking problem.
-→ Release 9.3.11
Wednesday 17 June 2009
- Built-in a quick a patch to the API and the blogging redirector.
- Fixed photo uploading (actually a bug from Saturday's release I think)
→ Release 188.8.131.52
Thursday 18 June 2009
- It was failing on "start and duration" or "end and duration" with no duration. Made these change silently into "start date" and "end date" respectively
- Fixed adding photos properly this time (added a call to initialise some new workspace in multiple stage activities)
- Reorganised the transaction log and add photo code slightly
→ Release 184.108.40.206
Friday 19 June 2009
No bugs at all in the last 24 hours - that's real progress
- Added a session purger to the deferred action system. Added a trigger in the "build new index page" code so that it is started once a day
Saturday 20 June 2009
- Lots of things on the deferred action system:
- Tidied up deferred action server log.
- Added a "kill server" deferred command that will work with make file on any system
- Make "Make" invoke this
- Made server remove lock file when terminating(!)
- Added a purger for old index pages. Added a trigger for this as well
- Made server wake up more frequently
- Added "turn round here" to route lists
- Added road names and numbers to route lists
- Changed default for narrow canals to neutral - it was leading to exagerated avoidance of other waterways (issue 16).
- Added a message when having smooth preferences would give a significantly quicker, shorter or less locked route
-→ Release 9.3.12
- Bugfix in logon to make recovery of options work properly when you log on.
Sunday 21 June 2009
- Completed earlier "add an isolated place" and "add a waterway" code, locally tested - will test on live when released.
- Made hidden menu items less hard-wired, and made the "edit" button on the home page into one (so you have to be a user to use it)
-→ Release 9.3.13
- Tested by adding a bit of the River Seine
- Removed OS grid from gazetteer entries for places outside the range of the system
- Made database reading code more robust for reading null values created by new waterway creation
-→ Release 220.127.116.11
- Fixed gauges in newly added waterways
- Made new waterways set the distance table as well (needed for later adjustments)
- Made adding distances in metres
- Tested by adding the Manchester Bolton and Bury Canal
→ Relase 18.104.22.168
- Added polyline maps to waterway gazetteers
- Added a more sophisticated polyline fetcher to the API
- Made parent waterways always be mentioned in waterway gazetteers
→ Release 9.3.14
- Made polyline bounds calculation in gazetteer maps work better
- Made polylines automatically adjust when a place is moved or added (deferred action again)
→ Release 22.214.171.124
- Fixed bug where selector was breaking on these newly added waterways
→ Release 126.96.36.199
- Added a pile of places on the S&SYN submitted to the old version, and started extending France.
Monday 22 June 2009
- Fixed a bug where some places were described as being some distance "away away."
Thursday 25 June 2009
Over the last few days I've continued to extend the French waterways network
Saturday 27 June 2009
- Roughly structured waterways into those of the British Isles and those of Mainland Europe. I'll further structure the European ones later (they are just thrown in a bag at the moment).
- Tested that the selector code worked with this - it did
- Added a "locale" block to the system variables. Added code to auto-populate the "distance_units" and "dimension_units" fields of this from a new "waterway_locale" table in the database
- Added top-level locales for Britain and Europe
- Made selection of default units for display use the locale information
- Made a new option to override the default (off by default) - involved writing new "disable" code for fieldsets (roll on HTML 5).
- The combined effect of this is that the UK displays by default in miles and furlongs, and France in km
- Added escaping and re-creation for newlines in wikilike changes
→ Release 9.3.15
- Fixed a build bug in sqlite3_unicode
- Fixed bug where a comma in a user comment lead to it being truncated (special code I'd added to handle sets of coordinates was cutting in unnecessarily)
→ Release 188.8.131.52
- Fixed bug where queued action couldn't write deeleygrams
- Fixed bug where queued action sometimes failed with short read
- Improved parsing of results from Google's API so that links with strange characters in them don't get broken
→ Release 184.108.40.206
Sunday 28 June 2009
- Added code I'd written in May to make plugins have options, and work properly in the gazetteer options page
- Moved the default position for user information up the page
- Gave it a better name and description
- Fixed a layout error that put a blank at the bottom of longish user information boxes
- Fixed the gauge on a couple of London waterways
- Write generated IDs to transaction log file - first stage of something to ensure no synchronisation problems
→ Release 9.3.16
- Prevented stray warnings about better routes being available when they aren't
- Fixed a couple of spacing errors in route distance totals
- Made "override" for locale times act properly stickily
- Made movable bridge times survive properly when options edited
- Made changes to movable bridge times cause recalculation
- Made recalculation recalculate the overall total as well
→ Release 220.127.116.11
Tuesday 30 July 2009
- Fixed bug where particular combinations of modes and durations could cause a segfault in the overnights table
Wednesday 1 July 2009
- Added simple conditional clauses to configuration file - first being parity of the day number(!)
- Another such clause: the value of the HTTP_HOST environment variable
- Used the first of these to put developer and hoster adsense accounts up in equal proportion
- Used the second to use the appropriate google API key
Saturday 4 July 2009
- Added a cache for Google and Wikipedia searches. Reduces server load, and also speeds up page rendering. Currently there is no way to force a cache-reload: I may add that in future
- Fixed a couple of small bugs in JSON conversion (both ways!) that this exposed
- Using these, and a couple of bits of stuff I found on the web, each of which would nearly do what I wanted, I've added a "rate this mooring" feature. It was Steve's suggestion. The next thing, once there's a bit of data, is use it to suggest better overnight stops, and to allow people to comment on why this is a good mooring, exactly where it is etc.
→ Release 9.3.17