Skip to end of metadata
Go to start of metadata

[08:47:37 CST(-0600)] <jhung> justin_o: I have posted a "spec" for genpdf. Take a look when you have time. http://wiki.fluidproject.org/display/fluid/Decapod+genpdf+features+and+functions

[08:48:35 CST(-0600)] <Justin_o> jhung thanks.. i was looking over this a bit yesterday.. i'm assuming this is all functionality that we'd like to have as opposed to what is currently there

[08:51:21 CST(-0600)] <Justin_o> jhung: i wonder if the colour output should be split

[08:51:41 CST(-0600)] <Justin_o> so one option for bit depth and one for colour

[08:51:46 CST(-0600)] <Justin_o> jhung: ^

[08:52:21 CST(-0600)] <Justin_o> but if you think it will be too complicated that's fine

[08:53:17 CST(-0600)] <jhung> justin_o: if we split the colour into separate options, it's possible that a user would put both "grey" and "colour" in the same command. We'd have to throw an exception in that case I guess.

[08:55:14 CST(-0600)] <Justin_o> jhung: I mean.. they would do something like -bit 8 -c g

[08:55:16 CST(-0600)] <jhung> but you're right though, it would be nice if we can go genpdf -grey 256 instead.

[08:55:25 CST(-0600)] <jhung> ah

[08:55:26 CST(-0600)] <Justin_o> jhung: yes.. something like that

[08:55:46 CST(-0600)] <jhung> so we treat bit and colour as different options. Got it.

[08:56:09 CST(-0600)] <Justin_o> the issue though would be you could have -bit 24 -c b which it looks like would be an error

[08:56:11 CST(-0600)] <jhung> makes sense. It will make more logically to what we would have on the UI too justin_o.

[08:57:11 CST(-0600)] <jhung> I'll update that now.

[08:59:56 CST(-0600)] <Justin_o> jhung: thanks

[09:13:24 CST(-0600)] <jhung> justin_o: here's an interesting situation. what if the user does "genpdf -c bw -bit 8"? Should the behaviour be to override with the -bit 1 default, or throw an error? I'm thinking that an error is appropriate since we shouldn't assume the user's intent.

[09:14:04 CST(-0600)] <Justin_o> jhung: i think i'd agree with you.. better than having to wait a few hours to find out it didn't do what you expected

[09:14:13 CST(-0600)] <jhung> lol

[09:14:19 CST(-0600)] <jhung> true justin_o.

[09:15:25 CST(-0600)] <jhung> Also, what should we do in this situaiton: genpdf -c colour -bit 1. Should we just binarize to black and white, or throw an error?

[09:15:38 CST(-0600)] <jhung> ^justino

[09:15:43 CST(-0600)] <jhung> ^justin_o rather

[09:18:04 CST(-0600)] <Justin_o> jhung: hmm.. so because it's one bit it will always be banalized?

[09:18:38 CST(-0600)] <jhung> justin_o: yes. by definition 1 bit colour is binary.

[09:18:44 CST(-0600)] <Justin_o> jhung: that was supposed to be binarized, i blame my autocorrection

[09:18:50 CST(-0600)] <michelled> colinclark: alexn2 and I are making progress on getting the captions to show

[09:19:02 CST(-0600)] <jhung> (black and white is so banal! (tongue) )

[09:19:25 CST(-0600)] <colinclark> Justin_o: I thought it was very poetic

[09:19:30 CST(-0600)] <jhung> lol

[09:20:09 CST(-0600)] <Justin_o> (smile) jameswy would be happy to know that my Mac is forcing my writing to be more beautiful

[09:20:22 CST(-0600)] * jhung rofl

[09:20:26 CST(-0600)] <jameswy> (smile)

[09:20:33 CST(-0600)] <jhung> it beckons me...

[09:21:52 CST(-0600)] <Justin_o> (smile)

[09:22:47 CST(-0600)] <jhung> so justin_o, I think regardless of what -c is, if the user specifies -bit 1 it will always be binary.

[09:23:17 CST(-0600)] <Justin_o> jhung: so i'm thinking about this again, and wonder if we are losing some consistency

