Name SeleniumDriver is confusing

[v-mwalk]

Discussion with a colleague confirmed using the name SeleniumDriver for the root class is confusing. With method names that are the same as Selenium (such as FindElement) but with different functionality there is much confusion.

To resolve this, I propose renaming SeleniumDriver to Controlium (open to suggestions!) and perhaps the renaming of methods that clash with Selenium - IE. FindElement->ElementFind etc. Note that the old names would still be persisted to ensure backwards compatibility but marked as depreciated.

In addition, HTML blocks - which is what Controlium is based around - should be referred to as Components; which is what there are referred to as in the dev world. This would mean - for example - ControlBase (the base abstract class all components inherit from) would be named simply Component.

This would mean a major rework, and an update to the Java version as well. However, the conversation with the colleague was really just a confirmation. He put is very eloquently, asking what Controlium brought that Selenium didn't already , and the prime reason was the naming confusion.