I had to change a few occurances of Tomahawk.resolver.instance in here, shouldn't be the case IMHO. We should really get rid of those (relying on a single instance here is a bad thing).
Commits after Soundcloud work are not tested by any means, just wanted to get started and see how multiple files feel.
You need tomahawkcc to compile soundcloud, to a standalone resolver containing all necessary parts of former tomahawk.js, rsvp.js and almond.js (and AMD module loader).
See PR for changes in Tomahawk https://github.com/tomahawk-player/tomahawk/pull/336
I had to change a few occurances of
Tomahawk.resolver.instance
in here, shouldn't be the case IMHO. We should really get rid of those (relying on a single instance here is a bad thing).Commits after Soundcloud work are not tested by any means, just wanted to get started and see how multiple files feel.
You need
tomahawkcc
to compile soundcloud, to a standalone resolver containing all necessary parts of formertomahawk.js
,rsvp.js
andalmond.js
(and AMD module loader).https://github.com/dschmidt/tomahawkcc
If you have a working
Node.js
environment, simplynpm install -g dschmidt/tomahawkcc
.If not, here's a standalone build, which should run on 64bit linux: http://download.tomahawk-player.org/test/tomahawkcc