Drop "on" prefix from event names

[davetodd]

Right now all the events have the "on" prefix, like "onvaluechange" and "onfocus". This is weird because you have to do editor.on("onvaluechange"). I believe this was done to avoid conflicts with the jQuery focus event, but we should still figure out a way to work around it.

[chriskwan]

@leobalter, @Wilto we were thinking an easy way to fix this would be to namespace the events, e.g. "arte:focus" instead of "onfocus". What do you guys think of this approach or is there a better way?

[leobalter]

Custom events are a good idea, but they might not be exactly the necessary fix to avoid conflicts. I'll take at ArteJS events interface to give you a better feedback.

[Wilto]

I think namespacing might be a good first step here, but I’ll defer to @leobalter.

[ilyavolodin]

Just to give a bit of history, the reasons why events are prefixed with "on" is because when this project was started, there was no plans originally to make jQuery wrapper for it. Because of that, to confirm better to browser events like document.getElementById("#a").onclick = ... events were prefixed with "on". I guess it was never changed later.