Cliff, it's a bit unfortunate that we do not maintain more than one JS Framework for the port. Mootools is one solution, many other will prefer others which will not be compatible with this one.
I did put the old port on a branch, and there it can be maintained and bugfixed.
It is not a decision that I made lightly, and I hate it that there has to be a dependency on any outside framework. PureMVC is meant to be tied to language not platform. This is why I long contended that a port to JS was not possible.
As you say, some will be ok with MooTools, but others will want some other framework or approach for doing 'classes'. If we go down that avenue then we might end up with 10 different PureMVC Standard for JS ports. Each with its own ports of various utilities. That way lies madness. Not only from a maintenance standpoint but also on the part of the new developer who comes to the site and tries to figure out which port to use.
And does Mootols support a system of Interface implementation ? I saw a reference to an "implement" method but is it the one used to check if all methods of a class where correctly implemented regarding a "pseudo-interface" ?
IMHO, JS developers aren't likely to care about interfaces (or they'd be using Java or AS3 or some actual OOP language). So in the end it comes down to easily accessible docs, and the simplicity of the developer's day to day implementation code.
Note that I will port my Objs EmployeeAdmin demo in the Mootools port. First release will be as is. Only a conversion from one port to the other. It will be pretty easy. But I will try later to add a support for JQuery above to add some beautiful components.
This would be super! Just the straight port will help to get AS3 people over since they'll have the AS3 reference demo.
And after having a look, I believe that this can work with JQuery. I may be fatally wrong, but I'm not seeing anything at the moment that prevents it. Here's a very brief article about it. http://davidwalsh.name/jquery-mootools
It's funny reading the comments on that article, which simply shows how to set some text color with JQuery and border color with MooTools. Looks simple enough but the thread breaks down to an argument over whether one should use multiple frameworks in a page or not with the main detractor saying that if you want to use a JQuery component on a MooTools page you should port the component (and visa versa). That seems completely daft to me. I'd really like to see if the new port works with JQuery as well.