February 9, 2012

15 Segment ASCII Display Project

15seg 15 Segment ASCII Display ProjectWith the resurgence of interest in hobby electronics, I thought my readers might enjoy looking at the details of a simple project I did with cheap EBay-acquired parts. This was a fairly straightforward scrolling LED ascii display.

Goal

A simple-to-use Simstick display, capable of showing a reasonable subset of ASCII, utilizing cheap 15seg displays.

15 Seg Display

I chose to use LTP588G 15seg display, since it was cheaply available via EBay or surplus.

Segment Lettering

I could not find a “standard” segment-to-letter map for a 15 seg display, so I have extrapolated from the standard 7 seg layout:

15seg 15 Segment ASCII Display Project
[Read more...]

GBuy predictions

crystal ball GBuy predictionsI have a prediction for Google’s soon-to-be-released service GBuy that I haven’t read anywhere else. I think they may incidentally take out PayPal, but it will only be a pleasant (for them) side-effect of thier real goal. I just don’t think that goal is big enough for Google.

They want the holy grail.

They want to monetise the internet, and they surely want to remove their deadly over-reliance on ads. Solution? Micro-payments. That’s right, micropayments. I know, they have been tried several times and they’ve always died a miserable death. But, no one with the clout, public goodwill, and intelligence of Google has tried.

Imagine, if customers could manage their subscription settings via Google:

  • Customers could put a maximum pay-per-page or pay-per-session for a site, and then when they hit those sites, there would be no barriers, logins, or subscription requests. Google would just hit their credit card or bank accounts for them, and forward the money to the site.
  • Google could feature sites which have GBuy enabled by some icon on the search listings.
  • Sites would be able to be “all content”, and no longer have to serve ads, or optionally no longer have to serve ads – for the paying visitors.
  • Google could also enable pay-for-feed, which is something no one is really trying yet.

Steps to a goal

I don’t believe they will just roll out what I describe in phase one. What I think will happen is that they’ll undercut PayPal’s fees, getting a lot of instant webmaster users. People will sign up for GBuy, and Google will move that money around for them, taking a small cut, possibly even deliberately taking a small loss to fuel uptake. When a certain critical mass is reached, when enough people have accounts, they’ll release the micropay API/subscription model.

They’ve already said they aren’t really interested in the stored-payment model, I think they are aiming higher. Higher probably even than my modest prediction. I don’t have unthinking awe for Google, like so many do, but I sincerely respect and admire their audacity at going after new and bigger markets.

[tags]Google,GBuy,PayPal,predictions[/tags]

Dvorak as a cure for typing pain – a four year report

blue keyboard Dvorak as a cure for typing pain   a four year reportFour years ago, I decided to resolve a problem that had been troubling me for years. The situation was that my wrists and fingers hurt almost all the time, and it was clearly due to computer use.

I decided to do some real research with the intent to follow up by adopting a new scheme for interfacing with my computer. To facilitate coming up with solutions, I decided up front that there were no reasonable limits on what I might choose to do. I was willing to learn new keyboarding skills, even to the point of learning to chord-type.

Searching for the Ergonomic Holy Grail

My solution constraints:

  • must be possible to use for the medium-term future.
  • must not be purely or primarily Windows based.
  • must be at least half as fast as qwerty keyboarding, preferably faster.
  • should be programmer-friendly

What I came up with:

  • retrain from qwerty to dvorak typing
  • vary posture
  • get a zero-force touchtyping keyboard with an integrated mouse

I knew it was going to be difficult to change my keyboarding habits. Moving from the QWERTY key layout to Dvorak is hard. You see, other than the numbers, only two letters stay on the same key. It is worth it, since moving all the keys around to more optimum positions pays off in speed and in comfort. With a QWERTY layout, one can only type about 10% of the words in the English language without leaving the home row. With Dvorak, the number moves to something like 70-80%. For example, the home row for the left hand has all the vowels, with only “Y” requiring any finger stretching, and that is with your strongest finger, the index. The right hand has “DHTNS”, which makes many word startings-and-endings immediately accesible.

Here are the steps I took to switch:

  • Bought Dvorak key labels for all three of the keyboards I used at the house
  • Remapped the key layouts on my Linux and Windows machines (which is very easy)
  • Found an online Dvorak typing exercise, and practiced it for an hour at a time, 3-4 days. Went cold turkey.