[09:23:35 CST(-0600)] <Justin_o> or maybe this is just an edge case

[09:24:16 CST(-0600)] <jhung> justin_o: it's an edge case, but I'd like to hear your thoughts about consistency.

[09:25:06 CST(-0600)] <Justin_o> jhung: so we were saying that for the case where they said -c bw -bit 8 it would throw an error

[09:25:23 CST(-0600)] <Justin_o> but not for -c colour -bit 1

[09:25:42 CST(-0600)] <Justin_o> but it could be the -bit 1 that was typed incorrectly

[09:26:12 CST(-0600)] <Justin_o> although I suppose that the edge case here is that it's still technically correct.. that -bit 1 with any colour setting is equivalent

[09:26:26 CST(-0600)] <Justin_o> jhung: ^

[09:27:26 CST(-0600)] <jhung> hmmm. good point.

[09:28:03 CST(-0600)] <jhung> what if we got rid of the -c bw option and support -c colour / grey. Then to binarize, the user would specify a bit depth of 1.

[09:28:06 CST(-0600)] <jhung> ^justin_o

[09:28:23 CST(-0600)] <Justin_o> jhung: yes i like that better

[09:28:59 CST(-0600)] <jhung> justin_o excellent. I'll put that in.

[09:30:26 CST(-0600)] <Justin_o> jhung: thanks..

[09:34:43 CST(-0600)] <michelled> colinclark, cindyli: we checked in with jvass and apparently the hiding and showing of the controls should slide up and down and push the captions up with it. I'm feeling pretty strongly that the markup needs to change at this point because it isn't a good reflection of the interface we want. if we make changes to the markup do you think that will be a problem for the work you are doing?

[09:35:11 CST(-0600)] <colinclark> michelled: no, I think we should just merge my branch first (smile)

[09:35:45 CST(-0600)] <colinclark> it's an improvement, especially if you can address the captions

[09:35:51 CST(-0600)] <colinclark> i think the sliding in and out stuff will be really cool

[09:36:00 CST(-0600)] <michelled> colinclark: we have a quick and dirty for the captions that could go in now

[09:36:06 CST(-0600)] <colinclark> yeah, let's do it

[09:36:12 CST(-0600)] <michelled> then we could do a better job which includes the markup changes

[09:36:14 CST(-0600)] <colinclark> Put the usual TODOs in the code

[09:36:21 CST(-0600)] <colinclark> so we make it clear that it's hacky

[09:36:27 CST(-0600)] <colinclark> and let's focus on the real thing

[09:36:32 CST(-0600)] <colinclark> a nicer, working demo branch

[09:36:42 CST(-0600)] <colinclark> michelled: How about you and alexn2 review my branch

[09:36:44 CST(-0600)] <colinclark> it's small and simple

[09:36:53 CST(-0600)] <colinclark> and then push 'er on up to the demo branch?

[09:37:00 CST(-0600)] <michelled> colinclark: sounds good colinclark

[09:37:13 CST(-0600)] <colinclark> I believe I made three commits

[09:37:20 CST(-0600)] <colinclark> each commit itemizes the issues I think I fixed

[09:37:29 CST(-0600)] <colinclark> There is a one-line JS change

[09:37:37 CST(-0600)] <colinclark> The HTML of course will look radically different due to tabbing

[09:37:52 CST(-0600)] <colinclark> Maybe someone has a nice way to do non-whitespace diffs in Git?

[09:37:58 CST(-0600)] <colinclark> The CSS should look fairly straightforward

[09:38:05 CST(-0600)] <colinclark> the only complication to seeing what I've done is that I moved stuff around

[09:38:11 CST(-0600)] <colinclark> we had styles flung all over the place

[09:38:22 CST(-0600)] <colinclark> so I've been trying to group them together roughly by component or region of the page

[09:38:48 CST(-0600)] <colinclark> alexn2: Your turn to review me--go for it!

[09:39:49 CST(-0600)] <michelled> colinclark: I see 2 commits - does that seem right?

