Needs a port to Linux

[GoogleCodeExporter]

This product is just screaming for a port to linux. I'm not sure how someone 
would work around the kinect issue, but without it, making this product cheap 
and ubiquitous will never happen. see http://openkinect.org/wiki/Main_Page

Original issue reported on code.google.com by evan.ca...@gmail.com on 25 Jan 2013 at 3:01

[GoogleCodeExporter]

I agree, a Linux port would be fantastic.  I will accept the issue.  

Porting the Kinect would not be difficult as Ubi Displays only requires the 
depth frame to work.  The main work would come from porting the UI.  However, 
using a Kinect on a non-ms platform would violate the MS license agreement as 
far as I understand it.  This would also mean support for less widely available 
depth sensing hardware - although this is not a big problem.

I would be more interested in doing so as a distributed version of the software 
which can run on multiple PCs.  For instance: one raspberry pi running the HTML 
renderer, another processing touch from a depth camera.  These can then work 
together to provide a more scalable experience.  I have an early version which 
workes in this way, but it requires windows support.

What are your thoughts? :)

Original comment by asheepca...@gmail.com on 31 Jan 2013 at 10:23

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This sounds like a good scaleable option, and at ~$99 USD / raspberry,
seems like a reasonably affordable solution. Just don't use SOAP as the IPC
mechanism. I'm curious about the kinect license. I know for instance, that
in the DIY realm, these licenses are meaningless, however, for retail,
what's to stop someone from selling a solution which allows someone else,
who has already purchased the hardware, from plugging it into a non-windows
box?

Original comment by evan.ca...@gmail.com on 31 Jan 2013 at 4:05

[GoogleCodeExporter]

Original comment by asheepca...@gmail.com on 31 Jan 2013 at 6:52

• Changed state: Accepted

[GoogleCodeExporter]

Yea, definitely steering clear of SOAP.  I quite like the lightweight HTTP 
route because it is easy for people to extend and uses standards that are 
pervasive and likely familiar.  I read an interesting paper about the 
challenges in streaming multi-touch events between devices:  
http://dl.acm.org/citation.cfm?id=2107599

The Kinect EULA is here: 
http://www.microsoft.com/en-us/kinectforwindows/develop/sdk-eula.aspx  where 
there is the clause: "You may not: distribute Distributable Code to run on a 
platform other than a Microsoft Windows operating system;".  I am not sure what 
the Microsoft stance is on the NUI community APIs?

Original comment by asheepca...@gmail.com on 4 Feb 2013 at 8:48

[GoogleCodeExporter]

I'm just wondering if there has been any update on a linux port... 

Original comment by kevinont...@gmail.com on 8 Apr 2015 at 7:53