It took about two weeks of mental pain before it “clicked” and I regained any real ability to touch type. Until then, I would find myself with my fingers poised, frozen, while I tried in vain to remember which finger to move. I toughed it out by using the mental stick and carrot. The stick was that I really hate wrist pain and I honestly believed the ergonomics would help (even if only marginally) decrease my pain. It is my career, after all, and I want to be able to continue it without a slow ramp of pain. The carrot was that, quite unexpectedly, I really love the layout. I love efficiency and elegance. It is that and more. Almost addictive.

Switching Back

I kept using the Dvorak keyboard for two and a half years. Almost all my wrist pain went away in about six months. I can’t honestly say how much the Dvorak layout played a part in this wonderful change, since I changed a few other aspects of my approach to computer interaction at the same time. I can say without reservation that it was worth it, however. Changing layouts allowed me to relearn some other aspects of data input, which would had been difficult to address by themselves.

A year and a half ago, I switched back to the QWERTY keyboard layout, primarily due to the hassle. Although I never fully lost my ability to type on standard keyboards, it was a mental switch that took a few minutes each time. I’m a senior programmer. I often need to type on other peoples’ computers. Using a Dvorak layout made me look fumbling and inept whenever I did so. Beyond the simple ego of it, I was surprised to find how integrated the standard layout is in non-PC usage. My Palm Treo phone had a qwerty layout. Powells books has a qwerty layout on their book search kiosk. The library used the standard layout as well. These sorts of problems, along with my needing to work with coworkers and their standard layouts, meant that I had to switch back and forth several times a day.

I love the Dvorak layout, I think it is easier and less painful. But, the hassle wasn’t worth it for me in the end.

The conclusion is positive, however. My wrists do not hurt any more. Paying close attention to keyboarding habits, especially including posture, has paid off in a permanent reduction of pain. Another payoff is a marked increase in typing speed, even after the permanent switch-back to QWERTY.

[tags]keyboard,dvorak,qwerty,carpal tunnel[/tags]

WordPress 2.0.1 still has annoying attribute stripping

stop button Wordpress 2.0.1 still has annoying attribute strippingWhen WordPress 2.0 was released, its aggressive tag attribute stripping caused me a lot of pain. For example, I couldn’t link any image at all using my favorite blogging client, Ecto. I was hoping that the 2.0.1 release would fix this problem.

Well, yes and no

It fixed some-but-not-all of the tag problems. It still strips too much for my taste. I’ve once again added several attributes back into my wp-includes/kses.php file.

The changes I’ve made are:
'div' => array ('align' => array (), 'class' => array (), 'id' => array(), 'style' => array()),
'img' => array ('alt' => array (), 'class' => array(), 'align' => array (), 'border' => array (), 'height' => array (), 'hspace' => array (), 'longdesc' => array (), 'vspace' => array (), 'src' => array (), 'title' => array (), 'width' => array ()),
'span' => array ('class' => array (), 'id' => array(), 'style' => array()),
'p' => array ('align' => array (), 'class' => array (), 'id' => array(), 'style' => array()),
'tag' => array(), 'tags' => array(),

You can download a pre-tweaked kses.php here: wp2-kses-fix.zip
[tags]Wordpress,Wordpress2,Wordpress2.0.1[/tags]

Ajax remoting for Invisible Castle

happy Ajax remoting for Invisible CastleI offer the code for my Invisible Castle site under a GPL license. However, it is not the easiest code in the world to get running. Plus, it is really overkill for most people. Most people who ask for the code really just want a die-roller with database lookup for their site. They aren’t really prepared to provide a working Python/Cheetah/MySql install. That’s fine, I could help them out and pick up a new skill in one fell swoop.

Ajax to the rescue

I quickly wrote a simple remote interface to the die-roller, and then used the Prototype library to implement an Ajax interface to it. Simple simple simple. It worked beautifully, with one problem, that pesky restriction agains cross-domain XMLHTTPRequests. So, I wrote a simple little PHP proxy page, and it works perfectly!

All together, this was a pretty nice payoff for a couple hours of work, including ramping up from zero about XMLHTTPRequest objects. I already have two remote client sites functioning happily using the script, which has a working demo with install instructions here.
[tags]javascript,Ajax,cross-site scripting,xss,xmlhttprequest,prototype[/tags]