3 ms·
I'm not sure what you mean by "fixing" javascript's OO implementation, but I guess you could have a look at qxoo, qooxdoo's oo engine re-packaged as a standalon
by plq 14y ago
I'm not sure what you mean by "fixing" javascript's OO implementation, but I guess you could have a look at qxoo, qooxdoo's oo engine re-packaged as a standalone project.
https://github.com/fjakobs/qxoo/ https://github.com/fjakobs/qxoo/
- some1else 14y agoThanks! It looks like a full-featured solution, and it's even a commonJS module. Thing is, that CoffeeScript solves the most common pain though (the *.prototype syntax), and the chasm between that and interfaces, singletons, private members, etc., might be too big for the standard use case.
- jarek-foksa 14y agoAs of ECMAScript 5 you can build inheritance chains without constructor functions and *.prototype objects. It is simple enough without any framworks (https://gist.github.com/1558929 https://gist.github.com/1558929) and it is just a bit more verbose than CoffeeScript classes (https://gist.github.com/1671263 https://gist.github.com/1671263)