Form is emptiness, emptiness is form.
Following the release of Ruby1.9.2-p136 source and RubyInstaller, I’ve taken time to update RailsFTW accordingly. Head on over to http://railsftw.bryanbibat.net/ for the latest installer.
Aside from updating the patch level, I’ve also taken time to figure out how to build the mysql2 gem using MariaDB instead of MySQL. Less chance of lawsuits = more fun for us.
As a bonus, here’s a screenshot of RailsFTW showing HAML, rspec, and Capybara working properly on Windows:
I hate design work.
Wait, that’s how I started my last blog post. =/
Anyway, I just came to post that I spent the past 10 hours building the mini-site for RailsFTW. There you could download the latest version of RailsFTW (v0.3) which contains the recently released Rails 3.0.3.
That site also contains lists of recommended links and downloads for people who want to use Ruby and Rails in Windows. If you have some suggestions, feel free to send them over to me.
With mysql2 now working on Windows here’s a small update to my hacked together Rails on Windows installer. I also took the opportunity to update the Rails to 3.0.1.
Also replaced the libmysql.dll with the one from MariaDB. That should probably be enough to keep the Oracle lawyers at bay…
Download Rails For (the) Windows v0.2
latest version is v0.4. grab it here
One of the questions raised during the last Rails training course I held was “Can Ruby on Rails work with XAMPP?”
With this new version of Rails FTW, the answer to that question is YES.
Download Rails For (the) Windows v0.1
latest version is v0.4. grab it here
OK, so this version doesn’t install mod_rails on XAMPP, but it does allow you to get around the headaches involved in making Rails 3 work with MySQL on Windows.
Here’s a basic rundown of the changes from the last installer:
Rundown of the quick blog app demo using this installer below the cut.
Continue reading “Rails FTW, now with MySQL support!”
Red asked me to give a talk in Ignite Manila 1 mainly because he remembered that I tend to break character once in a while back in our old workplace. It should be easy for me to give a presentation on something related to anime given my level of experience in the matter.
Problem is, even if I focused on just anime and manga instead of the entire Japanese hobby culture scene (which would include cosplay, collectibles, etc), I still have literally dozens of possible topics to talk about.
After thinking about it for a day, I went with the topic that I could say that I am really passionate about: the story of how we reversed the fortunes of UP AME; from being a hopeless anime organization into a thriving one. Not only is it a significant part of my life, the topic would also be relevant for most of the audience (I doubt that most of them aren’t inside a club or community of their own).
—
I put a decent amount of effort into this talk, not only because I don’t want to embarrass myself or the org, I also don’t want do look like a hypocrite after bashing the presentations in last year’s Y4IT.
Most of my effort went to the slides. It took me at least 3 days to finish them mainly because of my lack of experience (dammit, I’m a software engineer, not a graphic designer!) and because I had to look for good pictures from various sources. I also had to re-read Presentation Zen since it’s been a long time since I’ve made presentations.
Preparation for the talk itself was difficult, though it’s not as hard as the slides. I’d have to thank Scott Berkun for this part, his Confessions of a Public Speaker as well as his Ignite talk on giving Ignite talks gave me invaluable tips for making my talk.
One thing I learned on my own about Ignite was that Ignite presentations are more like song performances than presentations when you have more than 4 points to make. My talk had 7 different points so the timing is important. It didn’t worry me, though, since I have experience singing in front of a lot of people. I just had to practice enough that my mouth goes auto-pilot when on the stage, ignoring the inevitable effects of stage fright.
My script went through at least a dozen revisions throughout my practice sessions. With at least 3 runs per revision, I’m guessing that it took me 60 partial runs (just a 1-minute section) and about 30 full runs to get the hang of things. As you would see below, even with all this practice, I still had to ad-lib and adapt to the situation.
—
Oh and yeah, Ana Santos of Sex and Sensibilities talked before me. Talking about hardcore geeks after a talk on sex was kinda awkward. D:
—
Script, slides, and side comments below the cut.