I’m old enough to have experienced the AI dreams of the 1990’s – Lisp machines and Prolog and Neural Nets. I also remember
The curve is also valid for politics and social/cultural changes and even investing. I digress.
So, that said, my old AI crashed and burned to be resurrected as “deep learning” which appears to be on the slope of enlightenment section. Google amd Amazon and others used it to predict what you want next. What role could Shoes and Ruby add? Consider this presentation of tensor flow:
What role for Shoes? Easy dialogs and quick charts, perhaps?
After @backorder moved the Shoes C code into a more logical configuration and I changed the rakefile mess to leverage that – It’s quite developer friendly now if you are of the C persuasion. Most Shoes folk will never see those changes and that’s OK with me. It was something that just needed to be done.
Turns out there is another task that ‘just needs to be done’ – cleaning up my computers by removing all the useless junk I have gathered over many years. Some junk was shoes related and some were just grand ideas I got involed with Shoes. I have a soft spot in my heart for the Raspberri Pi so I ordered an SSD and that board didn’t work, I ordered some more parts to make the ssd work in the main box because good money needs more good money and and then some more parts and then some head scratching on making all these Chinese adapters work and I was pushing GB’s of data around which is kind of slow.
I’m not done yet but I can see the light at end of the tunnel. It just needed to be done.
Shoes 3.3.3 is being worked on. “What’s the hold up?”, You might ask.
Well known secret: Shoes is hard to build from source and if you happen to be a C willing developer it’s a big mess of grok until you can get started. We’d like to make more approachable. The cool kids call this refactoring. This takes a lot of effort (imagine your testing load X 40 and the errors are hard to track down and the fixes break other builds) . But It’s the right thing to do and the right time to do it. Sometimes you have to do the correct thing.
There’s a couple of bug fixes of course. Some smallish new things.
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.
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)
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.
- exit should no longer be used. Please use Shoes.quit
- plot widget (line,bar,scatter, pie charts and radar/spider)
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
- 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
- debugging with byebug is much better.
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.
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
That’s right! Another 3.3.2 beta at the usual place. It’s almost ready for a release. Seriously. After a lot of coding and testing, Shoes can draw line, column, scatter, pie, radar charts and has some interesting features for time series charts with 1000’s of data points. It doesn’t have all the sophisticated options that Excel or LibreOffice and other applications have but it does have a fair amount of knobs you can set and get something useful enough.
See the wiki documentation for something resembling a tutorial.
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).
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.