Rails vs. Seaside

I have started my first app in Rails at work. Though I find it's ease of database access really appealing, I am not convinced that I find it a better suit than Seaside. There is something about programming everything in Smalltalk that is so much more appealing than figuring out "OK, what can this view see now? What does this partial know about? What does that controller have its fingers into?"

It's killing me trying to find out the context in which everything lives. In Smalltalk I know what the context is... I can evaluate things, I can set breakpoints (OK, self halt), I can send messages to known classes -- not just some digital ether.

Until next time...

About the test

Well, things went pretty smoothly for the most part. The only thing that didn't work as expected was the link. I didn't add the HTTP protocol, so it showed up as a link to a supposed page on Blogger.

Let's try that again, shall we? Here's a link to Squeak.

This is a test

I am writing this from my Blog Poster desktop applet. So, for now this is just a test to see how things go.

From this applet (desktoplet?) I can add links to things I like, I can italicize, and I can bold face things.

So, how does it show up on the web?

Until next time...