From: Paul Archer <paul@...>
Date: 2009-03-09T01:23:06+09:00
Subject: Re: OO style tutorials?

Thanks very much to all that responded. I'm frankly a bit overwhelmed by 
both the quantity and quality of responses. I feel a bit like the singer 
in The Police's "Message In A Bottle": "Woke up this morning/don't believe 
what I saw/Hundred million bottles washed up on my shore."

@Ian: You're probably right, I need to dig in and get started. It's not 
that I'm a perfectionist, exactly--but I have this "I've got to do it 
right the first time" mentality that I need to get past.

@Phlip: I guess thinking of it as refactoring, rather than just "redoing 
my poor first attempt", that'll help. (See above about wanting to do it 
right the first time.) And thanks for pointing me to your website.

@Yun: What's CRC?

@Udayanga: thanks, I'll check out the "Head First" book.

@Saji & Rick: And the "Design Patterns" book, too.

@Robert: The OO Encyclopedia looks like a good reference. (Might even find 
out what CRC is. 8-)

@Paul: So get to work.

thanks, all!

Paul


On Sun, 8 Mar 2009, Paul Archer wrote:

> I'm pretty new to Ruby, and while I've read (and mostly get) several books on 
> Ruby, I'm having trouble with one thing: Object Oriented programming.
> Don't get me wrong, I get the concepts of OO. I can construct objects and 
> classes. The mechanics of it don't phase me.
>
> I'm good with the how, I'm just a little fuzzy on the how much. To put it in 
> more concrete terms: I'm writing (or, rather, I want to write) a script that 
> takes incoming digital images from my camera and renames them and puts them 
> in a directory structure based on their date. Now, I have a background in 
> scripting (Bourne shell and Perl), and can see doing this in a purely 
> procedural way. But I'm not sure about how to do it in an OO way. Do I 
> represent each image as an object? What attributes should the objects have?
>
> So the question is: Are there any tutorials or resources that go more into 
> the appropriate use of OO programming, strategies for structuring classes, 
> rather than the nuts and bolts of creating objects and such?
>
> Paul Archer
>