Well that's not really very surprising I know; but currently it's even more of a mess than I was expecting.
We got up this morning, and full of enthusiasm we decided to do some tidying. Now the landing has been full of all our Cropredy kit (tents, chairs, etc) for weeks, and finally we were going to put it back into the roof. Since the roof is full of junk however, we thought it was a good time to finally throw some of it away, and make more room for the things we actually want.
So off I go into the nursery, to bag up all the stuff in there that needs throwing away, and Herring headed up to the roof. Soon he was happily throwing things out of the roof (literally!) and I was walled in by bags of stuff. I say how happy I am that we're finally tidying this lot up, and he says, yes, something normally comes up which stops us getting this done. (Jinx!)
So a bit later he wants to show me something, so I go to look. He is at the top of the loft ladder with something in his hand (small and light, whatever it was). Then suddenly 'Ow, my back!'. He's suddenly incapacitated, and struggles down the ladder. End of tidying!
So now my landing is still full of Cropredy kit AND things destined to be thrown out. Not quite the result I was looking for.
He has assured me he was not deliberately trying to get out of tidying...
Saturday, 30 August 2008
Tuesday, 12 August 2008
Oh why is IE such a time waster?
Well, that's probably not the right question to ask, as its easily answered:
"Internet Explorer is such a time waster as it does not adhere to web standards, and does not provide any sort of helpful error messages."
A better question is why is IE so difficult to work with. The answer to that is probably something along the lines of "Microsoft did not really care about developers who were not using its products."
As you have probably gathered by now, I have just spent the best part of four hours with a Javascript (a rant by itself) error that only appears in IE. What's more, IE provided very little diagnostics about what was actually wrong. So I was basically left with adding lines of code to see if that shifted the error about, so I could gradually narrow down where the actual problem was.
We got there in the end, but it really should not be that difficult. If IE had something like Firebug, it would make the whole thing a lot easier. So would IE adhering to published standards, but I suspect that porcines will be taking off on skis in hell before that happens.
"Internet Explorer is such a time waster as it does not adhere to web standards, and does not provide any sort of helpful error messages."
A better question is why is IE so difficult to work with. The answer to that is probably something along the lines of "Microsoft did not really care about developers who were not using its products."
As you have probably gathered by now, I have just spent the best part of four hours with a Javascript (a rant by itself) error that only appears in IE. What's more, IE provided very little diagnostics about what was actually wrong. So I was basically left with adding lines of code to see if that shifted the error about, so I could gradually narrow down where the actual problem was.
We got there in the end, but it really should not be that difficult. If IE had something like Firebug, it would make the whole thing a lot easier. So would IE adhering to published standards, but I suspect that porcines will be taking off on skis in hell before that happens.
Subscribe to:
Posts (Atom)