Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Is depthjs still maintained ? #55

Open
emilsoman opened this Issue · 5 comments

4 participants

@emilsoman

I was trying to get this up and running but I found that most tutorials on setting up OpenNI are outdated and have broken links and installing it on my Ubuntu 13 so far has not been successful. Looks like you guys were working on a one click installer, any news with that ?
@doug , I was wondering if the repository is still maintained and would get support if I used it.

@doug
Owner

I would not say support is likely. @royshil has valiantly continued to make updates to try and keep it working, but no one is actively developing the code. The approach of Firebreath build and OpenNI backend is good, but staying up to date is hard, so the only way this would be maintained long term is if it somehow started to develop a larger community of volunteers producing pull requests and edits or if someone wanted to pay somebody to work on it. Maybe a wrapper listed on the openni site would work for you http://www.openni.org/software/?cat_slug=file-cat2, though I'll admit I have not tried any of them. @royshil can correct me if I'm wrong since he has been the most recent one to commit.

@royshil
Collaborator

I've planned on moving to OpenNI 2.x but couldn't get to it.
Also, NPAPI plugins are being abandoned for vertical technologies from each browser vendor. Chrome will drop NPAPI in a matter of months, FireFox at the end of this year, and Safari is already past them.
There is no future in NPAPI, and therefore - for this approach to depth.js.
The firebreath website offers some alternatives, but all are bleak: http://www.firebreath.org/display/documentation/Browser+Plugins+in+a+post-NPAPI+world

@doug
Owner

I thought about trying to wrap this: http://developer.chrome.com/apps/usb.html but didn't get very far. In light of the recent down turn of NPAPI it looks difficult to maintain depth.js as is. Could OpenNI 2.x be compiled with NaCl and then the usb interface be done over http://developer.chrome.com/apps/usb.html. The nice thing about this approach would be a user could install an chrome app and not have to ever think about an extra plugin or download anything at all. The downside of course is it would be Chrome only.

@MirkoGelsomini

Hi guys! Are there any news about this NaCl approach?

@doug
Owner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.