EMadden wrote:Morning.
Why didn't you build eValid as a "plugin"... wouldn't that have made it easier to deal with?
Thanks
That is a very good question and the answer is fairly deep in the details of eValid's architecture EMadden.
To begin with, here is a page outlining a few of the initial design considerations for eValid:
http://www.e-valid.com/Products/Documen ... aints.htmlThat that is only part of the story.
When eValid was conceived, the notion of a plugin was not available.
Even later, when plugins were available, we found out that eValid didn't need that extra level of control.
As it turns out, eValid runs 100% on resources that were -- and are still -- available in the DOM of the browser, beginning with IE 5.50 and up to and including IE10.
So. our thinking was, if you don't need it, then don't worry about it.
It is interesting to note that even if you HAVE a plugin (or even multiple plugins) eValid doesn't care about that.
Instead, eValid relies on some very fundamental features of how the DOM interacts with the browser to accomplish its functions of test recording, playback, synchronization, etc.
-- eValid Support