I’ve delivered simple, clear and easy-to-use services for 20 years, for startups, scaleups and government. I write about the nerdy bits here.
— @joahua
This one should probably even be readable! Seriously, it’s been cleaned up a lot… if the last one was too much, this should be easier to read… and hopefully less dependent upon the original play it’s based on!
I also refuse to use version numbers for a composition, so I’m just going to say this:
I received another 4 letters yesterday from the same company as was responsible for the original posting on this matter. Of course, I’m transferring none of the four domains to that registrar, and they sent it by registered mail from the US.
Sucks to be them.
Anyone else received any? Or am I somehow special?
Tangential P.S.: Please please please read and comment on the post Recreant Strength. Please?
Kindly attack the previous post as much as you want. Vicious criticism is welcomed and requested, seeing as my chances of getting it from teachers are too slim; that’s not arrogance, that’s internal school policy which means they can’t comment on assessments.
Ridiculous.
In all seriousness, please take to it with a knife (or a pen/keyboard, whatever).
The first draft of a short story for part of an assessment task, that I share in an attempt at publishing non-geek content a little more often here. Or something!
Recreant Strength is only available in PDF form at the present time, because it’d take too long to markup properly, and I’m not going to trust either Microsoft Word nor OpenOffice to export to HTML cleanly. Because it won’t.
Damn it, I think I just went and ruined a non-geeky post… sorry!
I just realised I hadn’t implemented this on my website yet, so I just remedied that situation. Due to workloads at the minute I’m not getting time to write lots here, so I thought I’d just share this snippet quickly.
It’s a good practice for search forms to include some text (the value attribute) so that users can know what they’re for, even if it’s apparently self explantory. On this website, the search box at time of writing lacks any label at all except for the text denoting “search” in the box. This is all well and good, up until the time someone wants to actually search for something. They can’t just click the field and type the query and bang return; they need to ensure they select the contents of the field properly, so that they can delete it and it isn’t included in the query.
We can do this with event handlers — in this case, onclick. Essentially, the logic flows something like this:
If a person clicks the field, the contents are wiped.
Anything wrong with that?
Yes, of course there is. That’s the simplest way to do it, but it’s wrong. What if the user types a query in and uses the mouse to click a point in the text to edit it? Their query would be wiped, because onclick clears the field whenever it occurs, regardless of content.
So what do we want? Using the text on this site as an example, we want to wipe the contents of the field when a person clicks it only if the contents are exactly “search”. Admittedly, this still has some problems — if someone were searching for a search engine or had any other reason to include “search” in their string and went to edit, there’d be potential for issues, but that, by my thinking, is tolerable.
The simpler version, which doesn’t check to see if the value is “search” before erasing, is simply
onclick="this.value=''"
The marginally more complicated version, which is far more usable, goes like this
onclick="if(this.value=='search'){this.value=''}"
That means our new input field code looks like this:
<input type="text" class="search" value="search" name="s" id="s" size="13" onclick="if(this.value=='search'){this.value=''}" />
Now go use it!
p.s. No need to say that this isn’t particularly groundbreaking. I’d just forgotten to implement it here, and thought it could be helpful to other people write about.