From: "aidy.lewis@..." <aidy.lewis@...>
Date: 2007-07-12T06:55:06+09:00
Subject: Re: module name == class name?

On 11 Jul, 20:04, "Tim Pease" <tim.pe...@gmail.com> wrote:
> On 7/11/07,aidy.le...@googlemail.com <aidy.le...@googlemail.com> wrote:
>
> If your Login module only contains one class and nothing else, then
> you should remove the module and use only the class. You will still
> have the naming conflict if you should want another Login class.
>
> A different approach would be to encapsulate all the classes related
> to a particular website in a module.
>
> module MyWebsite
>   class Login
>   end
>
>   class UserInfo
>   end
>
>   # etc.
> end
>

Yes, I think this is a very good idea. As I would need only one
require and include.

The one thing I am concerned about is hierarchy. One HTML page does
not inherit another by nature. Should I inherit through a sequence of
actions (i.e. a use-case)? A use-case is not OO - Meyer tells us this.

Should I say:

class Main_Page < Login

Because in the test script the login is an antecedent to the main
page.

I don't like it. I am confused.

Aidy