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.
Possible. I'm open to suggestions. This "pattern" and its naming is used in many popular Ruby-based solutions, one of which is shown here:

http://www.rubydoc.info/github/cheezy/page-object/PageObject/PageFactory

But admittedly somewhat different than what is shown here:

https://code.google.com/p/selenium/wiki/PageFactory

The concept of a "page factory" has, admittedly, gotten a bit diffuse but the idea is it is a minimal factory that creates or references a page definition, creates a page object, and stores an active reference to it. That's the pattern used in a lot of tools. I used it in my Symbiont tool as well:

https://github.com/jnyman/symbiont/blob/master/lib/symbiont/factory.rb

I suppose this module could be called PageFactory, like the PageObject gem does, but the "factory" also can apply to activity objects, not just page objects, even though most people automating treat them as the same thing.

As I said, I'm open to specific suggestions if it's felt the functionality itself is worthwhile.