today, we visited a water reservoir not far from here where we used to make bike tours or just pay visits to when i was really young. here are some impressions.
it’s not the first time i’m annoyed by php, and surely not the last one. i’ve often called php an ad-hoc language, which is changed a lot and contains many inconsistencies. and often tends to break backwards compatibility. for example, i recently upgraded to php 5.3 (while upgrading the server; before, it was running 5.2 if i recall correctly). this instantly broke the openid server i’m using to login to mathoverflow. this was easy to fix, apparently some behaviour changed and i had to replace two or three lines of codes by almost identical ones to make it work again. now i stumbled about something else, while posting something new on blackness. namely, the member function setdate of the datetime object changed a little bit: on success, it no longer returns null, but the object itself. (in case of an error, it still returns false.) well, the blackness editor was expecting null to indicate success, and complained that the data was invalid. great.
i mean, its nicer to return the object (to allow cascadation, at least if one is sure no error occurs – otherwise one is screwed), but why just change this between two versions?! such changes make upgrading php a russian roulette: it might break your programs. and in many cases (like this), it might take you a long time to find out that your program is broken. and when you found out it’s broken, you have to search for the problem, identify it, only to find out that php just changed the rules a little bit. this is just bad. and yet another reason not to use php for anything serious.
(and a programming language not useable for anything serious is, well, to be bluntly: a big pile of crap.)
here’s my project 52 shot for the third week. the topic was
so finally i have snow, which i really could have used last week. well, that’s bad luck. but the good thing is, snow and shade encapsulates my two favorite colors, if there are any: black and white. (just look at this blog, which colors are prominently featured.) so i took one of the snow photos from today, made it black and white with my favorite photo editing program, gimp, and here it is. please click the photo to get a larger version:
technical details: 1/160s, f/5.6, 31mm, iso 100, aps-c; modified using gimp.
while complaining last week that all snow was gone, when i had to produce a photo for project 52, i got snow this week while staying in zürich. here are some snowy impressions from around noon:
later, it started snowing again, continuing until the evening. on my way back from my current quest, i took some more pictures (and already lamented about the absense of my big camera, which is much better suited for low-light photography). the interaction of snowflakes with beams of light is just a perfect thing to photograph!
walking through falling snow is just great!
when i noticed that the spielwiese‘s archives list was pretty long (one line per month, that accumulates over time), i looked for a way to turn this into a tree which is by default folded together to a short list of years. after a short search, i found the wp-dtree plugin, which works nice, but doesn’t really do with the archives what i wanted to do. so i created my own plugin, which uses wp-dtree’s javascript code to create an archives tree as i wanted it. now i polished the plugin a bit, and decided to upload it here, so other interested persons can try it out.
to use it, you must have the wp-dtree-30 plugin installed and activated. otherwise, you won’t see anything. you can download my plugin here. just unzip it into your wordpress’ plugin directory, activate it and add the “lazyone’s archives.” widget to your sidebar and configure it as you wish. as usual, no warranty for anything.
note that you need a new enough version of wordpress. wp-dtree-30 requires wordpress 3.0.1, and my plugin requires wordpress 2.8 (for the new widget interface). so if you have a wordpress installation older than 3.0.1, either upgrade or don’t use the plugins.
here’s my project 52 shot for the second week. the topic was
winterwunderland
(ist abgebrannt, und dann schreiend weggerannt).
well. last week, there was a lot of snow left, but this week, it’s all gone. almost all, that is. not that the leftovers are noteworthy; “wretched” describes the situation better. (and if i would have burnt wood or ashes, i would have decorated a bit of it, to add at least some dignity.) please click the photo to get a larger version:
technical details: 1/40s, f/16, 50mm, iso 400.
today i was in our local church here in seppenrade to take a photo of the crib, which will be removed the next days due to planned constructions. it was rather dark inside, which resulted in some nice photos:
here are some more snapshots i made while roaming through the house:
and finally, a little christmas tree:
i finally got around to do my first project 52 shot for the first week (i.e. last week). the topic was
while walking around the house, i happened to watch out of my window and had this fantastic view, which ended up as a snapshot. please click the photo to get a larger version:
technical details: 1/6400s, f/1.4, 50mm, iso 200.
as you might have noticed, musikwiese has its categories displayed as a tree. i did this using the wp-dtree plugin. this is pretty nice, and i thought that i might also be able to use it for spielwiese‘s archives list – after all, that list contains like 40 entries. so it would be nice to have a tree with the years as top-level nodes, which can be expanded to get a list of months. unfortunately, wp-dtree doesn’t do this. so i started programming myself, creating a small plugin which outputs the code wp-dtree should create to display such an archive. and, it seems to work fine! i also included a noscript fallback for people with disabled javascript; in that case, the “classical” archives will be displayed.
if you are interested in my plugin, ask me, and i will send it to you or maybe also upload it somewhere here.
