Plans to make it node compatible?

[automata]

Any plans or appointment to make it run on node/io?

[auduno]

Yes, I've been thinking about making it node-compatible, but currently it's on my (longish) TODO list. :/
If anyone wants to help out, they're welcome. The main challenge is probably to adapt the library to available node canvas & webgl libraries.

[andyinabox]

Perhaps a first step might be to make it CommonJS compatible as it is? At that point it could be installed with NPM and used with tools like browserify.

[andyinabox]

I would be interested in helping convert to CommonJS if you feel that's worthwhile! I would love to be able to use this library in an npm workflow to make it jive well with http://stack.gl and similar tools.

Giving it a go right now just to see how much trouble it actually is...

[andyinabox]

Working in this branch on my fork if you're interested! https://github.com/andyinabox/clmtrackr/tree/CommonJS

My goals are to:

• Maintain browser global compatibility so that it can still be used with the current approach
• Use npm to manage as many of the current dependencies as possible (jsfeat, numeric.js, etc)
• Make CommonJS compatible so that it can be included using tools like browserify as a package
• Include an example for using as an NPM package with browserify

Andy

[jesusgollonet]

In case anyone is interested, I have a super quick & dirty POC of the image example running on node here
https://github.com/jesusgollonet/clmtrackr

It's forked off @andyinabox commonJS port. The changes I've had to make have been basically:

• make it run on node-canvas
• fix json files to make them stricter json (it's amazing how permissive browsers have become)
• shim out or temporarily comment out browser specific stuff (window, document...)
• switch events to EventEmitter

list of my commits here
andyinabox/clmtrackr@master...jesusgollonet:develop

It's nowhere near PR or even test ready, but it's a start and it has worked.

[andyinabox]

@jesusgollonet +1 nice!

[aaronshaf]

This would be nice for those of us messing around with our new Tessel :)

[hyzhak]

👍 yes, it definitely should be converted to CommonJS or something compatible with node.js

[post2seth]

Yes node will be a good, even if that works with nw js then this community
can grow more with desktop power.
On 08-Jul-2016 7:24 PM, "Eugene Krevenets" notifications@github.com wrote:

👍 yes, it definitely should be converted to CommonJS or something
compatible with node.js

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#42 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AC0DcAEMmCqbt3t3GQsOC6WK7YBtX1F6ks5qTlaZgaJpZM4ENvB5
.

[igorescobar]

Is this still an issue? Is there any way I can use this on with node (server side)?