I’m sure someone’s posted about this already, but here goes anyway.
I was going through my RSS feeds, got to Cidoc, and clicked through a couple of articles.
One of the first told me about the Scottish Arts Council’s logo, brand and such-like. The very next one told me about Quark’s new logo and identity.
It’s fresh, inviting, and open
says Quark. I can just imagine the response at SAC: Maybe it is, but it’s exactly the same bloody logo as ours!
I had a bit of geek pleasure this week. I took an in-house web-application and tidied it’s output up. What was once a pile of tag-soup junk is now clean, accessible, sentatically correct, valid HTML. This was relatively easy, once I’d got my head around the way the app works. It’s quite nice now – but it sits on our intranet, so you’ll never get to see it unless you happen to work in the same place I do.
Then I got cocky. I thought If I can do that for that app, why can’t I do it for this ever so slightly more complex one?
So I started looking at the source files. Holy crap! It looks like the code was written by a gibbon jumping up and down on the keyboard! As soon as I started trying to tidy it up, things got squelchy. Undo, undo undo! Put it back exactly how it was! Phew. Making that one look nice is going to be an interesting experience.
Still, I think it’s worth doing, even if it’s “just” an in-house intranet application. Your in-house customers are just as important as the outside ones. If you don’t keep them happy, the products and services that they produce for outside customers won’t be as good. Keeping the interface and the code clean and accessible means that it’ll be nicer for user’s to interact with. What’s more, it’ll be easier for the next set of programmers and designers to work with next time around.
Oh my. Lost is a bit good isn’t it? I’ve just reached the end of Season 1. Yes, I know downloading the whole series at once is cheating.
I won’t spoil it for everybody else – we’ve still got about another five months of it on TV over here. Suffice it to say that I really need to see Season 2, right about now.
I’m currently working my way through a sample chapter Sitepoint‘s DHTML Utopia book – partly to see if I want to buy the book, and partly because I’m trying to get my head around event listeners. I got some way through the chapter, testing my work in Firefox as I went, and it was all going swimmingly.
What happens in Internet Explorer then?
, thinks I. Precisely nowt. It was at this point that my colleagues looked around to see what the swearing was all about. From the book:
Naturally, making events work cross-browser is not as easy as just following the DOM standard. Internet Explorer doesn’t implement the DOM Events model very well. Instead, it offers a proprietary and different way to hook up event listeners and gain access to event data.
What’s the point in having a standard if the most popular sodding browser is going to completely ignore it!?
Luckily, the book explains ways around Internet Explorer’s Javascript deficiencies in a calm and friendly manner (e.g. This is inconvenient but not catastrophic; it just means that you have to take different actions for different browsers.
). It’s entirely possible that I’ll buy the book, simply because it’ll help dig me out of some big holes.
So, I decided to try applying the lessons learned to one of my own projects. It was all going fine, up until I went to test it in IE. This time, the scripts were working perfectly. No, IE had to find some other way of buggering it up. Now, every time an event was fired, IE decided to re-load all of the background images in the elements effected. Flickerytastic dude! Does this mean I have to put an epilepsy warning up on the page? I navigate away, click ‘back’ and all is fine again.
A bit of googling, asking around on mailing lists, and tearing out of my fast-greying hair reveals that are two ways of fixing the problem:
It’s really frustrating that every time I try to do almost anything on the web, Internet Explorer jumps in front of me and holds up an enourmous stop sign. It’s good in a way, in that it forces me to find an acceptable way around the problem. I just wish finding that answer didn’t usually double the time it takes to complete a project. If IE7 really has improved as much as Microsoft say it has, I can’t wait for it to arrive. It’s just a pity that IE5, 5.5 and 6 will continue to linger for as long as they inevitably will.
Just going through my old text messages and came across this one from Alice, my sister. I’ve been reluctant to delete it for some reason.
SMS From: Alice Mob 07.07.2005 11:04 Oliver they are blowing up london the whole of zone one is shut. im ok though. im in selfridges wierdly people are still shopping! Alice x
It was quite a relief to get that message, I can tell you. Quite insightful too. Despite all the chaos going on outside, these people were trapped in huge department store. What else were they going to do?
Hello Abigail. Yes, you, in the pink.
Your big brother (that’ll be me) has been spectacularly useless, and failed to get you anything nice for your birthday (that’s today, as I’m sure you’re aware).
This could be something to do with not having a clue what you’d like. He thought about another game for the ‘cube but he would appear to have already bought you all the good ones. The he thought about a CD, but what does an Abbie listen to, if anything? The chocolate, sweets and book/music/beer token options all seem like a bit of a cop-out.
It could also be down to sheer disorganisation on his part.
No doubt he’ll give you a call later and see if you know what you’d like [1]), have a think, buy something and put it in the post. Maybe he’ll come and visit you at some point in the near future? He can’t plan his life beyond tomorrow so who knows when that might be…
Anyway, he hopes you’re having a good one and that you’ll forgive his uselessness – you really ought to be used to it by now!
[1] The reader might be interested to know that this question usually results in an “erm…” or something very very expensive indeed.
You know when you go into the supermarket at the end of the day and the checkout girlie (or indeed blokie) blatantly doesn’t want to be there? You know, grumpy, really wants to go home, that sort of thing – just like you or I at the end of a bad day.
Smile. Be cheery. Say please and thank-you. It’s amazing how often they’ll cheer up. you’ll find that they start the transaction as a grumpy monkey and and up as a shiny happy monkey. You’re the winner. Feel free to carry on with your day as normal.
Anyway, it’s been a while hasn’t it? I’ve been going through one of those phases where I’ve got plenty to write but no real motivation to do it. Moving house (let me know if you want my new address) didn’t help. It’s the summer too, so there’s always something better to be doing outside. And lots of other excuses too, while I’m at it.
Anyway, I’m now living in a rather fantastic thatched cottage. My sister has major house envy, which is always a bonus. I’m still in Cheltenham, just a bit further out than before. The cycle-commute is longer as a result, which is probably a good thing, even if riding a bike is the last thing I want to do on some mornings. Which reminds me, I must put the rear-mudguard back on if these storms are going to persist in soaking me. I’d best do that now, or I’ll forget and end up sitting in damp trousers all day tomorrow or something. Laters.
A couple of years back, when working for a small design firm, I put together a little website for a new restaurant in Leicester, called Mobius.
I was quite proud of it at the time, except for the glaring bug. It makes use of the Suckerfish menu system. Due to a (still unfixed) bug in Gecko-based browsers (including Firefox), if the menu intersects with an element which has a style of overflow:auto;, it’ll disappear as soon as you mouse-over that element.
At the time this really annoyed me. I posted on various web-forums asking if anybody had come across the same problem and if so, how they went about fixing it. It soon became clear that it was a bug in the browser, and there wasn’t a lot I could do about it. In the end, I gave up and left it. At the time, Firefox was very much a niche browser, not one who had been downloaded by 80 million users and was coasting comfortably past the 10% market share point. Alas, the site still suffers from the problem, just as it always did.
Now, I was quite surprised when out of the blue, two years later, someone calling themselves “Event Horizon” emailed me out of the blue with a potential fix for the problem. “Perhaps you could apply this fix on the Mobius site you worked on.” they said. “Not likely” I replied, “I don’t work there anymore, but thanks nonetheless”.
The very next day, I was ever so slightly taken aback once more, when I took a phonecall from Mark Sanders at Chorlton Web & Design. “Two years ago” he said, “you had some problems with overflow in Firefox”. “Indeed I did” said I, “and in a very odd turn of events, I got an email about the fix last night”. “Bloody Hell!” exclaimed he. Very bizarre.
Anyway, I figured that if two people were going to contact me about the problem in the same week, there’s quite a demand for this knowledge. So I thought I’d share the story and the link to the solution. I hope it’s useful to someone.