What is the difference? For Shoes, not much. It’s pretty arbitrary. In the case of 3.3.1 there are a few bugs/features that we want to fix before we say done. But there’s some features we think you want to look at so, 3.3.1 is available for beta download.
- Video Widgets. You must have a recent VLC downloaded and installed in it default location, versions 2.1.x or 2.2.x. If Shoes finds it, it enables you to use the new code. Please try the sample/expert-video-play.rb for a great example of what it can do. Since its Shoes/Ruby code you’ll want to study it before you write your own.
- Secondary Packaging – This is too odd to describe here so read the wiki
articles This one and this too.
- For Windows, a better way of dealing with Fonts. This needs some more testing so you can help. Aside from a faster install it will be easier/faster to test packaged scripts on the same box. This is a precursor to a way to package apps and pretend to hides Shoes from the user. As always, uninstall older Shoes first before installing 3.3.1
- Ruby 2.2.4 – Beware this may require you to update binary gems that you installed into Shoes.
The Changelog is always the last thing to get updated. Or is it the manual? One of them is the last.
There is one gotcha with betas. If you package a Shoes app or script with the beta, it’s going use the older 3.3.0 unless you know how to change it (you can but then have to remember to undo that when you get the real Release.
I got busy chasing Shiny Things like new bug reports and then went even deeper into some long standing ‘if only you knew’ arcane things and I forgot I’m supposed to release 3.3.1. In my defense, I am becoming more Windows knowledgeable and some of those arcane bugs are really hard. None of which would actually matter to getting Shoes 3.3.1 out of the door, usable for most people.
That’s a personal failing. I was trying to make it perfect and get some other bugs fixed. That and the new features like Video and secondary packaging are not so easy to understand, document or debug. But it is documented in the manual (thanks to passenger94) and at the wiki and I’m always going to get lost chasing shiny things.
It’s released. For better or worse. I think better. Look at the changelog
Walkabout – Shoes 3.3
The name reflects back to when Shoes creator why_the_lucky_stiff disappeared
from the internet. He went walkabout! We changed some icons and backgrounds
to reflect that whimsical theme.
Walkabout (3.3) will be less compatible with the unmaintained 3.1 and not really released yet 4.0 (jRuby), We have interesting ideas of we what we do with Shoes that maybe very difficult to implement in Shoes 4.
New with 3.3.0
- Uses Gtk3 (not gtk2) for Linux and Windows. This will change visuals on both platorms.
- add font and wrap styles for list_box. A popular request – we are limited to what Gtk3 can do, however. The default behaviour for long strings in the list box is now to
ellipize … in the middle. THIS could effect your current apps.
Issue 109 https://github.com/Shoes3/shoes3/issues/109
- A new Svg widget to display svg images – similar to Image but
NOT really the same. Has aspect scaling options based on the svg internals. See samples/good-svgview.rb. samples/good-flip.rb and the manual. We also include a svg deck of playing cards. It’s a bit fragile so please file bug reports and ask for feature requests.
- Very verbose Issue 54 – https://github.com/Shoes3/shoes3/issues/54
- Pay attention to the OSX workaround #178 https://github.com/Shoes3/shoes3/is
- Preliminary save and export methods:
Issue #177 https://github.com/Shoes3/shoes3/issues/177
- add a refresh slot method
Issue 152 https://github.com/Shoes3/shoes3/issues/152
- Uses ruby 2.1.7 or 2.1.8 and rubygems 2.4.7+
Issue 164 https://github.com/Shoes3/shoes3/issues/164
- New splash screen (no animation).
- Added samples/good-image-rotate.rb because it’s fun to watch.
Issue 157 – https://github.com/Shoes3/shoes3/issues/157
Fixed with 3.3.0
- OSX – do not use home brew to manage dependecies.
- Remove pango-querymodules from OSX. Yay!
Issue 156 – https://github.com/Shoes3/shoes3/issues/156
- Uninstall Shoes menu item for Linux (for some window managers)
Issue 31 – https://github.com/Shoes3/shoes3/issues/31
- repaint after slot remove
Issue 151 – https://github.com/Shoes3/shoes3/issues/151
- Windows: 256×256 icons failed when packaging.
Issue 10 – https://github.com/Shoes3/shoes3/issues/10
- developer name and RVM and linker info gets embedded in
binary libraries. No solution worth the effort.
Issue 66 – https://github.com/Shoes3/shoes3/issues/66
- Windows: fontconfig problems if you build shoes and download shoes
Issue 141 – https://github.com/Shoes3/shoes3/issues/141
Yes, we have been busy beavers. Next up is Shoes 3.3.1. It will be Amazing Too! You’ll get tired of how awesome Shoe 3.3 will be. Shoes will be great Again!
There’s just a few more things to finish before Shoes 3.3.0 (WalkAbout) is finished. In fact its good enough for folks who like to poke at new things and leave some feedback. So, there are beta downloads.
There are numerous big fixes and a couple of new features. One popular request is to do something that can shrink long strings in list_box. OSX does a wonderful job at this but Linux and Windows don’t. In 3.3.0 you can set the font for a list_box and you can create a two line entry if you specify a wrap: option which shows two lines of the string with some control on wrapping. The default without wrap is show the first part an ellipsis … and the last part of the long string. That effects existing Shoes programs visually. If long strings is a problem for you, try the beta and let us know if it’s good enough or unsatisfactory. Of course you’ll have to read the manual for what the options details are.
The other new feature is the ability to load and display Svg files and keep them in vector format. You also get some Svg unique methods for managing aspect and drawing a (sub)group in an Svg file. This is actually a brand new widget for Shoes 3.3.0 which took us a long time do correctly. It only looks like an Image. We also included two good sample programs and a deck of playing cards so after reading the manual, you can read the sample code and get familiar with what could be done. If you study the samples you’ll notice an OSX work around. It’s only a beta! We know that bug exists.
And the artwork has changed and – that’s enough for now.
No sooner than when I said Shoes was moving to 3.3, I got a complaint that recent OSX builds of 3.2 don’t work on OSX 9. As is often the case, the bug report was correct. 3.2.25, 3.2.24. and probably 3.2.23 don’t work on 10.9 – they do work on 10.10 but not everybody chooses to update and I promised 10.9. I failed and that must be repaired.
If you don’t care about how or why: There is a Shoes-3.2.26 for OSX. It was built on 10.9 and works for 10.9 and above. If you package a script or app for OSX that’s what it’s going to use on the end-users system. You’ll might notice it is 14MB in size instead of the usual 16MB.
I’ve also built the same Shoes on 10.10 (Yosemite) only its called Shoes 3.3.0 and available at the beta download site
The root problem was I’ve been updating my OSX system (now Yosemite) and xcode and more importantly, I did a ‘brew update’ and ‘brew upgrade’ which is when things really broke. By design brew updates to the latest packages and some of the latest don’t work on 10.9 and there is no way to remove an upgraded package by version number in brew. So I did what I do for building Shoes on Windows (and the we don’t talk about snow leopard build): Build my own dependencies. Don’t use brew. Don’t use rvm.
That was not an easy road nor is it the fast road. But I did it. It’s frozen in stone. 10.9 won’t change and those deps won’t change (unless there are bugs in them that matter). While I was at it, I built ruby 2.1.7 from source and stuffed rubygems 2.4.7 in it. It does not use rvm to install or build that Ruby, just like it didn’t use brew. While that was a very long process (2 days times 3 because that’s how many times I had to start and build every thing from scratch). There are benefits.
Shoes 3.3 is about new infrastructure and really pushing forward. For OSX, I cleaned up the rake files although there is always more to do for that task. The download size is 14MB so it’s about the same size as some Linux builds. No unused X11 libraries inside. No brew or rvm hangovers. I learned some things (X 3)
I went to Costco and bought a 1.5TB usb external drive. $59 USD. Because I live dangerously, I upgraded the pi2 to the latest Raspbian Jessie and eventually got my user name set up instead of the default ‘pi’. It makes everything easier in NFS to have the same user id (1000) on all NFS systems.
Then I had to get ssh whipped into shape. Always a mystery. Always a struggle.
I connected the SeaGate to my raspberry pi2 and after much horsing around with usb cables and even more horsing around with /etc/fstab and netatalk, it’s doing a Time Machine backup of the Mac Mini over enet to a pi with an external usb disk. Slow? Of course it is. Neither enet or USB is going to be fast on a Pi. 50% of one of 4 cores on the pi2. I also need to modify/add to the Linux backup scheme which uses rsync to backup to the pi2.
Having had to restore from backups before, I know what I should do buy there are constraints that in any scheme. Constraints that don’t need to apply get encoded into scripts and processes. Since I’m pushing around GB of data around, it takes time. A lot of time.
It’s available. Nothing really important to most of you.
New with 3.2.25
Fixed with 3.2.25
- documented app.slot().
- really remove shy temp file remnants on Windows
Infrastructure for 3.2.25
What is not mentioned above is this will be the last 3.2.x release. Don’t worry – we are going to create to a Shoes 3.3 because this is as far as I can go with a “maintenance release”. Most of you won’t even notice. And that is is as it should be.
One reason I wanted to analyze the logs was to see if Shoes is being downloaded by real people and how many downloads are from packaging. I did discover an easy way to do some of that. Below is the partial url and the number of time it was used by Shoes for the week of data.
/public/select/pkg.rb cnt 120
/public/shoes/shoes-3.2.24-gtk2-x86_64.install cnt 7
/public/shoes/shoes-3.2.24-osx-10.9.tgz cnt 4
/public/shoes/shoes-3.2.24-gtk2-32.exe cnt 16
/public/shoes/shoes-3.2.24-gtk2-i686.install cnt 2
/public/images/dino.jpg cnt 1
/ cnt 4
Unique IP's 42 Total: 154
There are interesting things. 42 people attempted to do something with the packaging. There were real (to me) 29 packaging attempts in that week and 120 presses on the “Select Architecture” button. 24% decided to package. (29/120). Because of the way Shoes caches downloads, when 3.2.24 was released that week – those 29 had to grab the new version for their cache. Once the new version is loaded in the cache. Further packaging attempts would only be in the 120 number
I’m pleased by these numbers. They are higher than I thought. Shoes is being used! I have no way of knowing how many people actually run Shoes. I might be able to figure out how many new shoes were downloaded by real people that week although that’s a lot harder to figure out and has plenty of uncertainty.
P.S. I have no interest or desire track the ip# back to the origin network or country or try to identify individual users. That said, there are people or bots that are trying to break in. Those I do hunt down and block.
If you don’t have enough to do, you can try the 3.2.24 beta. Or you could wait a few days and I’ll release 3.2.24. Bug fixes and a feature or two. Mostly a yawn unless it’s your bug or you really like the feature.