Yes, it took forever and it’s not perfect but we could wait forever for perfection. Shoes 3.3.2 has some fun new features and some bug fixes. Available via at the usual place.

New with 3.3.2
• Ruby is updated to 2.2.6 (windows still uses 2.2.4)
• gems is updated to 2.6.8
• Profiler with both a GUI and the more traditional text report.
  Written in Shoes and Ruby so you can modify it if you like.
  issue 232
  Wiki – how to use
• Shoes.show_console is now Shoes.terminal with many options for size, and
  colors. It can handle some common escape sequences (colors and bolding)
  On Windows:
  Use Msys> cshoes.exe
  or install one of those ANSI dll things for your DOS era console.
  Rumor: Win 10 does support ansi escape sequences on it’s console.
  Sometimes Win7 does ok with some escape sequence.
  On OSX – scrollbars might not show up. page up/down keys and home/end
  and scroll wheel do work.
  Useful for running unit tests of Shoes and other terminal stuff like the
  profiler text report.
  Note: raspbian may have font issues for ‘monospace’ font.
  issue 236
  issue 256
• exit should no longer be used. Please use Shoes.quit
  issue 263
• plot widget (line,bar,scatter, pie charts and radar/spider)
  issue 288
  issue 264
  Wiki – how to use
  expect some confusion and bugs.
• rename method ‘refresh_slot’ to ‘refresh’ before too many people
  use the old name. This could break some scripts.

Fixed with 3.3.2
• Radio buttons fix
  issue 274
• A new launch script for OSX (cshoes) that works like Linux and Windows
  from the command line. Use Cobbler to create your osx cshoes script.
• Windows: bug261 – fix font loading
  issue 261
• debugging with byebug is much better.
  issue 263
  Wiki – how to use
• fixed: click and release methods return the documented button. top, left
  values. Button numbers start with left button = 1 and increases from there.
  How many buttons and how they are numbered is not something Shoes can know
  about so it’s the user responsibility to be cross platform with buttons > 1.
  issue 240

You may have noticed that it’s been a while since Shoes 3.3.1 was released and 3.3.2 keeps getting pushed into the future. What’s going on?

Well, some of the new features are very difficult to write and time consuming to test. We’ve discovered some very difficult issues with packaging for Windows 10 and so far, there is no way to get around what Microsoft wants and what I’m willing to do to Shoes, or what your willing to do. It’s called “code signing” which requires the annual purchase of a certificate (and the price can be very high with some certificate authorities). I won’t pay for that and I don’t think you should either.

The ground shifted and all we can do is adapt. Don’t package your scripts in an exe! Just tell your Windows users to install Shoes first. Then run the .shy you created.

Ruby also shifts under our feet. As Ruby evolves, they change things. Some of those changes will involve a lot of work for the Shoes C code in the future. I just found another problem with Ruby 2.2.6 (can’t cross compile the fiddle gem for Windows) – that will slow down building and testing even more if it can’t be resolved. I also found a new dependency problem last night for Windows but that should not be too difficult.

And then there are the Shiny Things that may not work, but consume lots of time to discover if it’s a failure or a brilliant idea. Like ebook

This one might cause some problems because it fixes a problem where the code didn’t do what the documentation said for some click and release events. The docs say to deliver |btn, left, top| to the proc. They didn’t. From what I can tell, they never did.

We also accept/present more button numbers instead of is always “1”. Button numbers start at one and increase from there in some pattern only you and your mouse device know. Cross platform? No! Your problem to sort out if the wheel click on OSX is a different number on Linux. Most people will stick with not caring which button. Now you have options.

If you’ve worked around the lack of |btn,l,t| on click and release then you may want to test your scripts with this beta. In this case, the documentation says the right thing and the code was incorrect. Long time wrong. See here

The beta also include the latest, almost nearly OK, plot widget.

I thought Shoes should have a plot widget and I happened to have some ancient 1989 Java code (still works) that I could re-purpose into a C/Cairo based ‘plot’ widget for Shoes. Shiny! New! Fun! Might as well fix some know problems with that old code. So I did that It wasn’t the easiest thing in to do in Shoes but not the hardest either. There are many sharp edges to make round so it might not be in Shoes 3.3.2 – currently it’s issue 264.

It’s never going to be gnuplot replacement. If you need that level of control, you’re already using gnuplot or matlab. This would only be a gateway into the world of visualization).

Toy Data:

Real data:

I like it and there is the possibility to add to the graph in real time with new data or add new data series to plot,

It’s also a long road to release quality. I did mention the edge case problems, Yes, I did.

Shoes 3.3.2 may not redefine Ruby exit and quit like it used to. Instead your scripts should use Shoes.quit. That should work on on Shoes 3.3.1 (and perhaps earlier). I might be the only person that calls exit or quit on a button press.

The window decorator icons and the osx global menu work as before. Avoid the panic and change your calls to Ruby quit and exit to Shoes.quit. Assuming you have any. Of course, you’ll try it and report bugs if it doesn’t work. Right? Please.

I know it seems like a long time since the last release – it has been a long time. Here is the deal, we were mucking around with command line stuff which is not cross platform by definition and is difficult to debug and test. A lot of that difficulty went away with the new cshoes launch scripts for OSX – I think I told you how great fix is?

Pretending to be a xterm console will get you into some dark places. Digging new tunnels in dark places is usually not a successful strategy for finding daylight. Dig I did.

Byebug was never well tested or used and with the old clunky osx launcher not all that usable. Shoes 3.3.2 is going to fix that. From the cshoes command line, `-d` will put you in byebug, pointing to some Shoes startup Ruby code. Set breakpoints in whatever file you intend to debug. ‘c’ and continue to it. Any args after -d are subject to normal shoes handling – so -d knows nothing about those extra args. You can debug the Ruby code of Shoes startup and processing this way or set a breakpoint on the file you want and let Shoes load it normally.

I’ve already mentioned the Shoes.terminal and it’s documented in the Shoes Manual now in case you need to change some appearance settings. Beta Time!

Yes, there are some known bugs. It’s a beta. You might find it useful.