ChildChange vs ChildAdded, ChildRemoved

I don't like consolidating ChildAdded/ChildRemoved into ChildChange.

It's the equivalent of reducing Press/Release/Click into MouseButtonEvent,
forcing you to _always_ check which button has been pressed and what the
event is.

Put it this way, with ChildChange, it will virtually always start:

ChildChange ++= function(v) {
    if (indexof(v) > -1) ...
    else ...

What's the point?

I do agree that, for consistency, it should be capitalised as it's an
event but ChildAdded / ChildRemoved are much saner than forcing a
mandatory index check.

- Charlie

The future of webapps - www.xwt.org