> But like I said, just stick to one class per file (and one > file per class) unless you have a good reason not to. > That makes it easy to find any given class, and saves you > from having to think about which classes "belong together". > Which is not neccessarily a good thing. Thinking about which classes are coupled and which are not is an important design decision in my opinion. best regards, Brian -- http://ruby.brian-schroeder.de/ Stringed instrument chords: http://chordlist.brian-schroeder.de/