[09:56:39 CDT(-0500)] <colinclark> Justin_o: You mentioned that you recently configured your new laptop to build Infusion with Ant...
[09:56:54 CDT(-0500)] <colinclark> were there any tricks or details you encountered, or can I just follow the instructions in the wiki?
[09:57:13 CDT(-0500)] <Justin_o> colinclark: well actually i didn't finish getting it all set up.. there was a problem with maven
[09:57:33 CDT(-0500)] <colinclark> Okay
[09:57:38 CDT(-0500)] <Justin_o> i had been following all the steps up to that.. it could be that mac os ships with a different version of maven than we require
[09:57:52 CDT(-0500)] <colinclark> This is confirming to me that this stuff needs to be smashed asap
[09:58:19 CDT(-0500)] <colinclark> Perhaps I'll start by removing support for building the .war file?
[09:58:27 CDT(-0500)] <colinclark> We've wanted to remove it for ages
[09:58:40 CDT(-0500)] <colinclark> As the King, do you think it's a reasonable thing to ditch for 1.5?
[09:58:50 CDT(-0500)] <colinclark> I'll ditch the whole thing for a Node.js build system
[09:58:54 CDT(-0500)] <colinclark> but you have to start somewhere
[10:00:11 CDT(-0500)] <Justin_o> colinclark: sounds reasonable.. is it possible to split off the war generation into a separate utility that we can just host in a separate git repo or something
[10:00:35 CDT(-0500)] <colinclark> Justin_o: I'd argue that it's more trouble than it's worth for a feature no one has, to the best of my knowledge, ever used
[10:00:36 CDT(-0500)] <Justin_o> so that we can just have some tool to convert our package into a war if anyone wants to use it
[10:00:53 CDT(-0500)] <Justin_o> colinclark: if that true, i agree
[10:01:05 CDT(-0500)] <Justin_o> no point to spend a lot of time on something that really isn't any value anyways
[10:01:48 CDT(-0500)] <colinclark> I guess there might still be one use for this war file, absurdly
[10:01:54 CDT(-0500)] <colinclark> perhaps someone can verify
[10:02:11 CDT(-0500)] <colinclark> I think we might host our daily build site inside a Tomcat instance?
[10:02:20 CDT(-0500)] <colinclark> hopefully that's long gone
[10:02:30 CDT(-0500)] <Justin_o> anastasiac: do you know if this is still the case ^
[10:03:50 CDT(-0500)] <anastasiac> Justin_o, no, I don't know if that's still the case
[10:04:46 CDT(-0500)] <colinclark> I suspect Continuum could tell us
[10:05:44 CDT(-0500)] <Justin_o> colinclark: i don't remember what the pw is for that.. i remember we had to change it a bunch of times a while ago… don't remember what it got put to though
[10:05:54 CDT(-0500)] <colinclark> lol
[10:06:00 CDT(-0500)] <colinclark> Yes, I remember this whole fiasco
[10:06:06 CDT(-0500)] <colinclark> anastasiac: Do you know, by chance?
[10:06:23 CDT(-0500)] <colinclark> Otherwise, let's distract and annoy avtar when he gets in
[10:06:41 CDT(-0500)] <Justin_o> colinclark: sounds like a plan
[10:06:43 CDT(-0500)] <anastasiac> password for which site? continuum?
[10:06:46 CDT(-0500)] <anastasiac> hm
[10:06:49 CDT(-0500)] <colinclark> yes, continuum
[10:07:20 CDT(-0500)] <Justin_o> fluid-everyone: opinions… should an onReady event fire after the component has initialized.. or after all of it's subcomponents have?
[10:07:58 CDT(-0500)] <colinclark> The name implies, to me, that the component is ready to go, ready to be used
[10:08:46 CDT(-0500)] <Justin_o> colinclark: well i guess that's the thing.. the component itself is ready, but maybe not all the parts it depends on.. if that makes sense
[10:09:03 CDT(-0500)] <anastasiac> I have my own password, but I don't recall the 'group' password. I tried what I thought it might be, and it doesn't work
[10:09:13 CDT(-0500)] <Justin_o> colinclark: so i think it can be used in IoC, but it's subcomponents may not yet be accessible
[10:09:37 CDT(-0500)] <colinclark> anastasiac: What does your own account tell you about the nature of the Infusion builds?
[10:09:51 CDT(-0500)] <colinclark> Justin_o: That's interesting
[10:10:08 CDT(-0500)] <colinclark> Since I imagine many components aren't able to do their job without help from their subcomponents
[10:10:30 CDT(-0500)] <colinclark> onReallyReady
[10:10:38 CDT(-0500)] <Justin_o> colinclark:
[10:11:34 CDT(-0500)] <colinclark> I don't have an SSH key registered for build.fluidproject.org (which is crazy), but if someone else does perhaps it would be easy and quick just to shell into the box and have a look around
[10:11:36 CDT(-0500)] <Justin_o> colinclark: this is one of the reasons why i wish there was an automatic afterInit event
[10:12:01 CDT(-0500)] <colinclark> afterInit would fire when the component had finished initializing, but prior to its subcomponents?
[10:12:17 CDT(-0500)] <colinclark> and onReady would be onReallyReady, is that what you're thinking?
[10:12:36 CDT(-0500)] <Justin_o> colinclark: yes.. something like that
[10:12:42 CDT(-0500)] <colinclark> it seems fairly reasonable to me
[10:13:19 CDT(-0500)] <anastasiac> the infusion build has two build definitions, a maven clean+install using pom.xml and an ant build using build-scripts/build.xml
[10:13:28 CDT(-0500)] <Justin_o> colinclark: guess i'll need to chat with bosmon about it..
[10:13:49 CDT(-0500)] <anastasiac> the ant build is the default
[10:16:36 CDT(-0500)] <colinclark> Justin_o: I would, yes
[10:16:39 CDT(-0500)] <colinclark> thanks, anastasiac
[10:23:55 CDT(-0500)] <colinclark> hey michelled, can you do a bit of sanity checking for me?
[10:24:12 CDT(-0500)] <michelled> sure
[10:24:15 CDT(-0500)] <colinclark> Run an Infusion build on your laptop--just make sure it works fine for you?
[10:25:13 CDT(-0500)] <michelled> ok, it's running colinclark
[10:25:17 CDT(-0500)] <colinclark> excellent
[10:25:26 CDT(-0500)] <colinclark> So I'm getting an error related to eval() in Rhino
[10:25:33 CDT(-0500)] <colinclark> Which I remember at least vaguely
[10:26:03 CDT(-0500)] <colinclark> I believe it involved us upgrading to a newer version of Rhino, which presumably is the one that is distributed directly with Infusion
[10:26:20 CDT(-0500)] <michelled> yeah, that sounds familiar
[10:26:22 CDT(-0500)] <colinclark> Now, I also vaguely remember that maybe another version of Rhino was being sourced from somewhere else
[10:26:30 CDT(-0500)] <colinclark> does any of this ring bells?
[10:26:51 CDT(-0500)] <michelled> yes, it does
[10:27:19 CDT(-0500)] <michelled> and we were either using a command line flag to use the correct rhino version or setting an environment variable
[10:27:38 CDT(-0500)] <michelled> since mine just completed successfully, I must have set a variable somewhere
[10:28:11 CDT(-0500)] <colinclark> aha, excellent
[10:28:33 CDT(-0500)] <colinclark> yes, I see that flag in some of the examples!
[10:28:36 CDT(-0500)] <colinclark> thanks so much!
[10:28:56 CDT(-0500)] <colinclark> that did it
[10:29:28 CDT(-0500)] <michelled> np - glad it worked
[10:29:47 CDT(-0500)] <colinclark> Justin_o: I'm thinking that, when we upgrade to a Node.js-based build, we can probably toss all of that complexity in the Builder around caching...
[10:30:11 CDT(-0500)] <colinclark> I have a feeling that running Uglify.js to minify our stuff in Node will be nearly instantaneous
[10:30:33 CDT(-0500)] <michelled> that would be really wonderful
[10:30:48 CDT(-0500)] <Justin_o> colinclark: that would be awesome
[10:31:33 CDT(-0500)] <boyan> colinclark: I won't be able to come to the architecture call, just sent an email with status and priority suggestions
[10:31:46 CDT(-0500)] <colinclark> boyan: Sorry to hear it. Thanks for the email
[10:33:53 CDT(-0500)] <boyan> colinclark: you're welcome, sorry to miss the call as well (and sorry for the late notice)
[10:34:00 CDT(-0500)] <colinclark> no problem at all
[10:34:02 CDT(-0500)] <colinclark> have a great rest of the day
[10:34:14 CDT(-0500)] <boyan> thanks!
[10:35:28 CDT(-0500)] <colinclark> hey fluid-everyone, it's lonely here at standup
[10:47:50 CDT(-0500)] <Justin_o> colinclark: we had a bit if technical difficulty.. the machine was missing a power cord
[10:48:00 CDT(-0500)] <colinclark> no worries
[10:48:06 CDT(-0500)] <colinclark> that's bizarre
[10:48:33 CDT(-0500)] <colinclark> Justin_o: I just noticed a new issue type in JIRA...
[10:48:34 CDT(-0500)] <colinclark> "epic"
[10:48:45 CDT(-0500)] <colinclark> Do you think this issue I'm working on counts as being "epic?"
[10:49:02 CDT(-0500)] <Justin_o> colinclark: it could
[10:49:46 CDT(-0500)] <Justin_o> colinclark: officially.. this is what an epic issue refers to "A big user story that needs to be broken down."
[10:50:30 CDT(-0500)] <colinclark> wow
[10:50:31 CDT(-0500)] <colinclark> this must be some kind of agile plugin for JIRA?
[10:50:33 CDT(-0500)] <colinclark> or just a built-in feature?
[10:50:58 CDT(-0500)] <Justin_o> colinclark: not sure where it came from
[10:55:49 CDT(-0500)] <colinclark> michelled: How is it going with mediaelement.js?
[10:56:11 CDT(-0500)] <colinclark> And I'm curious to know how the WebKit implementation of <track> are seeming to you
[11:00:15 CDT(-0500)] <michelled> colinclark: I haven't used media element yet - I was trying to get the base working in webkit. I can't seem to hide the tracks although according to the spec there is mode that I should be able to set to hidden
[11:00:30 CDT(-0500)] <colinclark> ah, that's really great--so you're starting without the polyfill
[11:00:40 CDT(-0500)] <colinclark> hide the tracks how?
[11:01:25 CDT(-0500)] <michelled> colinclark: when the user turns captions off. http://dev.w3.org/html5/spec/single-page.html#text-track-hidden
[11:04:07 CDT(-0500)] <michelled> colinclark: there's probably just a bug in my sketchy code - I'm finally forced to use Chrome dev tools
[11:04:20 CDT(-0500)] <colinclark> Yeah
[11:04:26 CDT(-0500)] <colinclark> Sadly, you'll find that they're pretty good
[11:04:31 CDT(-0500)] <colinclark> all the kids these days love them
[11:07:25 CDT(-0500)] <colinclark> yura: kasper is going to come liberate us from this connect layout shortly
[11:08:50 CDT(-0500)] <Justin_o> colinclark, michelled: have you tried the new ones in Safari 6? They are the same style as in Xcode.. i'm not sure i like it just yet
[11:08:58 CDT(-0500)] <colinclark> oh yes
[11:09:07 CDT(-0500)] <colinclark> I was doing some Flocking debugging in Safari the other day
[11:09:12 CDT(-0500)] <colinclark> I found them disturbing
[11:09:23 CDT(-0500)] <colinclark> but I guess you just have to spend some time with them to know if they're any good
[11:09:33 CDT(-0500)] <kasper> colinclark: upgraded you to be a uber super powered adobe connect user
[11:09:34 CDT(-0500)] <colinclark> when you're just quickly trying to debug something and the UI is new, it can be challenging
[11:09:39 CDT(-0500)] <colinclark> kasper: omg omg!
[11:09:51 CDT(-0500)] <Justin_o> colinclark: probably.. i guess it's a good idea to have them consistent with their other debugger
[11:10:31 CDT(-0500)] <colinclark> I haven't used Xcode in ages
[11:10:45 CDT(-0500)] <colinclark> I remember Project Builder on NeXTSTEP was really cool
[11:10:58 CDT(-0500)] <colinclark> with its GUI fronted for GDB
[11:11:13 CDT(-0500)] <colinclark> I wouldn't be surprised if, somewhere down there, it's still the same code
[11:22:14 CDT(-0500)] <michelled> colinclark: success! I have it working nicely in Chrome and throwing an error in FF - now to swap in media element
[11:22:20 CDT(-0500)] <colinclark> yay!
[11:45:54 CDT(-0500)] <Justin_o> Bosmon: thanks for looking at the FLUID-4739, I'm mid-way through some other work at the moment so haven't yet had a chance to try out your branch
[11:52:38 CDT(-0500)] <Bosmon> Hi Justin_o
[11:54:16 CDT(-0500)] <Justin_o> Bosmon: hello
[11:54:58 CDT(-0500)] <Justin_o> Bosmon: I have a bit of a question about how some IoC things work.. i guess i'll start by telling you what the problem i'm trying to solve is
[11:55:18 CDT(-0500)] <Justin_o> Bosmon: so basically i have this button.. it should only be enabled when a couple of conditions are satisfied..
[11:55:23 CDT(-0500)] <Bosmon> Cool, go ahead
[11:55:28 CDT(-0500)] <Justin_o> no errors, and files added to the queue
[11:55:47 CDT(-0500)] <Justin_o> so the conditions are satisfied by two vary different pieces of code..
[11:56:07 CDT(-0500)] <Justin_o> one of them is at the top level component.. the other is in a subcomponent of a sibling tree..
[11:56:14 CDT(-0500)] <Justin_o> so i wanted to communicate via events
[11:56:16 CDT(-0500)] <Bosmon> Yes
[11:57:09 CDT(-0500)] <Justin_o> the one from the parent works fine, but I can't seem to get the event wired up from the other subcomponent
[11:57:15 CDT(-0500)] <Bosmon> I see
[11:57:16 CDT(-0500)] <Justin_o> my demands never resolve
[11:57:36 CDT(-0500)] <Bosmon> Probably best to steer clear of demands for the time being : P
[11:57:41 CDT(-0500)] <Bosmon> Show me what you have written....
[11:57:56 CDT(-0500)] <Justin_o> Bosmon: hmm.. that might be tricky
[11:58:21 CDT(-0500)] <Justin_o> i guess i'll show you the old code for now.. i have a bunch of code in progress but it's not ready to commit just yet
[11:59:14 CDT(-0500)] <Justin_o> Bosmon: so we can start here https://bitbucket.org/jobara/decapod-0.6-ui-iteration5/src/326f955f143b/components/exporter/js/pdfExporter.js
[11:59:59 CDT(-0500)] <Justin_o> this isn't the top most component, but it is the first common ancestor of the two subcomponents in question
[12:00:14 CDT(-0500)] <Bosmon> And which are they?
[12:00:20 CDT(-0500)] <Justin_o> Bosmon: comming up
[12:00:26 CDT(-0500)] <Justin_o> Bosmon: here's the next file https://bitbucket.org/jobara/decapod-0.6-ui-iteration5/src/326f955f143b/components/exporter/js/exportType.js
[12:00:35 CDT(-0500)] <Justin_o> that contains all the subcomponents
[12:01:18 CDT(-0500)] <Justin_o> Bosmon: in pdfExporter.js there are two subcomponents.. exportControls and exportOptions
[12:01:28 CDT(-0500)] <Justin_o> you can see these in exportType.js
[12:01:51 CDT(-0500)] <Bosmon> You seem to have exportPoller implemented twice...
[12:02:46 CDT(-0500)] <Justin_o> now these components have the relavents subcompoents.. so i want decapod.outputSettings from decapod.pdfExportOptions to fire an event that is listened to by a function in decapod.exportControls.trigger, which is created by the renderer in decapod.exportControls
[12:03:04 CDT(-0500)] <Justin_o> Bosmon: you're so fast.. yes.. i had missed that in some previous refactoring i have it fixed in my local changes
[12:03:17 CDT(-0500)] <Justin_o> I removed it from pdfExporter.js
[12:03:59 CDT(-0500)] <Bosmon> So, I don't see any relevant demands block that you have tried?
[12:04:17 CDT(-0500)] <Justin_o> Bosmon: sorry… didn't notice the time.. i have to run out for a bit, but will be back for the UIO talk.. will catch up then
[12:04:34 CDT(-0500)] <Bosmon> ok, see you later
[12:05:10 CDT(-0500)] <Justin_o> Bosmon: yes.. sorry that's in my local code too.. basically in the demands for pdfExporter.js i was trying to set a demand for the trigger component in the context ["decapod.pdfExporter", "decapod.exportControls", "decapod.outputSettings"] but that would never resolve
[12:05:29 CDT(-0500)] <Justin_o> if i removed the outputSettings context it would, but of course wouldn't work properly
[12:05:36 CDT(-0500)] <Justin_o> be back in a bit
[12:05:45 CDT(-0500)] <colinclark> hey Justin_o Do you think I'll be okay to attend the UIO community meeting today remotely, now that we have that microphone
[12:05:45 CDT(-0500)] <colinclark> ?
[12:06:00 CDT(-0500)] <Bosmon> The parent component doesn't seem to have a subcomponent matching outputSettings....
[12:06:08 CDT(-0500)] <Justin_o> colinclark: hopefully, we have a lot of remote attendants this time
[12:06:23 CDT(-0500)] <Bosmon> I see one on pdfExportOptions....
[12:06:35 CDT(-0500)] <Justin_o> Bosmon: yes that's where it is
[12:06:38 CDT(-0500)] <Justin_o> okay.. gotta run
[12:07:35 CDT(-0500)] <Bosmon> Yes, it looks like with that geometry the relevant components could not see each other
[12:07:43 CDT(-0500)] <Bosmon> You will need to introduce a "relay" component at the top level
[12:08:11 CDT(-0500)] <Bosmon> But we should draw it out on a little piece of paper to make sure
[12:08:25 CDT(-0500)] <Bosmon> Or use our marvellous and yet to be constructed AUTHO(U)RING TOOLS (TM)
[12:08:39 CDT(-0500)] <colinclark> a little piece of scanned or photographed paper
[12:08:52 CDT(-0500)] <colinclark> speaking of scanned paper, I have receipts to send to yura and Bosmon
[12:08:56 CDT(-0500)] <colinclark> sorry for being so slow
[12:08:58 CDT(-0500)] <Bosmon> That would be really excellent
[12:09:07 CDT(-0500)] <Bosmon> Don't worry, I haven't even begun to think about submitting my expenses
[12:23:28 CDT(-0500)] <colinclark> michelled: It looks like MediaElement.js's track support is not very well factored
[12:23:50 CDT(-0500)] <colinclark> but they did at least create a distinct WebVTT parser, which you might be able to use to bootstrap your own <track> presentation layer
[12:23:52 CDT(-0500)] <colinclark> https://github.com/johndyer/mediaelement/blob/master/src/js/mep-feature-tracks.js#L412
[12:24:20 CDT(-0500)] <colinclark> although, it is 70 lines of regexps and that's about it
[12:24:47 CDT(-0500)] <michelled> thx colinclark
[12:25:03 CDT(-0500)] <colinclark> this looks like the main logic for displaying captions, and it's incredibly simplistic: https://github.com/johndyer/mediaelement/blob/master/src/js/mep-feature-tracks.js#L247-269
[12:25:49 CDT(-0500)] <colinclark> most of the rest of the file consists of that typical kind of jQuery code we see these days
[12:26:02 CDT(-0500)] <colinclark> endlessly chained
[12:26:07 CDT(-0500)] <colinclark> extremely DOM-specific
[12:26:17 CDT(-0500)] <colinclark> for rendering track-related UI controls
[12:26:43 CDT(-0500)] <colinclark> this is the markup they render for displaying captions: https://github.com/johndyer/mediaelement/blob/master/src/js/mep-feature-tracks.js#L27-42
[12:26:53 CDT(-0500)] <michelled> I'm surprised they put this in their player instead of in the polyfill
[12:27:13 CDT(-0500)] <colinclark> Yes
[12:27:23 CDT(-0500)] <colinclark> It's really terrible factoring
[12:27:35 CDT(-0500)] <colinclark> Someone should do the world a favour and make a clear, focused <track> polyfill
[12:27:41 CDT(-0500)] * colinclark coughs
[12:27:51 CDT(-0500)] <michelled> ha - yeah, I think I might have to
[12:29:01 CDT(-0500)] <colinclark> I'm just going to have a look at Captionator's code
[12:29:11 CDT(-0500)] <colinclark> and see if we can't assemble a picture of the logic required for a sane polyfill
[12:29:46 CDT(-0500)] <colinclark> How he managed to need 2000 lines to do this is beyond me
[13:07:37 CDT(-0500)] <michelled> colinclark: what do you think about me pulling the track support out of media element player and putting into media element js and offering that back?
[13:07:53 CDT(-0500)] <Bosmon> Is github timing out for anyone else....?
[13:08:19 CDT(-0500)] <colinclark> michelled: I think it's worth a shot
[13:11:02 CDT(-0500)] <colinclark> Bosmon: Any guesses on how much work is involved with creating MSIs for Windows?
[13:12:54 CDT(-0500)] <Bosmon> colinclark - no guesses
[13:13:00 CDT(-0500)] <colinclark> ok
[13:13:26 CDT(-0500)] <colinclark> kasper and I are doing some planning--just dreaming of what might be possible before our Microsoft visit
[13:17:46 CDT(-0500)] <colinclark> michelled: Can you think of any small, cool projects related to media, Floe, and the Video Player for this FCC hackathon?
[13:17:46 CDT(-0500)] <colinclark> I was thinking that it would be cool to have people hack on described video features, for example
[13:18:02 CDT(-0500)] <colinclark> the Amara team wants to connect their widget up with new sites
[13:18:02 CDT(-0500)] <colinclark> etc.
[13:31:44 CDT(-0500)] <michelled> those sound good colinclark
[13:42:01 CDT(-0500)] <colinclark> fluid-everyone: is anyone else interested in going the UIO meeting today?