Factory pattern added for using page objects.

The idea here is to provide a mechanism that instantiates page objects by using a simple factory approach. The idea for this is to allow code to take on a very common structure, making it easy to review and easy to build automatic checkers for. This approach is also nice for indicating workflows in a browser application.

There are two factory methods: on_view() and on().

The on_view() factory simply creates the page instance and uses the load() method to bring that page up in the browser. The on() factory creates the page instance but does not need to bring up the page in the browser since it's assumed the relevant page is already in view.
Incidentally, I should have added: it's certainly logical to say "Who cares what other tools do if they are doing it 'wrong'?" It's a valid question. However, in my experience a lot of people move between a lot of these gems and are often looking for similar functionality and constructs. That being said, a case can be made for not perpetuating bad ideas ... if, in fact, the ideas are bad.

In this case, people tend to associate these minimal constructs as a simple creational factory.

But ... I could see an argument for this module perhaps being called Context. After all, that's what the methods do: establish an operating context that happens to be a page definition. What do you think?