|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Comment:
Changes (1)
View Page History
...
\[10:30:51 CDT(-0500)\] {color:black} <logiclord_> yura1 : can we discuss about epub reader ?{color} \[10:31:16 CDT(-0500)\] {color:black} <yura1> logiclord_: give me 10 minutes, thanks{color}
\[10:31:22 CDT(-0500)\] {color:black} <logiclord_> okay{color}
\[10:42:34 CDT(-0500)\] {color:black} <yura1> hey logiclord_{color}
\[10:49:36 CDT(-0500)\] {color:black} <logiclord_> Hi Yura{color}
\[10:49:56 CDT(-0500)\] {color:black} <yura1> hi, logiclord_, you had questions your wanted to discuss :) ?{color}
\[10:50:28 CDT(-0500)\] {color:black} <logiclord_> yura1: yes there are 2 major issue that I described in email{color}
\[10:52:03 CDT(-0500)\] {color:black} <yura1> logiclord_: right, so for the first one, i m not sure i understand the problem, could you elaborate ?{color}
\[10:52:04 CDT(-0500)\] {color:black} <logiclord_> I am converting images into data URI form for very chapter and height of unloaded image is not available (i.e. set as 0) but sometimes browsers tend to use cached images and .load handler is not triggered. I have tried to find my way by checking through the height and it works in all browser except Firefox. I need height of image so as to adjust it according to my preference of book size{color}
\[10:52:04 CDT(-0500)\] {color:black} <logiclord_> and divide chapters into pages. Is there any way I can detect whether images are loaded in the browser or not ?{color}
\[10:52:31 CDT(-0500)\] {color:black} <yura1> logiclord_: i dont think there's a way{color}
\[10:53:01 CDT(-0500)\] {color:black} <logiclord_> yura1: basically the issue is for data uri images browsers can't give us height/width not even with jquery until image is loaded{color}
\[10:53:15 CDT(-0500)\] {color:black} <logiclord_> so I placed a load event on last image{color}
\[10:53:35 CDT(-0500)\] {color:black} <yura1> logiclord_: why do you need the height and width ? to scale it somehow ?{color}
\[10:54:00 CDT(-0500)\] {color:black} <logiclord_> yura1 : yes I will be giving maxHeight and maxWidth for images as option{color}
\[10:54:22 CDT(-0500)\] {color:black} <logiclord_> because many images are around 800px to 1000px{color}
\[10:54:25 CDT(-0500)\] {color:black} <yura1> logiclord_: i think this can be done with just css ?{color}
\[10:55:14 CDT(-0500)\] {color:black} <logiclord_> yura1: yes it can be but I tried to scale height and width propotionally.. I am using css only in onload event handler{color}
\[10:55:25 CDT(-0500)\] {color:black} <logiclord_> jquery .height and .width methods{color}
\[10:55:46 CDT(-0500)\] {color:black} <logiclord_> but I am not able to read through them untill on load{color}
\[10:56:07 CDT(-0500)\] {color:black} <logiclord_> I tried a hack by checking for height = 0 and it works in all browser except firefox{color}
\[10:56:13 CDT(-0500)\] {color:black} <yura1> logiclord_: sorry i meant actually having a css file for your reader with set rules for images within the book{color}
\[10:56:44 CDT(-0500)\] {color:black} <yura1> logiclord_: also , i was trying to load the reader in the browser , do I just open index.html ?{color}
\[10:56:58 CDT(-0500)\] {color:black} <yura1> if so , i get an error - jQuery not defined{color}
\[10:57:04 CDT(-0500)\] {color:black} <logiclord_> yura1 : use a localhost{color}
\[10:57:14 CDT(-0500)\] {color:black} <logiclord_> I am using jquery hosted at google{color}
\[10:57:19 CDT(-0500)\] {color:black} <yura1> logiclord_: oh ok{color}
\[10:57:39 CDT(-0500)\] {color:black} <logiclord_> yura1: I am importing css stylesheets of each chapter as well in a div{color}
\[11:00:33 CDT(-0500)\] {color:black} <logiclord_> yura1: You can change ebook by editing line 6 in js/temp.js{color}
\[11:00:33 CDT(-0500)\] {color:black} <logiclord_> var zipFileName = 'epubs/carroll-alice-in-wonderland-illustrations.epub';{color}
\[11:02:33 CDT(-0500)\] {color:black} <logiclord_> up arrow for prev chapter, down arrow for next chapter, left-right for prev-nect page{color}
\[11:02:37 CDT(-0500)\] {color:black} <logiclord_> *next{color}
\[11:04:32 CDT(-0500)\] {color:black} <yura1> logiclord_: is there a reason you are using raw XMLHttpRequest instead of jQuery, since you already include it ?{color}
\[11:05:31 CDT(-0500)\] {color:black} <logiclord_> yura1: I read somewhere about jQuery.get being corrupt for zip file{color}
\[11:05:55 CDT(-0500)\] {color:black} <jhung> Justin_o: The package made it to Ibadan. Benedict got it this morning. :){color}
\[11:06:08 CDT(-0500)\] {color:black} <Justin_o> jhung: excellent{color}
\[11:06:22 CDT(-0500)\] {color:black} <Justin_o> jhung: everything inside okay?{color}
\[11:06:25 CDT(-0500)\] {color:black} <logiclord_> yura : following reader was facing this problem{color}
\[11:06:26 CDT(-0500)\] {color:black} <logiclord_> http://badassjs.com/post/704695450/booktorious-a-client-side-epub-reader-in-javascript{color}
\[11:06:29 CDT(-0500)\] {color:black} <jhung> Next time we'll DHL ourselves to Nigeria. Faster than taking regular airlines.{color}
\[11:06:54 CDT(-0500)\] {color:black} <logiclord_> they tried to encode entire zip to base64{color}
\[11:06:58 CDT(-0500)\] {color:black} <jhung> justin_o: Benedict didn't say otherwise. I'll forward you his email.{color}
\[11:07:00 CDT(-0500)\] {color:black} <logiclord_> and decode in js{color}
\[11:07:50 CDT(-0500)\] {color:black} <Justin_o> jhung: thanks.. i just checked the tracking.. the other one has left lagos but i guess it will take a bit longer to fly it to kano{color}
\[11:07:53 CDT(-0500)\] {color:black} <yura> logiclord_: right but how recent is this? surely, there were a lot of jquery releases after that ? you should probably try and see if it works now{color}
\[11:08:26 CDT(-0500)\] {color:black} <logiclord_> yura: Okay I will do some research and replace if it works{color}
\[11:08:56 CDT(-0500)\] {color:black} <yura> logiclord_: so regarding the images{color}
\[11:09:21 CDT(-0500)\] {color:black} <yura> i think what you are trying to do is to set max height and width for book images regarding of the css that they might have , right ?{color}
\[11:09:32 CDT(-0500)\] {color:black} <logiclord_> yura: yes{color}
\[11:09:41 CDT(-0500)\] {color:black} <logiclord_> due to 2 main reasons{color}
\[11:09:58 CDT(-0500)\] {color:black} <logiclord_> 1 to avoid image extending out of page length{color}
\[11:10:18 CDT(-0500)\] {color:black} <logiclord_> 2 fit in the reading div{color}
\[11:10:28 CDT(-0500)\] {color:black} <yura> logiclord_: so i think you would want to try creating your own css file (for your epub reader) , like a master one. It will have those rules for internal images defined, do you think it would work >{color}
\[11:10:30 CDT(-0500)\] {color:black} <yura> ?{color}
\[11:11:37 CDT(-0500)\] {color:black} <logiclord_> yura : no I doubt.. because I tried to add css rules in current css files{color}
\[11:12:29 CDT(-0500)\] {color:black} <logiclord_> yura .. It might be due to the fact that chapter stylesheet interfere with css file{color}
\[11:12:48 CDT(-0500)\] {color:black} <yura> hmm, right, it gets loaded after the main one right ?{color}
\[11:12:59 CDT(-0500)\] {color:black} <logiclord_> yes{color}
\[11:13:12 CDT(-0500)\] {color:black} <logiclord_> yura : even with stylesheet how will I maintain aspect ratio of images ?{color}
\[11:14:45 CDT(-0500)\] {color:black} <yura> logiclord_: i think it is possible let me see if i can find some reasources{color}
\[11:15:14 CDT(-0500)\] {color:black} <yura> http://www.briangrinstead.com/blog/keep-aspect-ratio-with-html-and-css{color}
\[11:15:41 CDT(-0500)\] {color:black} <yura> http://stackoverflow.com/questions/757782/how-to-preserve-aspect-ratio-when-scaling-image-using-one-css-dimension-in-ie6{color}
\[11:16:23 CDT(-0500)\] {color:black} <yura> i think you can do it with some smart css, i remember i could do it for websites on iphone a couple of years ago{color}
\[11:17:24 CDT(-0500)\] {color:black} <Justin_o> jhung: i'm going to test out the install script update in Decapod 10.04 now too..{color}
\[11:18:52 CDT(-0500)\] {color:black} <logiclord_> yura : Yes it seems to work.. If it works instantly (i.e. no onload lag) then 1st issue will be solved{color}
\[11:19:01 CDT(-0500)\] {color:black} <logiclord_> I will try out and update about that{color}
\[11:19:20 CDT(-0500)\] {color:black} <logiclord_> yura: about 2nd point in email ?{color}
\[11:19:52 CDT(-0500)\] {color:black} <jhung> ok justin_o{color}
\[11:20:35 CDT(-0500)\] {color:black} <yura> logiclord_: right so once you structure your code into components, you will probably have the events belonging to some of them which means that the event handlers should probably be the public methods of those components{color}
\[11:22:25 CDT(-0500)\] {color:black} <logiclord_> yura: even event handlers of internal dom elements ?{color}
\[11:24:02 CDT(-0500)\] {color:black} <yura> logiclord_: oh that, so the idea is to have as much configurable as possible. So when you attach a listener for an event, there should be an option to override it. Which means it should be configurable through component options. So yes i think it makes sense to have them internalized to the components that own the DOM{color}
\[11:27:00 CDT(-0500)\] {color:black} <logiclord_> yura : I thought each component will be provided with a selector and using dom binder it can update its part of scope{color}
\[11:27:09 CDT(-0500)\] {color:black} <logiclord_> e.g. bookmark{color}
\[11:27:48 CDT(-0500)\] {color:black} <yura> logiclord_: not sure i understand{color}
\[11:28:35 CDT(-0500)\] {color:black} <logiclord_> yura: each component dealing with a UI related element suppose bookmark{color}
\[11:28:48 CDT(-0500)\] {color:black} <logiclord_> will be passed a selector of bookmark container{color}
\[11:28:50 CDT(-0500)\] {color:black} <anastasiac> michelled, I have a fix for the 'skip tags' link in a branch, ready for review: https://github.com/acheetham/OER-Commons/tree/604-skip-tags{color}
\[11:29:14 CDT(-0500)\] {color:black} <michelled> thx anastasiac{color}
\[11:29:18 CDT(-0500)\] {color:black} <logiclord_> yura: and it can then update bookmarks in it using other components like navigator{color}
\[11:30:57 CDT(-0500)\] {color:black} <yura> logiclord_: well right, so if you want to attach event handlers to its internal dom elements you should do it within the component, and probably have it as a method of the component, not an anonymous function{color}
\[11:31:21 CDT(-0500)\] {color:black} <logiclord_> yura: got it{color}
\[11:31:51 CDT(-0500)\] {color:black} <logiclord_> one last thing ... I was browsing through the documentation and many APIs are in sneak peak state{color}
\[11:31:55 CDT(-0500)\] {color:black} <logiclord_> should I use them ?{color}
\[11:32:16 CDT(-0500)\] {color:black} <yura> logiclord_: once you start converting things into components, ill try to add as many comments as i can.{color}
\[11:32:21 CDT(-0500)\] {color:black} <yura> logiclord_: yes definitely :){color}
\[11:33:01 CDT(-0500)\] {color:black} <logiclord_> yura: actually I read somehere "sneak peak status. APIs may change which may break the code" :-/{color}
\[11:33:21 CDT(-0500)\] {color:black} <yura> logiclord_: one more tip, for the latest most update examples of how things can be used, also check out the framework tests, they seem to have the most up to date examples.{color}
\[11:33:35 CDT(-0500)\] {color:black} <yura> logiclord_: yes, i dont think it will happen soon, or be that dramatic{color}
\[11:33:58 CDT(-0500)\] {color:black} <logiclord_> yura : could you point me to the url ?{color}
\[11:34:02 CDT(-0500)\] {color:black} <yura> sure{color}
\[11:34:42 CDT(-0500)\] {color:black} <yura> so here are examples of how to use some of the inversion of control features - https://github.com/fluid-project/infusion/blob/master/src/webapp/tests/framework-tests/core/js/FluidIoCTests.js{color}
\[11:36:14 CDT(-0500)\] {color:black} <logiclord_> yura: I might take a off tomorrow.. but I will complete milestone one working weekend if required{color}
\[11:36:56 CDT(-0500)\] {color:black} <yura> logiclord_: let me know if you want me to look at particular things in the code{color}
\[11:38:05 CDT(-0500)\] {color:black} <logiclord_> yura: did you noticed that in current version of epub reader.. when you press previous page button (being at first page of a chapter){color}
\[11:38:18 CDT(-0500)\] {color:black} <logiclord_> you will go to first page of previosu chapter{color}
\[11:38:48 CDT(-0500)\] {color:black} <yura> logiclord_: oh interseting{color}
\[11:38:57 CDT(-0500)\] {color:black} <logiclord_> I was not able to figre out .. how to calculate last page directly{color}
\[11:39:13 CDT(-0500)\] {color:black} <logiclord_> within the chapter it works fine{color}
\[11:40:10 CDT(-0500)\] {color:black} <yura> logiclord_: hmm{color}
\[11:41:18 CDT(-0500)\] {color:black} <logiclord_> yura: thanks for time :){color}
\[11:42:38 CDT(-0500)\] {color:black} <yura> logiclord_: ya we ll get to it , i think, also , you can think of issues like that in terms of tests too , see if you can start writing any already for cases like that{color}
\[11:43:22 CDT(-0500)\] {color:black} <logiclord_> yura: I will keep a note of such issues{color}
\[11:43:29 CDT(-0500)\] {color:black} <yura> logiclord_: cool{color}
\[12:03:00 CDT(-0500)\] {color:black} <anastasiac> michelled, I've got a fix for 605 in a branch, ready for review: https://github.com/acheetham/OER-Commons/tree/605-view-item-link{color}
\[12:03:11 CDT(-0500)\] {color:black} <michelled> thx anastasiac{color}
\[12:30:34 CDT(-0500)\] {color:black} <michelled> anastasiac: I noticed that you modified the materials index and the front page to add the skip over tags link. I searched the repo and it looks like you should also modify the 'green' and green-browse pages. maybe also the item-tags-portlet page. I haven't actually tried to view any of those, so you'll probably want to figure out whether they are even used at this point{color}
\[12:31:28 CDT(-0500)\] {color:black} <anastasiac> michelled, yes, I noticed those, but couldn't figure out where they were being used. I'll check again, and maybe modify them anyway (and just assume they'll work the same){color}
\[12:32:20 CDT(-0500)\] {color:black} <michelled> anastasiac: I think if they aren't used we shouldn't fix them - ask Andrey on the ticket whether or not they are used{color}
\[12:32:37 CDT(-0500)\] {color:black} <michelled> we can suggest refactoring or removing them if they aren't{color}
\[12:35:20 CDT(-0500)\] {color:black} <michelled> anastasiac: I just looked at your 605 branch. I totally agree that the item names in each search result wouldn't be an h1 but I'm wondering if they would still be a heading{color}
\[12:36:03 CDT(-0500)\] {color:black} <anastasiac> michelled, the main reason I remove the heading was because I think that contributes to part of the confusion for screen reader users{color}
\[12:36:27 CDT(-0500)\] {color:black} <anastasiac> the screen reader appends "heading level 2" to the link text{color}
\[12:36:30 CDT(-0500)\] {color:black} <anastasiac> for both links{color}
\[12:38:00 CDT(-0500)\] {color:black} <michelled> I suppose the second link may not semantically be a heading. do you agree with me that the title of the resource is semantically a heading?{color}
\[12:39:28 CDT(-0500)\] {color:black} <anastasiac> michelled, I'm not entirely sure about that one. I might be convinced, but I'm not sure. Right now, everything on the page is h1, which kind of makes it meaningless{color}
\[12:40:17 CDT(-0500)\] {color:black} <michelled> are you suggesting we address it when we deal with FLOE-29?{color}
\[12:51:44 CDT(-0500)\] {color:black} <asteig> Morning Justin_o, jhung. :){color}
\[12:52:12 CDT(-0500)\] {color:black} <Justin_o> asteig: hello.. how are things going?{color}
\[12:53:13 CDT(-0500)\] {color:black} <asteig> Justin_o: Good, still on track. Should be making a commit shortly. :){color}
\[12:53:25 CDT(-0500)\] {color:black} <asteig> Justin_o: Finished the UI and started working on collecting the data.{color}
\[12:53:40 CDT(-0500)\] {color:black} <asteig> Justin_o: UI meaning the markup, not all the JS.{color}
\[12:55:39 CDT(-0500)\] {color:black} <Justin_o> asteig: cool.. and that will all be in your coming commit?{color}
\[12:55:54 CDT(-0500)\] {color:black} <asteig> Justin_o: Yep.{color}
\[12:56:05 CDT(-0500)\] {color:black} <asteig> Justin_o: Just want to give it a look over and clean it up a tad first.{color}
\[12:56:44 CDT(-0500)\] {color:black} <jhung> asteig, excellent! Looking forward in seeing it.{color}
\[12:57:39 CDT(-0500)\] {color:black} <Justin_o> asteig: great thanks.. oh a couple things about the fluid studios post before i forget.. can you make sure to update it with your progress and also maybe change the name to include more info about the project.. we have a few more gsoc projects going on here and I think others will start posting there as well.. so even just including html5 image editor or something like that in the title would be good{color}
\[12:58:12 CDT(-0500)\] {color:black} <asteig> Justin_o: Yeah, definitely. I'll log in and do that right now.{color}
\[12:59:46 CDT(-0500)\] {color:black} <Justin_o> asteig: thanks for that{color}
\[13:17:29 CDT(-0500)\] {color:black} <Justin_o> asteig: do you have any questions for jhung and I?{color}
\[13:20:35 CDT(-0500)\] {color:black} <asteig> Justin_o: Nope, I think I'm good for the moment. :){color}
\[13:21:22 CDT(-0500)\] {color:black} <Justin_o> asteig: great..glad things are moving along well{color}
\[13:31:59 CDT(-0500)\] {color:black} <jhung> asteig: sorry asteig, I have contractors vying for my attention at the moment.{color}
\[13:32:33 CDT(-0500)\] {color:black} <jhung> asteig: let us know when the code is up so we can take a look. But progress looks good.{color}
\[13:34:10 CDT(-0500)\] {color:black} <asteig> jhung: Will do. I'll send you an email. :){color}
\[14:29:30 CDT(-0500)\] {color:black} <Justin_o> jhung: did we decide how we want to return the tiff export to users? zip?{color}
\[14:43:18 CDT(-0500)\] {color:black} <jhung> Yeah. Zip.{color}
\[14:43:33 CDT(-0500)\] {color:black} <jhung> Puts into question space concerns though. Tiffs can get really big justin_o.{color}
\[14:43:50 CDT(-0500)\] {color:black} <Justin_o> jhung: hmm.. true{color}
\[14:43:57 CDT(-0500)\] {color:black} <jhung> Perhaps we should think of a strategy for estimating space?{color}
\[14:44:16 CDT(-0500)\] {color:black} <Justin_o> lets say 70MB a page.. and 1000 page book..{color}
\[14:44:20 CDT(-0500)\] {color:black} <Justin_o> that'd be pretty huge{color}
\[14:44:47 CDT(-0500)\] {color:black} <jhung> justin_o: yup.{color}
\[14:44:53 CDT(-0500)\] {color:black} <Justin_o> jhung: i guess.. not sure yet how to calculate it.. but we can look into it{color}
\[14:45:19 CDT(-0500)\] {color:black} <Justin_o> in terms of what the UI has access to though.. it may just be a guess{color}
\[14:46:01 CDT(-0500)\] {color:black} <jhung> justin_o: The problem is, in creating the archive, we essentially double the amount of disk space consumption. So maybe we can return a link to the directory? But the directory isn't stable, so they'll need to move the files out before refreshing the browser...{color}
\[14:46:33 CDT(-0500)\] {color:black} <Justin_o> jhung: :({color}
\[14:46:40 CDT(-0500)\] {color:black} <Justin_o> hopefully not double{color}
\[14:47:08 CDT(-0500)\] {color:black} <Justin_o> jhung: but point taken.. and considering these things are already there in some other format on the machine there will be at least 3 copies and two of them in tiff format{color}
\[14:48:02 CDT(-0500)\] {color:black} <colinclark> I guess the problem is that, by nature of being a client-driven application, we have a kind of abstraction over the file system? The user can't really tell us where they want us to drop of their files to, in terms of the local file system?{color}
\[14:48:16 CDT(-0500)\] {color:black} <Justin_o> jhung: if we were to give them a link to the directory that would start to betray the possible client server separation{color}
\[14:48:27 CDT(-0500)\] {color:black} <Justin_o> meaning it would require you to be on the same machine{color}
\[14:48:39 CDT(-0500)\] {color:black} <colinclark> So the only user-tangible option--especially with the potential of client/server separation--is to pack them up a zip file and deliver it back via the browser?{color}
\[14:48:47 CDT(-0500)\] {color:black} <colinclark> Am I right, Justin_o?{color}
\[14:48:54 CDT(-0500)\] {color:black} <Justin_o> colinclark: yep.. that's what i was thinking{color}
\[14:49:07 CDT(-0500)\] {color:black} <colinclark> And remind me again...{color}
\[14:49:27 CDT(-0500)\] {color:black} <colinclark> the new Web File System API provides a sandboxed space on the file system?{color}
\[14:49:35 CDT(-0500)\] {color:black} <colinclark> in other words, it's opaque to the user{color}
\[14:49:38 CDT(-0500)\] {color:black} <colinclark> is that correct?{color}
\[14:50:24 CDT(-0500)\] {color:black} <Justin_o> colinclark: as far as i know yes...{color}
\[14:50:29 CDT(-0500)\] {color:black} <colinclark> yeah{color}
\[14:50:49 CDT(-0500)\] {color:black} <colinclark> I can't think of any way around this, off the top of my head{color}
\[14:50:58 CDT(-0500)\] {color:black} <colinclark> we might just have to fall back on "storage is cheap"{color}
\[14:51:07 CDT(-0500)\] {color:black} <colinclark> even though it's still not as cheap as it used to be{color}
\[14:53:13 CDT(-0500)\] {color:black} <Justin_o> colinclark: yep.. not sure what we could do..{color}
\[14:54:42 CDT(-0500)\] {color:black} <colinclark> I guess at some point after you've bundled up the images a zip and sent it off to the client, you can safely delete one or the other?{color}
\[14:54:47 CDT(-0500)\] {color:black} <colinclark> either the zip file or the original files?{color}
\[14:55:17 CDT(-0500)\] {color:black} <colinclark> It sounds like we're going to have, realistically, potentially four copies of the book on the hard drive at some point in the workflow{color}
\[14:55:35 CDT(-0500)\] {color:black} <colinclark> 1. The original images, say, scanned on a scanner or imported from another program{color}
\[14:56:08 CDT(-0500)\] {color:black} <colinclark> 2. The "Book" in terms of the data structure and persistence associated with each image once it's been imported into Decapod{color}
\[14:56:22 CDT(-0500)\] {color:black} <colinclark> 3. The images in a zip file, after it's been sent to the user{color}
\[14:56:28 CDT(-0500)\] {color:black} <colinclark> 4. The unzipped images{color}
\[14:56:50 CDT(-0500)\] {color:black} <colinclark> Justin_o: Am I correct?{color}
\[15:01:01 CDT(-0500)\] {color:black} <Justin_o> colinclark: potentially more.. so there are the convert un zipped images too{color}
\[15:01:13 CDT(-0500)\] {color:black} <Justin_o> converted, unzipped{color}
\[15:04:16 CDT(-0500)\] {color:black} <Justin_o> colinclark, jhung: have to run now.. maybe we can pick this conversation up again later{color}
\[15:04:27 CDT(-0500)\] {color:black} <colinclark> yup, see you{color}
\[15:59:13 CDT(-0500)\] {color:black} <travis_84> hello Bosmon, michelled, and colinclark{color}
\[16:06:16 CDT(-0500)\] {color:black} <travis_84> just a quick update. I have basic "getUserMedia" feature detection, and working 'video' playback in opera accessing the camera.{color}
\[16:07:45 CDT(-0500)\] {color:black} <travis_84> Audio is still unsupported so I am working on a fallback so I can continue{color}
\[16:12:41 CDT(-0500)\] {color:black} <Bosmon> Hey there travis_84{color}
\[16:12:43 CDT(-0500)\] {color:black} <Bosmon> Great stuff{color}
\[16:13:07 CDT(-0500)\] {color:black} <Bosmon> Glad you've got to pounding the keyboard :){color}
\[16:15:22 CDT(-0500)\] {color:black} <travis_84> thanks, Chrome is making a fuss. being vanilla to the this depth of a JS project is slowing me down a little ; ){color}
\[16:15:36 CDT(-0500)\] {color:black} <Bosmon> What kind of fuss?{color}
\[16:17:00 CDT(-0500)\] {color:black} <travis_84> throwing an error{color}
\[16:17:07 CDT(-0500)\] {color:black} <travis_84> "Uncaught Error: TYPE_MISMATCH_ERR: DOM Exception 17 "{color}
\[16:17:12 CDT(-0500)\] {color:black} <Bosmon> Oh yes, those{color}
\[16:17:15 CDT(-0500)\] {color:black} <Bosmon> Always nasty{color}
\[16:17:23 CDT(-0500)\] {color:black} <Bosmon> You can probably only locate it by bisection{color}
\[16:17:30 CDT(-0500)\] {color:black} <Bosmon> Unless you've already figured out which statement causes the error?{color}
\[16:18:31 CDT(-0500)\] {color:black} <travis_84> dev tools is saying "navigator.getUserMedia('video', successCallback, errorCallback);{color}
\[16:20:16 CDT(-0500)\] {color:black} <Bosmon> Ok{color}
\[16:20:20 CDT(-0500)\] {color:black} <Bosmon> The nasty part is taken care of then :){color}
\[16:21:18 CDT(-0500)\] {color:black} <travis_84> which is I think chrome doesn't like the 'video' being called as an object{color}
\[16:21:28 CDT(-0500)\] {color:black} <Bosmon> Looks like this API is incredibly unstable still{color}
\[16:21:34 CDT(-0500)\] {color:black} <Bosmon> http://stackoverflow.com/questions/5845306/how-do-i-access-navigator-getusermedia{color}
\[16:21:37 CDT(-0500)\] {color:black} <Bosmon> Don't worry too much about it{color}
\[16:21:48 CDT(-0500)\] {color:black} <Bosmon> Much more important to get anything at all working now, even if it is just in one browser{color}
\[16:23:11 CDT(-0500)\] {color:black} <travis_84> ya, soon though{color}
\[16:24:24 CDT(-0500)\] {color:black} <Bosmon> It would be helpful for us at least, in the longer term, if you thought about packaging your work as Fluid components if you can{color}
\[16:24:30 CDT(-0500)\] {color:black} <Bosmon> Since this should increase their reuse value{color}
\[16:24:56 CDT(-0500)\] {color:black} <Bosmon> I guess you are not yet looking at the UI implementation part{color}