The RubyCamp Lyon 2010 took place yesterday, Saturday 17th. I was great meeting all those people interested in Ruby, for both professional and amateur matters. Eyrolles was sponsoring the event and offered 10 books (I didn’t win one though – that’s for the sucking part :)).
I also obtained a last-minute sponsoring from Engine Yard, but as I obtained the required info the night before the presentation, I only showed a little bit the interface but didn’t do anything real with it. Instead, I used Heroku and presented the 60-second deployment stuff. I think I made my point there: configuring servers and low-level stuff isn’t fun anymore, let’s put the application at the center of all.
So here’s my slides. Be kind with the layout and content, it was best seeing me (or anybody else talking :)) live than it’s gonna be reading it.
Rails 3 brings a lot of useful features. The main one, in my humble opinion, is the introduction of the classes Rails::Railtie and Rails::Engine.
They bring the modularity that made code more reusable and easily integrable in your current code base. They also prove that there no reason to say that Rails is not ready for the Enterprise. One quick tip for the party poopers (you know who you are ;)): JRuby makes things even easier for your development operations team members as it allows you to run your Ruby app (ie: Rails) within your favorite App Server (Websphere, Tomcat, you name them).
In this article, I will try to explain a little bit what are these new classes, how they were implemented and how to start using them.
If you want to see a live presentation of this, come and join us to the RubyCamp Lyon 2010 on April 17th.
I was about to call this article “Gemcutter Webhooks on Google Wave (and Google App Engine) part 2” but then I realized that it was no more about that I wanted to focus on, but more on the Wave part (sorry Rubyists friends, but I had fun with Python (as long as I don’t try to do metaprogramming Python is nice to play with :)).
Google released the Google Wave Robot API v2 (hurray). In that major revision, they are introducing the Active Robot API that makes it possible for robots (i.e. GAE-baked applications) to interact with Waves. In the previous version, your robot was being notified each time a wave (or wavelet, or blip) was modified or when a participant was added to the wave, but now, your application can actually be active and contact Wave on its own.
In the first part of this series of articles, I was demonstrating how to build a GAE-baked application and how to subscribe to a web hook (being a Rubyist I was taking the webhooks from Gemcutter / Rubygems.org). I went only half-way as I wanted to actually see the result inside Google Wave. But then I think to my self, what a wonderful world think it would be to do something actually useful in my everyday life instead of just demonstrating mix of technologies (even if it’s neat to be able to make applications talk to each others).
So today, it’s gonna be about a 12-hour-design application: Live-Note.
