TPBETA 1505

TPBETA 1505

My own little concept for marking my spot as a TypePad beta tester. A small badge, with ‘TPBETA’ on the left, and ‘1505’ on the right. 1505 is the ID number for my TP blog — obviously, the older the blog, the lower the ID number will be. Just another idea to toss into the mix of ideas running around right now. ;)

On the off chance anyone wants to duplicate this, I used the Kalsey Button Maker with the following settings:

  • Outer border: 666666
  • Inner border: ffffff
  • Bar position: 50 pixels from left
  • Left box:
    • Text: tpbeta
    • Background: 006699
    • Text color: ffffff
    • Text start: 5 pixels from left
  • Right box:
    • Text: 1505
    • Background: dddddd
    • Text color: 000000
    • Text start: 4 pixels from the bar

Update (prompted by Grumpy’s comment): You can find your blog ID# by logging into your TypePad admin page, going to your weblog editing screen, and checking the address bar of your browser. The end of the URL will look something like blog_id=1505 — there you go!

TPS Syndrome

Am I suffering from TPS: TypePad Snobbery? You know it, baby! ;)

Common symptoms discovered so far:

Live Comment Previews

The ‘Live Comment Preview’ hack that I use on The Long Letter has now been implemented here on Eclecticism. If you know what I’m talking about, then we’re good to go. If you don’t know what I’m talking about, then click on the “Comments” link to any post, type something in the comment box, and look just below the comment box. It’s a nifty trick. ;)

I originally picked this up from ScriptyGoddess, with help from Phillip. Geeky tech details on my implementation here follow.

All this is is a nice little JavaScript addition to the page. I don’t believe that this will constitute a security risk, but I’m no expert, so use at your own risk. ;) Obviously, if you do want to use this on your site, you’ll need to have access to your templates.

In the header of the individual entry template, just after the already included JavaScript bits, I added the following code:

<script type="text/javascript">
 var newline = /n/g;
 function ReloadTextDiv() {
  var NewText = document.getElementById("text").value;
  NewText = NewText.replace(newline, "<br />");
  var DivElement = document.getElementById("TextDisplay");
  DivElement.innerHTML = NewText;
  }
</script>

Then, in the body of the template, just after the closing </div> tag following the preview and submit buttons, but before the </form> tag, I added the following:

<br />
<h2>Live Comment Preview:</h2>
<span id="TextDisplay">Note: if you're comfortable with HTML, feel free to use it in your comments. If not, just type away. Single returns will be automatically converted into linebreaks (&lt;br /&gt;), double returns will be converted into paragraph breaks (&lt;p&gt;). This text will disappear as soon as you start typing.</span>

Lastly, in the textarea tag that defines where the comment text is entered in by a visitor, I added a onkeyup="ReloadTextDiv();" declaration. The full textarea tag should look as follows:

<textarea tabindex="4" id="text" name="text" rows="10" style="width: 80%;" onkeyup="ReloadTextDiv();">

What all this does is actually simple enough. As a visitor enters their comment into the comment box, each time they release a key the onkeyup function calls the ReloadTextDiv JavaScript snippet that I added. This function loads any text inside the comment box (identified by its ID of "text"), replaces any carriage returns with <br /> tags so that line breaks appear correctly, then writes the output into the element identified as "TextDisplay" — in this case, between the span tags I added after the submit and preview buttons.

If you find this useful, feel free to use it in your own pages. While I wouldn’t refuse credit, it really does belong to ScriptyGoddess and Phillip. Enjoy!

The skyline is back

One minor change to the site design here — I moved my shot of the Seattle skyline that I use over at The Long Letter to this weblog also. Even when that’s the only change, replacing that garish green with the black and white skyline gives a very different feel to the page. I like it. It’s a return to the cool blue/grey combination that I keep returning to.

Bright neon lime green just wasn’t “me”, anyway. ;)

Squirrel Monkeys

Two pieces of news broke in one day yesterday.

Item one: “Microsoft acknowledged a critical vulnerability Wednesday in nearly all versions of its flagship Windows operating system software…[which] could allow hackers to seize control of a victim’s Windows computer over the Internet, stealing data, deleting files or eavesdropping on e-mails.”

Item two: “The Homeland Security Department has chosen Microsoft Corp. as its preferred supplier of desktop computer and server software, according to a statement issued late Tuesday. …perhaps most important to Homeland Security’s mission to get agencies communicating more easily, Microsoft will provide the standard e-mail software for the entire department.”

I loved Jeffrey Zeldman’s summary:

Let’s see what the government might have chosen in its effort to protect American lives from ruthless, technologically sophisticated terrorists:

UNIX, Linux
Inexpensive or free.
Requires some user knowledge.
Practically invulnerable to attack.
Mac OS
Costs money.
Easy to use.
Practically invulnerable to attack.
Windows
Costs money.
Easy to use.
Can be hacked by a squirrel monkey, thus is wide open to attack.
Produced by a company the Department of Justice found guilty of criminally abusing its monopoly power — a finding that is supposed to result in punishment, not in fat contracts bankrolled by taxpayers.

To the bureaucratic mind, the choice was obvious.

Sounds safe and secure to me.

Plain text in Apple's Mail program

For some reason, Apple doesn’t include a preference to default to plain text in Mail, the bundled e-mail application. The preference is there, though, just not in the interface.

Quit Mail, then type this into the command line:

defaults write com.apple.mail PreferPlainText -bool TRUE

(via MacOSXHints)

Tablet PCs

I just had someone ask me what I thought about TabletPCs. Honestly, I haven’t given a whole lot of thought to them. I have, though, been a fairly regular reader of Robert Scoble‘s for a while now, and he’s big into the TabletPC thing, so I just pointed them to his site. Too bad Radio doesn’t categorize, though — he’s mentioned TabletPCs so many times in so many different contexts, that it’s difficult to narrow down any single post about the various pros and cons of TabletPCs. The first two I came up with were both from last December. I’m sure that Robert himself could come up with better links, but those were a good start.

Pings?

Why is it that when using a desktop blogging client (I’ve noticed this behavior in three so far: Userspace, Kung-Log, and NetNewsWire), pings don’t seem to be sent when a post is published? The URLs to be pinged are saved with the post, but the actual ping doesn’t seem to take place. Is this a limitation of the XML-RPC implementation, or is it possibly a bug within TypePad (cringes, and looks around wildly for the gods of the NDA to strike me dead)?

News to nobody

Something I just discovered, thanks to a comment at Etherfarm. If you’re running Windows XP, on-screen text legibility can be drastically improved by switching on ClearType.

To do so: Start Menu > Control Panel > Display > Appearance tab > Effects… button > Use the following method to smooth edges of screen fonts option > ClearType menu choice > Apply.

Observe:

2003/07/graphics/standard

Without ClearType

2003/07/graphics/cleartype

With ClearType

Of course, text under OS X looks like ClearType-enabled text under XP from the getgo, without having to drill down through dialogs and menu choices to find the option, if you even know that it’s there. But, admittedly, at least the option is there, and it does help.