Monthly Archives: January 2015

In case of dangerous fumes

Shoes 3.2 doesn’t stink. Actually it works pretty up and walking good (an
American folk/country music phrase) It’s out of intensive care. The surgery was successful and Shoes 3.2 walks and talks.

Perhaps you find that overly dramatic. I’ll explain. I’ve sent or watched loved ones go into hospital. A few got out. I’ve been in the hospital and when the anesthesia mask settled onto my face, I thought I’ll wouldn’t know if I died on the table. And then I woke up and I wasn’t dead. The nice nurses insisted I remained hooked up to some sort of perverse leg warmers that “massage” my legs to reduce the chance of post-operative blot clots and strokes. Devil devices. The big test is when you can get your ass to the toilet by your self and take a shit. Do that and and staff starts looking at you like a house guest that has over stayed their welcome. If this hasn’t happened to you or a loved one yet, it will.

So, I went home and with some help from the neighbors, I fired up the smoker and produced 8lbs of pulled pork to share with them. I was alive, I was home, I have a smoker (Weber Smokey Mountain). That was “being alive again” for me. Sharing my Q skills, for better or worse.

What’s the connection to Shoes? Well, I was still physically weak and I’ll get tested for cancer in 1 month, and then two and 3 and 6 and 12 months. What could I do to share? Something I’m good at that other people might care about. Shoes! I can fix Shoes so it runs on a Raspberry Pi. That worked so well that I tried Windows/gtk and superficially, that worked too. I was still alive and the cancer tests kept coming back negative. I bought a Mac Mini just to build Shoes. That worked too and folks started to pay attentions. Some left words of encouragements. A very skillful person offered to help (Thanks Ian) and we’ve (notice the change from singular to plural) really beating down the bugs, adding features and making Shoes better. With some bickering between us on the best way forward.

There is nothing but shyness that keeps you from joining the 3.2 community. I used to be shy. I’m still a dumb shit. File a bug report. Or a feature request, even if you think it’s an idea only you care about. Some really great ideas come from simple requests. get a free github account and tell us what needs to be done or ask a question.

Without you’re help, we’ll just do what we think you want and we’ll do it wrong or never because no one told us what they wanted.


I’ve been busy on Shoes. Ian’s been busy on Shoes. We have added to the stack of bug reports but there was also time to add some neat stuff for the next release. We’ve improved the Shoes console. Ian really went to town on the code to display the manual. It acts more like a web browser – it’s got forward and back buttons! The manual responds to some common keystrokes like forward and back keys. The manual is really a joy to use now.

So much joy that we noticed it was missing some things and incorrect in some places (because the documentation always lags behind). We fixed some of that.

Then Ian thought the irb sample could be a really useful tool for Shoes folks if it had a few additions to be more like the real Ruby irb. Absolutely Brilliant and Fiendish. You didn’t know you want that. You do.

And we’ll have a new splash screen. Because we’re wild and crazy guys.

We might even fix a bug or two.

Shoes 3.2.20

Available here and which will get you to the same place. Just minor bug fixes, you say? Let me convince you why it’s worthy of a release number.
Reported Bugs:

  • fixes bug #13 – clipboard doesn’t work on Windows and Linux.
  • fixes #27 – Manual: Move focus to search box

Unreported Bugs:

  • remove simple-video from samples
  • In manual, State that video widgets are not available
  • remove files left over from debugging and development

Well that’s all lovely and boring. Let me show what one person (Ian) can do when you fix a bug (#13)
New features:

  • fixes #15 Clipboard support in the console
  • Add “Copy This” button for code snippets in the Manual


How many times have you wished for a way to copy those error messages into an email or couldn’t be bothered with a screen shot and image upload and finding a site to hold the image and then registering at the site and then you just gave up reporting the bug? Somebody else will report it. Right?

I don’t know about you, but it’s many, many times for me. No longer! You can report your console error messages as text strings. Just “Copy” to the clipboard and paste into your email or browser window.

Then Ian added the Save button so you can copy the console text to a file. Nifty for those that like to keep longer term copies of things.

But wait, If you order now…


Ian then added a “Copy This” to all the Manual’s “Run This” code snippets, which as you might guess – copies the text (not the image) to the clipboard so you can paste them into a text editor where you can save as a file of your own and run it from the command line or splash screen. Modify them to see what happens. It’s your file now! Explore, try things. The original snippet is still in the manual and you can use the “Copy This” button again if you need to start over.

I don’t know about you, but I’m not a very good Shoes programmer and I often go to the manual to see what is supposed to work. All to often, I’ve retyped the snippets and because I’m not that good at typing or proof reading, I screw that up.

January 2015 Status Report.

I like to write status reports because it reminds me of what’s been done. Although it’s quiet here at the blog, We have been busy and you know what? I really like where Shoes is. Ian’s filing bug reports for everything he doesn’t like and fixing a couple bugs in the process, all the while making sure I don’t screw up. Invaluable stuff!

I’ve been doing more admin stuff than coding. (re)Writing some wiki stuff and trying to improve building from source. It’s still hard to build 3.2 from source but it’s less confusing than it used to be. Just in case some other developers would like to join us. Those changes were long overdue. There is still much to do.

Want a tease for 3.2.20? Of course you do. We’ve fixed some annoyances you might have glossed over as no big deal or never noticed. We’ve add a few little features that you might not notice if no one told you about them. Then you’ll say “I always wanted that!”
Would you like to spot what’s new without a written hint? One and Two

3.2.20 is maturing. We are a functioning project and we’re taking care of business. I am really happy about that. Really happy.

The Shoes4 teams has a pre-release 3 out. Give it a spin. They’ve been busy too.

One last thing:

We have the ability to to build Shoes 3.2 for OSX 10.6 (that runs on 10.6+ (Intel) but it’s not an easy build for me and it’s missing the sqlite3 gem at the moment, so it’s not really mainstream. It may never be mainstream. But, it exists and if your stuck in Snow Leopard but want to use Shoes, leave a comment.

Twelve Days of Christmas

Thats been how long since the last post. Sorry. We have been busy on Shoes 3.2 but it’s not glamorous or newsworthy like fixing Shoesbugs or adding features to Shoes. Just working on the OSX infrastructure that only Shoes developers would care about. Edited some wiki pages to be less out of date. Re-factored some rake files (for OSX). Plumbing and wiring. Maintenance for a Maintenance Release.

We’re still working on getting Shoes 3.2 built properly (my definition of properly) for OSX 10.6