I cleaned up your README and made it use Markdown and extracted the license to its own file.

[chadoh]

I want to help make TryRuby better, and the first step is understanding how it works. And to do that I needed a better README. So I made it for you. Here's my first contribution. I hope you like it!

[chadoh]

Hmm. Having glanced through your README, it doesn't seem very current (especially considering that you last updated it at the end of 2009).

Perhaps you could bless me with a brain-dump of how it works now? I see you have two Rails apps (by the looks of it) in the TryRuby directory and the tryruby directory. I don't understand. If you let me know what's going on, I'll try to help fix some of your 44 issues and make new lessons with you.

[Sophrinix]

could you re submit this pull request via how I now have my git repo structured. There will be a top level directory called tryruby which doesn't exist. If you could make these changes against the legacy-non-rack/public version of try ruby, I will pull them over to the rack version I am about to upload. The readme is functionally useless btw. I am about to upload code which uses jQuery console and finally deliver on iPad compatibility. Also, I have permission to use jsLinux. This means I will be pushing a full linux kernel to the browser and using a js version of qemu to run it. This pushes the full try linux stack to the browser. This makes lessons concerning vm tuning or even object inspection/visualization like DrX possible :-)

BTW, the jsLinux inclusion won't happen for another month. I am investigating the possibility of writing my own jsLinux so it can be open source. I have a computer science background, so the task doesn't scare me too much. It's a time issue more than anything.

Thanks again for your help.