Hi there.
Up to now, Shoes has ambled along as an experiment of mine. While
being very promising, it's always been very buggy and prone to
crashes. And, well, this is probably due to all of the changes in
the platform code. For example, the OS X stuff was only recently
rewritten in Cocoa. And this month I also moved away from using
macros and refactored all of the Windows and GTK code.
Actually, the new Cocoa code is the big deal. Before that, I
didn't think Shoes was going to make it.
{o}
^
In July, Shoes will hit its first anniversary. I'd like to put out
a really solid release for that. A finished manual, perfect
EXE/DMG injection, faster repaints, sandboxed scripts.
The new calendar:
* raisins (july 31)
* murder (september)
* feinstein (december)
To do this, I hugely need all of your help. How can you help?
Here's two ways:
1. I would like to do a bug day every two weeks where we
can meet on Freenode's #shoes channel and sort through
your obstacles. Would anyone like to help set these up
and spread the word?
2. The Shoes triathlon. Writing a Shoes app in a day should
be easy, given that Shoes programs aren't very long. The
triathlon would be to (1) write the app, (2) explain the
app in a tutorial form and (3) make a video demoing the
app. So, basically, I need help putting this event
together, if you it sounds good to you guys.
Okay, and how to report bugs, you might wonder? I've started working on
the new bug tracker: http://github.com/why/sheila. Until then, just
post your bug reports here to the list or send them to my e-mail
account.
{o}
^
If you don't think Shoes is going to succeed or if you think I
might quit, maybe look at the github graph: http://github.com/why
I've rarely missed a week committing to Shoes. I've said I would
dedicate four years to Hackety Hack and I'm one-and-a-half years
into that deal.
See, this is an impassioned plea for your help! Really, if
Shoes is going to be the ultimate platform for beginners, it's
got to be ladders beyond what it is today.
_why