[09:39:53 CST(-0600)] <michelled> https://github.com/colinbdclark/videoPlayer/commits/FLUID-4596

[09:42:30 CST(-0600)] <colinclark> yes, two is right

[09:42:40 CST(-0600)] <colinclark> There was an imaginary third commit

[09:42:43 CST(-0600)] <colinclark> it is the best one

[09:42:59 CST(-0600)] <colinclark> everything in that commit looks exactly like how jvass wants it to (smile)

[09:43:36 CST(-0600)] <michelled> oh, I love that commit!

[09:45:05 CST(-0600)] <michelled> colinclark: does a border-radius of 0 do anything?

[09:48:47 CST(-0600)] <colinclark> michelled: it certainly does!

[09:48:51 CST(-0600)] <colinclark> it squares otherwise rounded corners

[09:49:04 CST(-0600)] <michelled> ah, makes sense

[09:49:16 CST(-0600)] <michelled> I'm also curious about the 'min' option of slider

[09:49:28 CST(-0600)] <michelled> "A min range goes from the slider min to one handle."

[09:49:41 CST(-0600)] <michelled> I'm not really sure what that means in context of the scrubber

[09:49:47 CST(-0600)] <colinclark> It colourized the region of the slider that is below the handle

[09:49:53 CST(-0600)] <michelled> ah, thanks

[09:50:10 CST(-0600)] <colinclark> so, in the case of the scrubber, it colourizes the section of the video that is "in the past"

[09:50:18 CST(-0600)] <michelled> your changes look good

[09:50:25 CST(-0600)] <michelled> we'll once over our changes and let you know when it's in

[09:50:56 CST(-0600)] <colinclark> great

[09:51:07 CST(-0600)] <colinclark> i'll hop on the subway and see you shortly to do more styling

[09:51:24 CST(-0600)] <colinclark> I'm hoping jvass will tell us we're cool by the end of the day

[09:51:35 CST(-0600)] <colinclark> maybe not done, but at least we can prove how cool we are

[09:53:25 CST(-0600)] <jvass> (smile)

[09:58:21 CST(-0600)] <michelled> cindyli: have you managed to push the fixes required for the tests to pass?

[09:58:35 CST(-0600)] <cindyli> yes, about to, michelled

[09:58:48 CST(-0600)] <michelled> ok, we'll wait for you (smile)

[10:03:48 CST(-0600)] <cindyli> pushed, michelled & alexn2. however, the tests still fail in ie8, and i believe also other non-html5 browsers due to the inclusion of html5Captionator script. It's perhaps OK for now since we know captionator only works in html5 browsers. But we do need to fix it at some point.

[10:15:00 CST(-0600)] <avtar> fluid-everyone: i'll miss standup/connections today because i'm racking servers with bert at the data centre. yesterday was spent looking into continuum and git branch issues, hanging out with colin and jess to briefly discuss future infrastructure planning and doing research for vendor rfp inquiries. i'll be back in the office once we're done here.

[10:19:32 CST(-0600)] <michelled> thx cindyli - we've pushed our changes too

[10:19:49 CST(-0600)] <michelled> cindyli: you will want to update because colin's styling modifications are in there too

[10:20:01 CST(-0600)] <cindyli> cool. thanks

[10:27:04 CST(-0600)] <michelled> jameswy, jvass: this is where we are at currently: http://build.fluidproject.org/videodemo/videoPlayer/demos/Mammals.html

[10:27:33 CST(-0600)] <michelled> and our demo plan: http://wiki.fluidproject.org/display/fluid/Floe+Demo+Plan

[10:27:56 CST(-0600)] <michelled> jameswy, jvass: if there are things you notice that should be fixed pre demo that aren't on our list please let us know

[10:28:10 CST(-0600)] <jameswy> Great; thanks, michelled

[10:57:19 CST(-0600)] <cindyli> michelled, alexn2, colinclark, i pushed in the auto-scrolling

[11:56:46 CST(-0600)] <colinclark> michelled, cindyli: I'm having trouble with VP in Chrome

