*** tpb has joined #timvideos | 00:00 | |
*** iiie has quit IRC | 00:24 | |
Sewar | CarlFK, iiie2, mithro, mithro-work: Any thoughts? http://mohammedalhadab.com/gsoc/edid-hunting/ | 01:45 |
---|---|---|
tpb | Title: Mohammed Alhadab (at mohammedalhadab.com) | 01:45 |
CarlFK | Sewar: "xrandr ... Depends on third-party application. " | 01:48 |
CarlFK | I wouldn't call that a problem | 01:48 |
Sewar | yeah, since it is used on most distros, that should be fine, right? | 01:49 |
CarlFK | xrandr .. from what I know about it, it is rock solid. | 01:49 |
*** iiie2 is now known as iiie | 01:49 | |
CarlFK | Will be written in Python ... doesn't sound rock solid.. doesn't even sound like it exists yet :) | 01:50 |
CarlFK | iiie: any chance the tunnel to plank is up? | 01:50 |
CarlFK | even better yet, can you do a df and see if it is full of log file ? | 01:50 |
iiie | I'll see... | 01:50 |
CarlFK | hmm... I doubt it | 01:51 |
*** mithro has quit IRC | 01:51 | |
Sewar | "Will be written in Python" that is for grabber script, everything is in Python, so far | 01:51 |
Sewar | python-smbus is C-extension for python | 01:52 |
iiie | connection refused on pyvideo, localhost | 01:52 |
mithro-work | Sewar, you'll probably want to write this code in C as it's easier to distribute a compiled C binary then a Python script | 02:09 |
iiie | mithro-work: compiled C binaries aren't particularly portable. i386, amd64, and maybe even lib versions mater | 02:19 |
mithro-work | iiie, a i386 binary works fine on an amd64 machine if compiled statically | 02:20 |
mithro-work | iiie, compiling statically is the trick | 02:20 |
iiie | speed isn't an issue, if the python works why aim for C? Make it a python package, put it on pypi | 02:21 |
iiie | mithro-work: What's the audience? Who is going to run the python or binary? Do we have a trusted channel to get the binary to them? Why do they trust us to run a binary from us? | 02:26 |
mithro-work | iiie, speed isn't an issue, portability is | 02:27 |
iiie | Sure it's easier from from a "here take this and run it" stand point, but we're already limited to technical users. What drives them to contribute? They want to fill out the database. | 02:28 |
mithro-work | iiie, Most non-technical users will quite happily run a binary without thinking if you ask them too | 02:29 |
Sewar | 'git clone; python script.py' vs 'git clone; make; ./script' | 02:29 |
mithro-work | Sewar, compared to "double click on this file" | 02:30 |
iiie | mithro means to distribute the compiled file | 02:30 |
Sewar | Isn't that rare in linux land? | 02:30 |
mithro-work | Sewar, reasonably | 02:30 |
mithro-work | Sewar, but for a small tool which you run once of twice perfectly reasonable | 02:31 |
Sewar | it's either through package manager or compile it yourself | 02:31 |
mithro-work | Also, on Windows it's the only real option | 02:31 |
iiie | alright, I won't worry about it. yeah, for windows you run it or you don't, there is almost never anything to look at. | 02:32 |
Sewar | iiie: meeting in 25 minutes, I'm ready when you are. | 02:35 |
mithro-work | and trying to create a compile binary with python is much harder then it first seems | 02:35 |
mithro-work | It's okay to prototype with Python | 02:35 |
iiie | I think we have two different cases though, 1) technical users who may be willing to help add to the database, but I would expect to be more leery of running a binary from $random_people and 2) non-technical people who would have no compunction about running a binary, but lack reward for contributing to the database. | 02:35 |
iiie | Oh, I thought there were three routes going here | 02:35 |
iiie | windows, mac, linux | 02:35 |
iiie | py2ex or py2app are indeed a pain | 02:36 |
mithro-work | Actually there are two different routes | 02:36 |
mithro-work | a) capture directly on a persons machine | 02:36 |
mithro-work | b) capture via a third-party hardware tool like the HDMI2USB | 02:36 |
mithro-work | a) needs to support as many different type of machines as possible - mac, linux, windows | 02:37 |
iiie | a) was the only one I'd considered. I didn't realize that the hardware project was going to call out to the internet, I guess it makes sense in retrospect | 02:39 |
iiie | Sewar: yeah, I still need a couple minutes | 02:39 |
Sewar | py2exe worked fine when I used it with wxWindows | 02:42 |
mithro-work | Sewar, if you think py2exe worked fine then you have obviously not distributed your binary far enough | 02:44 |
Sewar | exactly :D | 02:44 |
mithro-work | py2exe has some friken weird failure cases | 02:45 |
mithro-work | plus it makes *huge* binaries | 02:45 |
mithro-work | I don't imagine the edid grabber being more then a couple of kb | 02:45 |
Sewar | So I should write them all in C, each os in different project/codebase? | 02:48 |
Sewar | Since they will only share uploading part ... | 02:48 |
mithro-work | Sewar, you can probably share about 50% of the code, just abstract the edid reading method | 02:49 |
CarlFK | yeah, if it needs to run on windows, a binary will be way better than python. so may as well use that for all 3 OSs | 03:15 |
CarlFK | and py2exe.. I tried that once, pretty sure I don't want to try again. | 03:16 |
Sewar | I will switch to C and see how it goes, binary and no py2exe | 03:28 |
*** hyades_ has quit IRC | 04:02 | |
*** hyades_ has joined #timvideos | 04:02 | |
*** hyades_ has quit IRC | 04:29 | |
mithro-work | Sewar, you might need more then a single method for extracting edid information under Linux | 04:38 |
*** hyades has joined #timvideos | 04:57 | |
CarlFK | mithro-work: how is the user going to know which to pick? or can the app see what ..um.. dependencies or apis are available? | 05:11 |
mithro-work | CarlFK, the user doesn't pick, the tool tries them all | 05:12 |
CarlFK | k | 05:12 |
mithro-work | The tool should require *no* user interaction | 05:14 |
iiie | "run and forget" | 05:21 |
mithro-work | pretty much | 05:21 |
*** parx has quit IRC | 06:07 | |
*** hyades has quit IRC | 10:36 | |
*** hyades_ has joined #timvideos | 10:36 | |
*** hyades_ is now known as hyades | 10:36 | |
*** rihnapstor has joined #timvideos | 11:29 | |
*** rihnapstor has joined #timvideos | 11:30 | |
*** hyades has quit IRC | 12:22 | |
*** rihnapstor_ has joined #timvideos | 12:30 | |
*** rihnapstor has quit IRC | 12:31 | |
*** hyades has joined #timvideos | 13:09 | |
*** rihnapstor_ has quit IRC | 13:59 | |
*** parx has joined #timvideos | 14:52 | |
*** mithro has joined #timvideos | 15:02 | |
*** hyades has quit IRC | 16:11 | |
*** hyades has joined #timvideos | 16:37 | |
*** hyades has quit IRC | 18:22 | |
*** rihnapstor has joined #timvideos | 18:35 | |
*** rihnapstor has quit IRC | 18:36 | |
*** rihnapstor has joined #timvideos | 18:36 | |
*** hyades has joined #timvideos | 18:39 | |
*** hyades has quit IRC | 18:51 | |
*** rihnapstor has quit IRC | 19:13 | |
*** hyades has joined #timvideos | 19:14 | |
*** hyades has quit IRC | 19:26 | |
*** rihnapstor has joined #timvideos | 19:32 | |
*** rihnapstor has quit IRC | 19:32 | |
*** rihnapstor has joined #timvideos | 19:32 | |
*** hyades has joined #timvideos | 19:43 | |
*** hyades_ has joined #timvideos | 19:47 | |
*** hyades has quit IRC | 19:51 | |
*** hyades has joined #timvideos | 19:52 | |
*** hyades_ has quit IRC | 19:53 | |
*** rihnapstor has quit IRC | 20:49 | |
*** hyades has quit IRC | 21:25 | |
*** hyades has joined #timvideos | 21:26 | |
*** hyades has quit IRC | 21:29 | |
*** hyades has joined #timvideos | 21:29 | |
parx | hyades and Sewar: Recently you've been posting about once a week. Our agreement is for daily blog posts. | 21:34 |
hyades | ok | 21:35 |
hyades | will post more frequently :) | 21:35 |
Sewar | sure :) | 21:36 |
parx | CarlFK and iiie: call your students out when there's a lull in evidence of work | 21:36 |
parx | Thanks hyades and Sewar! Look forward to seeing you pick up the slack. | 21:37 |
parx | Oh, and let us know how it goes with classes starting : ) | 21:37 |
hyades | hehe | 21:38 |
parx | Sewar was a little ambitious with his number of classes... 40 credit hours, was it? :P | 21:39 |
Sewar | hehe, 20 or 40 is still too much :p | 21:39 |
parx | did you leave it at 20 or will you reduce? | 21:40 |
Sewar | Still 20, will see how first week goes, professors changes and stuff | 21:41 |
parx | Oh, just to reiterate, blog posts are for whatever you worked on that day NOT just what worked. What did you try? Why didn't it work? How can we replicate the error? | 21:43 |
Sewar | noted | 21:45 |
parx | keep doing it even if you don't get anywhere, kinda like this cat https://gs1.wac.edgecastcdn.net/8019B6/data.tumblr.com/tumblr_lx1m4y3Dp31r1lkdko1_250.gif | 21:47 |
tpb | <http://ln-s.net/-mMl> (at gs1.wac.edgecastcdn.net) | 21:47 |
parx | (carlfk will know where that's from) | 21:47 |
CarlFK | thats to cute! | 21:47 |
hyades | omg | 21:47 |
*** parx has quit IRC | 22:38 | |
*** parx1 has joined #timvideos | 22:38 | |
*** parx1 is now known as parx | 22:38 |
Generated by irclog2html.py 2.12.1 by Marius Gedminas - find it at mg.pov.lt!