Up to Main Index                              Up to Journal for June, 2015

                     JOURNAL FOR TUESDAY 30TH JUNE, 2015
______________________________________________________________________________

SUBJECT: Thanks for all the extra work Google!
   DATE: Tue 30 Jun 22:21:34 BST 2015

NOTE: I’ve used more Unicode than normal. If you see � you’re not viewing it
properly :(

I’ve recently been up to my eyeballs in work due to recent Google changes and
all of our clients jumping up and down now wanting their sites to be mobile
friendly. Normally my lament is “bloody IE not working properly again!”, then
go off in a huff while I try to work around IE compatibility issues without
breaking everything else. While working on mobile stuff this lament has
changed to “bloody Safari not working properly again!” - this is on iPhones.
Is it me or is Safari now lagging behind IE for compatibility issues and
missing features?

On top of that I’ve been struggling with a regression bug in Chrome. Bug
478696[1] - Chrome ignores keyboard input with focus-follows-mouse window
manager. Instead of just whinging about it I’ve actually been setting a build
environment, compiling Chromium and testing patches and providing feedback.
That is how much the bug has been screwing up my workflow! :( I hope the fix
will be in the next stable Chrome release - currently on 43.0.2357.130.

Usually my workflow is: edit code, tab to browser, Ctrl-R to refresh, check
changes, tab to editor, repeat all day long. With this bug I’m leaving the
keyboard and grabbing for the mouse most of the day :(

At the moment there is a mini heatwave, it’s about 30°C / 86°F, and I could
really do without any hassle. Could also do with some more coffee. Sit tight,
be right back…


  > You wait – time passes
  > Thorin sits down and starts singing about gold. [2]


…back again, beverage acquisition successful! :)

What was I going to talk about next? WolfMUD and the work on exits I guess.
Work has been progressing slowly with the exits issue[3] with everything else
going on. I’ve been working on both solutions: Exits referencing Exits and
Exits referencing Inventories. So far neither approach seems to be making much
of an impact on the amount of code or its efficiency when writing commands.

One thing I have been considering is adding a 'Here' direction or a 'Here'
member to Exits which would reference the current locations Inventory. This
would avoid the bounce to the parent Thing and having to lookup the current
Inventory attribute.

Hopefully I’ll have time to work on the Exits tomorrow - which looks to be
even hotter…

PS: Why is I've (with a straight apostrophe) okay with my spell checker but
I’ve (single closing typographical quote) is not? *sigh* yet more hassle. Oh
why didn’t I just stick with plain old ASCII damn it!

--
Diddymus

  [1] https://code.google.com/p/chromium/issues/detail?id=478696

  [2] Quote from “The Hobbit” text adventure by Melbourne House

  [3] See entry for Monday 15th June: /journal/2015/6/15.html


  Up to Main Index                              Up to Journal for June, 2015