[11:57:00 CST(-0600)] <colinclark> When I try to turn on captions, it throws an error

[11:57:23 CST(-0600)] <colinclark> we've got the minified version of Infusion in the repo again, so I can't debug it

[11:59:07 CST(-0600)] <colinclark> cindyli: I love your transcript component

[11:59:08 CST(-0600)] <colinclark> it's so cool

[11:59:22 CST(-0600)] <cindyli> thanks. i love it too (smile)

[12:07:35 CST(-0600)] <cindyli> colinclark: u r right that the event.layerX is from jQuery, not necessarily scrollTo plugin tho. Upgrading to jQuery 1.7 will fix this chrome warning: http://stackoverflow.com/questions/7825448/webkit-issues-with-event-layerx-and-event-layery

[12:09:53 CST(-0600)] <colinclark> aha

[12:09:59 CST(-0600)] <colinclark> okay, let's leave it for now

[12:10:02 CST(-0600)] <colinclark> can you file a quick bug about it?

[12:10:06 CST(-0600)] <colinclark> just so we don't forget?

[12:10:50 CST(-0600)] <cindyli> sure

[12:17:14 CST(-0600)] <cindyli> jira created - http://issues.fluidproject.org/browse/FLUID-4617

[12:17:44 CST(-0600)] <colinclark> thanks so much, cindyli

[12:17:51 CST(-0600)] <cindyli> np

[12:39:13 CST(-0600)] <Justin_o> colinclark, jvass: I guess you can look at this to see what you can use for css3 stuff http://caniuse.com/

[12:39:24 CST(-0600)] <Justin_o> it even looks like they tell you when you need the vendor prefixes

[12:56:52 CST(-0600)] <colinclark> jameswy: I'm obsessed with pixels

[12:57:01 CST(-0600)] <colinclark> each tiny pixel

[12:57:26 CST(-0600)] <jhung> ^oh no. not another one.

[12:58:10 CST(-0600)] <jameswy> Hahaha.

[12:58:16 CST(-0600)] <jameswy> I'm pleased, (smile)

[13:16:20 CST(-0600)] <jhung> justin_o: currently the --width and --height are in centimeters. Do you think there should be an option for inches? Example: genpdf -w 8.5 -h 11 -inches

[13:17:08 CST(-0600)] <Justin_o> jhung: i guess it would be nice

[13:19:06 CST(-0600)] <jhung> justin_o: so this raises an interesting question about how "nice" we should make the genpdf script....

[13:19:32 CST(-0600)] <Justin_o> jhung: that is a good question (smile)

[13:20:21 CST(-0600)] <jhung> justin_o: Along the same lines, I was thinking about specifying error messages too in the spec but I'm wondering if it's going too far?

[13:21:23 CST(-0600)] <Justin_o> jhung: why do you think that?

[13:22:59 CST(-0600)] <jhung> justin_o: maybe I just feel like I'm over-specc'ing things. (tongue)

[13:23:40 CST(-0600)] <Justin_o> jhung: (smile) hmm.. not sure.. could be.. it might help them out for development.. and it would make sure we would know what was wrong.. i suppose you could ask them to help with that

[13:27:10 CST(-0600)] <alexn2> cindyli, michelled: I'm not quite sure that the fact that videoPlayer does not work in lower versions of IE related to the captionator since I ran some tests and it fails in the Infusion.js file. IE complains about attributes.default = "true"; in html5Captionator since it does not like this syntax. Which is not right since default is a reserved word. But still if I change the code to attributes["default"] = "true"; which eliminates this warni

[13:27:44 CST(-0600)] <cindyli> interesting

[13:28:16 CST(-0600)] <alexn2> It definitely started to happen after the merge since the branch which I was using before the merge worked completely fine in lower versions in IE… so I will try to find what was changed.

[13:34:52 CST(-0600)] <jhung> justin_o: I'm also going to add a -f or --force option to force the overwriting of duplicate directories and output files.

[13:35:36 CST(-0600)] <Justin_o> jhung: that's good

