Dang, this is why I need to bother to read the docs! Trouble is that
in the currently seemingly unsandboxed shoes, I need to quit it after
each test and reopen it to ensure I get correct results, sometimes
things go wonky or even crash only after an app has already run once
before, and my own experimentation with sockets seems to indicate that
the ruby environment the app is running in doesn't shut down or close
until Shoes itself is quit. A windows-like tactic of closing down all
the left over's of the environment the app ran in, when the last of
it's windows have been closed, would be nice to have here.
Maybe I'll make a duplicate of Shoes.app so I can run two instances of
it, one for the manual and one I can keep opening and closing for
testing :)
Sandboxing is coming, right?