fluid-work IRC Logs-2012-09-13

[10:30:38 CDT(-0500)] <Justin_o> jhung: are we only supporting cameras connected by usb?

[10:43:58 CDT(-0500)] <colinclark> jhung: Any time you want, fire me links to the libraries we're using that you were wondering about

[10:44:09 CDT(-0500)] <colinclark> and if it's not too much trouble, links to places in the source code where we actually use them

[10:50:02 CDT(-0500)] <colinclark> hey alexn1

[10:50:15 CDT(-0500)] <colinclark> really sweet pull request for FLUID-4779

[10:50:17 CDT(-0500)] <colinclark> nice work

[10:50:19 CDT(-0500)] <colinclark>

[10:51:18 CDT(-0500)] <alexn1> thx colinclark ! it is sweet mostly because of your feedback

[10:51:25 CDT(-0500)] <alexn1> colinclark: and another one is coming very soon

[10:52:31 CDT(-0500)] <colinclark> cool, thanks

[12:27:43 CDT(-0500)] <jhung> colinclark: I'll send you references to lines and files once I've talked to Martin about it.

[12:28:31 CDT(-0500)] <jhung> justin_o: re: support for only USB cameras - yes.

[12:29:01 CDT(-0500)] <jhung> What other kinds of camera were you thinking of justin_o?

[12:29:53 CDT(-0500)] <Justin_o> jhung: just checking.. i suppose there could be firewire, thunderbolt… don't know if there are wifi or bluetooth cameras

[12:30:04 CDT(-0500)] <Justin_o> doubt those would have a high enough resolution anyways

[12:30:58 CDT(-0500)] <jhung> At least not for our application (although 4K thunderbolt cameras are probably sufficient .

[12:31:06 CDT(-0500)] <Justin_o> jhung:

[12:45:28 CDT(-0500)] <colinclark> jhung: In absence of links, I just dug up Martin's bitbucket and had a look myself

[12:45:40 CDT(-0500)] <colinclark> The problem library is pyVLFeat

[12:45:46 CDT(-0500)] <jhung> yes

[12:45:49 CDT(-0500)] <colinclark> which is indeed licensed under the GPL 2

[12:46:00 CDT(-0500)] <colinclark> It's a Python binding for a C library called VLFeat

[12:46:07 CDT(-0500)] <colinclark> which, interestingly enough, is BSD licensed

[12:46:25 CDT(-0500)] <colinclark> Since it's a language binding, we clearly use it as a direct linkage

[12:46:46 CDT(-0500)] <colinclark> a basic rule of thumb with the GPL is that if you link your code with GPL code, your code has to itself be distributed as GPL

[12:47:01 CDT(-0500)] <colinclark> It's often why library authors use LGPL or a non-"viral" license

[12:47:06 CDT(-0500)] <colinclark> Martin uses it one spot

[12:47:18 CDT(-0500)] <colinclark> In order to access VLFeat's sift algorithm

[12:47:25 CDT(-0500)] <colinclark> We have two options:

[12:47:47 CDT(-0500)] <colinclark> 1. Contact the authors of pyVLFeat and politely ask them if they'd consider sharing it with us under the BSD or another license

[12:48:12 CDT(-0500)] <colinclark> 2. Martin could use VLFeat directly, probably with a bit more inconvenience

[12:48:28 CDT(-0500)] <colinclark> Since he's only binding to a single function on pyVLFeat, he may not find that to be too difficult

[12:48:43 CDT(-0500)] <jhung> okay.

[12:48:46 CDT(-0500)] <colinclark> But unfortunately we can't distribute Decapod with the current dependency in place as-is

[12:48:59 CDT(-0500)] <colinclark> If we decide to go for #1, I'm happy to send a note to the authors

[12:49:07 CDT(-0500)] <colinclark> I've had a fair bit of success doing so in the past

[12:50:30 CDT(-0500)] <colinclark> He might be able to make his own Python bindings for VLFeat's sift function as easily as anything else

[12:50:38 CDT(-0500)] <colinclark> I believe Thomas has a fair bit of experience in this regard

[12:50:43 CDT(-0500)] <jhung> Ok. I'll pass that along to Martin and see what he prefers.

[12:50:45 CDT(-0500)] <colinclark> and Python programmers do this quite a bit

[12:50:46 CDT(-0500)] <colinclark> great, thanks

[12:50:58 CDT(-0500)] <colinclark> good catch, jhung

[12:51:32 CDT(-0500)] <jhung> thanks colinclark. Your dark knowledge of open source licenses has proven useful once again.

[13:05:05 CDT(-0500)] <Justin_o> jhung: cindyli and i are looking at want info to return for the cameras

[13:05:37 CDT(-0500)] <Justin_o> jhung: where are all the critical pieces of info that should be returned? do we need to return all the info the gphoto2 knows about a camera?

[13:10:22 CDT(-0500)] <jhung> Not necessary. We need MP count. Remote capture and download capability. Model.

[13:11:35 CDT(-0500)] <Justin_o> jhung: don't seem to have anything for MP count

[13:15:04 CDT(-0500)] <jhung> Resolution?

[13:16:50 CDT(-0500)] <Justin_o> jhung: don't see that either

[13:18:16 CDT(-0500)] <jhung> justin_o: really?

[13:18:19 CDT(-0500)] <jhung> oh brother.

[13:18:36 CDT(-0500)] <jhung> I guess we can do a test capture and download and check it ourselves.

[13:20:29 CDT(-0500)] <Justin_o> jhung:

[13:20:45 CDT(-0500)]

[13:21:16 CDT(-0500)] <yura> https://github.com/joyent/node/wiki/modules

[13:22:33 CDT(-0500)] <jhung> justin_o: What do you mean by that?

[13:22:45 CDT(-0500)] <colinclark> michelled, yura: Specifically, https://github.com/joyent/node/wiki/Modules#wiki-web-frameworks-static

[13:22:59 CDT(-0500)] <colinclark> It's one of those things you can whip up easily

[13:23:01 CDT(-0500)] <colinclark> but badly

[13:23:10 CDT(-0500)] <colinclark> I forget which ones seemed reasonably sensible to me

[13:23:44 CDT(-0500)] <Justin_o> jhung: directing the user to manually query the camera

[13:23:53 CDT(-0500)] <michelled> thanks colinclark

[13:24:12 CDT(-0500)] <colinclark> node-static might be the one, michelled

[13:24:30 CDT(-0500)] <jhung> justin_o: haha.

[13:24:40 CDT(-0500)] <jhung> justin_o: I don't think that will be reliable.

[13:25:08 CDT(-0500)] <jhung> System: "Please check your camera's megapixels."

[13:25:15 CDT(-0500)] <jhung> User: "Mega-what?!"