[13:36:01 CST(-0600)] <jhung> but in the case of a book directory, does using the -f overwrite and leave any non-overwritten files in the book directory intact, justin_o?

[13:36:33 CST(-0600)] <jhung> or does -f effectively delete the directory and creates a new one with the same name?

[13:37:40 CST(-0600)] <Justin_o> jhung: i would think it would clear it all out

[13:38:08 CST(-0600)] <jhung> justin_o: okay. I was thinking the same.

[13:39:08 CST(-0600)] <Justin_o> jhung: cool

[14:50:21 CST(-0600)] <Justin_o> jhung: i pushed up that component, i've called it visSwitcher for now.. it's not being used by anything, but you can play with the unit tests if you like (smile)

[14:53:28 CST(-0600)] <jhung> justin_o: excellent! Thanks. I'll check it out. So I guess the next step is to have the Exporter use this?

[14:54:11 CST(-0600)] <Justin_o> jhung: yes… i'll remove the statusToggle, use this there, and then work out how to use it for those export controls

[14:54:40 CST(-0600)] <jhung> Cool. Thanks Justin_o!

[14:55:55 CST(-0600)] <Justin_o> jhung: no problem.. have a good weekend and hope you feel better soon.

[14:58:14 CST(-0600)] <cindyli> michelled: alexn2, colinclark, i pushed some changes into the demo branch

[14:58:29 CST(-0600)] <michelled> thx cindyli

[14:58:36 CST(-0600)] <cindyli> np

[14:58:40 CST(-0600)] <michelled> how did you fix the problem with context resolution cindyli?

[14:59:16 CST(-0600)] <cindyli> michelled: add in another demands block that gets resolved in the absence of "controller"

[15:00:09 CST(-0600)] <michelled> ah, great

[15:00:11 CST(-0600)] <cindyli> yura helped me to identify the cause. (smile) thanks, yura

[15:09:02 CST(-0600)] <michelled> yay! we impressed yura with our video player + transcripts + UIO

[15:09:16 CST(-0600)] <yura> it's magical

[15:09:38 CST(-0600)] <michelled> cindyli: can you take a look at how transcripts respond to UIO?

[15:09:45 CST(-0600)] <michelled> it looks like line spacing isn't working

[15:15:58 CST(-0600)] <cindyli> sure, michelled

[16:13:07 CST(-0600)] <cindyli> michelled: the removal of the line-height from transcript DIV has been pushed

[16:15:46 CST(-0600)] <cindyli> heading home. have a great weekend, everyone

[16:30:32 CST(-0600)]

<drewwills> hello fluid gurus... i'm having an issue with that.locate(

Unknown macro: {selector}

)... it doesn't seem to be finding my node...

[16:30:42 CST(-0600)] <drewwills> my selector is this: ".portal-navigation-add, #portalPageHeader .portal-navigation-add"

[16:31:17 CST(-0600)] <drewwills> where #portalPageHeader is outside the original element upon which the fluid component was created

[16:36:59 CST(-0600)] <drewwills> is it impossible to select an element that is not a child of the one passed to the creator function?

[17:00:58 CST(-0600)] <colinclark_> hi drewwills

[17:01:16 CST(-0600)] <colinclark_> sorry for the delay in responding

[17:01:34 CST(-0600)] <colinclark_> By default, that.locate() will always scope selectors within the component's container.

[17:01:43 CST(-0600)] <colinclark_> It's literally the equivalent of doing this:

[17:01:49 CST(-0600)] <colinclark_> $(selector, that.container)

[17:01:57 CST(-0600)] <colinclark_> If you want to break out of the component's container, you can

[17:02:13 CST(-0600)] <colinclark_> just specify another context as the second argument to that.locate()

[17:02:18 CST(-0600)] <colinclark_> So, something like this:

[17:02:31 CST(-0600)] <colinclark_> that.locate("div", body)

[17:02:41 CST(-0600)] <colinclark_> which would select all the <divs> within the whole page.

[17:05:10 CST(-0600)] <drewwills> ah! thanks colin

[17:06:49 CST(-0600)] <colinclark_> any time

  • No labels