Posted via web from Tom’s posterous

Awesome. Things I remember about this game from my childhood:

* The goal of the game is to get Larry (your character) laid.
* Before playing you had to answer a series of questions to prove you were an “adult” (which is kind of unfortunately not part of this online version).
* At some point in the game you slip a receptionist of sorts some “Spanish Fly” and she gets all worked up, only to run off to have sex with her boyfriend. I remember being very disappointed at this point in the game.

Posted via web from Tom’s posterous

This is the most appealing Kindle I’ve seen yet. I kind of want one, but I’m hoping Apple will introduce a similarly sized tablet-esque device sometime this year, so it’s worth waiting a while (that and I don’t have $500 to burn at the moment)

It seems IE “enforces” this by quietly blocking cookies from any host that offends the rule. Of course, IE won’t complain when you visit a twisted, underscore-flaunting host, but if cookies are any part of the equation (say, required for login to work) IE will quietly ignore them. This will undoubtedly lead to hours of fun for anyone who is responsible for making the site work the way it should.

According to Microsoft:

Cookies on ASP pages are blocked if the server name contains characters that are not supported by Domain Name System (DNS). For example, you cannot use underscore characters (_) in the server name. This behavior is by design.

Granted that’s an old change, 2002 old. Still, it interfered with my week so I’m taking this opportunity to complain about it.

Multitasking is a trap, a siren song to the overworked. You can’t write multiple proposals at once, you can’t work on multiple webapps at once and you can’t give your attention to multiple clients at once. Chances are if you think you’re multitasking you’re either breaking up and prioritizing your tasks well (which is good, but not “multitasking”) or you aren’t giving any task your full attention.

Multitasking is a misleading term that has turned into a professional talking point and – in my opinion – it needs to be purged from our productivity vocabularies.

Embedded Rich Text Editors

The technologies the web relies upon have steadily advanced, new more powerful tools have been created, and thanks to the ever-enduring Moore’s law we can squeeze a great deal of functionality into a web page. There was a time when embedding a rich text editor in a page was an excessive and extravagant feat, yet today there are a plethora of simple ways to do it. TinyMCE and FCKEditor are the most popular, but many others exist (including the impressive YUI editor which I did not know about until today).

Embedded rich text editors are great tools but they may not be suitable for the discerning geek. In general these editors have a reputation for creating messy and verbose source code. How important this really is has been and will be a subject of debate for some time, but there is no question that clean, standards-compliant code is a good thing to have. When it comes down to it, I tend to think that if you can do something the right way with a reasonable amount of effort, why sacrifice correctness for a little bit of convenience?

Lightweight Markup Languages

When HTML is too verbose or complex for what you really need to accomplish, and rich text editors don’t give you the quality of code you’re looking for, you’re left with lightweight markup languages.

There are a number of different approaches to lightweight markup, in fact if you follow the Wikipedia link above you’ll possibly find more than you really care to know about, but there are only two that have emerged as the preferred choices among the current generation of web developers: Textile and Markdown. Markdown is great, but for the sake of this article I’m going to focus my attention on Textile, which is currently my favorite.

Textile relies on simple markup that is easy to edit in a plain text editor, or a simple textarea on a web form. A major benefit of Textile is that it is also easy to read in it’s unprocessed form, so editing it is relatively painless and not nearly as confusing as editing raw HTML. The syntax is easy to pick up, and new users can typically start authoring comment with very little introduction.

Here is a quick example of Textile code:

h3. Sample

This is a sample paragraph, complete with *bold* text, _italic_ text,
+underlined+ text and even a "link to google":http://google.com/.

For kicks, here is a second paragraph.

And this is what it looks like when displayed:

For a complete list of Textile samples view the example-based reference.

One of it’s greatest strengths, Textile adds a great deal in the way of proper typography. For most of the web, trademark symbols are left as TM, hyphens are substituted for en-dashes and “dumb” quotes are used instead of smart quotes. With Textile these nuances of type are easy to handle with very little effort. A (TM) is automatically converted to ™, a single hyphen is converted to an en-dash (two hyphens for an em-dash), and straight quotes around phrases are converted to smart quotes. With minimal effort you get a significantly more professional result.

Conclusion

Lightweight markup is not without it’s shortcomings. Rich text editors often provide enough visual aides to get people going with little or no introduction, and as I stated before the value of clean HTML in a web page is sometimes debated. In addition, the nature of rich text editors leaves the door open for more powerful features, such as built-in flickr browser or point-and-click YouTube video embedding. All the same, for most tasks, for most sites, I believe that lightweight markup languages are the best option.

Links of Interest

• Textile:
  • Wikipedia entry
  • Homepage and playground
  • Example-based reference
• Textile Alternatives
  • Markdown
  • reStructuredText
• Embedded Rich Text Editors
  • Kupu
  • TinyMCE
  • FCKEditor
  • YUI Rich Text Editor

That’s one option. Another is to have a side-scroller (also with a buzz song and pathetic bumble bee shrieks) that requires tapping on enemies (creepy bugs, drawn by Jess on a napkin some booze-inspired evening a while back) at which point the bumble will destroy the target with laser beams from it’s eyes. As targets are destroyed, the bumble will emit a little giggle or if something goes wrong, a sad sound of disappointment.

I think the bumble will be named Claude, Claude the Clumsy Bumble. There will be merchandise too, plush Claudes, coffee mugs and toddler onesies.

That’s the plan anyway…

Freddie works in a more shark-like manner. He usually circles me a bit first, getting a feel for the terrain and potential angles of approach until he decides on a way in. Maybe he’ll lay down on the far side of the desk where it’s too much of a hassle for me to remove him. Then he slowly twists and slinks his way towards me until one outstretched paw can just rest on my hand, at which point the claws come out just a tiny bit, just so I know he’s there. If I even acknowledge that he’s touching me in any positive way, say by petting him or making eye contact, he pops up and starts trying to rub on my face. It’s cute, but damn if it’s not annoying. Like an Ewok with a spear, or a child Jonathan Taylor Thomas.

Note the reckless sprawling and complete disregard for the things around him. Textbook Freddie maneuver.

Mikayla when she isn’t being chatty