[01:09:58 CDT(-0500)] * Bosmon4 (~a@c-67-176-80-187.hsd1.co.comcast.net) has joined #fluid-work
[05:51:45 CDT(-0500)] * denbuzze (~anonymous@ginger.caret.cam.ac.uk) has joined #fluid-work
[07:07:09 CDT(-0500)] * Justin_o (~Justin@142.150.154.171) has joined #fluid-work
[07:48:12 CDT(-0500)] * jessm (~Jess@c-71-232-3-151.hsd1.ma.comcast.net) has joined #fluid-work
[08:06:11 CDT(-0500)] * kasper (~kasper@189.130.79.156) has joined #fluid-work
[08:49:11 CDT(-0500)] * michelled (~michelled@142.150.154.141) has joined #fluid-work
[08:55:13 CDT(-0500)] * yura_ (~yura@142.150.154.114) has joined #fluid-work
[08:59:51 CDT(-0500)] <zafar> james are you there?
[09:03:10 CDT(-0500)] * jhung (~Asus@seahorse.atrc.utoronto.ca) has joined #fluid-work
[09:03:34 CDT(-0500)] <jameswy> jhung, zafar has some calibration questions for you
[09:04:09 CDT(-0500)] <jhung> zafar, I hope I can answer. I have questions for you too! 
[09:04:16 CDT(-0500)] * anastasiac (~team@142.150.154.193) has joined #fluid-work
[09:04:56 CDT(-0500)] * clown (~clown@142.150.154.101) has joined #fluid-work
[09:05:58 CDT(-0500)] <zafar> lets do this on a separate window
[09:09:35 CDT(-0500)] <zafar> do you have questions for me? I saw the wire frame for decapod 1.0 it looks pretty complete
[09:09:52 CDT(-0500)] <jhung> zafar: in the end, will calibration be the same sort of user process? i.e. position the cameras, take x samples until prompted to stop.
[09:10:28 CDT(-0500)] <zafar> yes it will take a certain number of frames, like previously it was four frames to have better accuracy
[09:10:44 CDT(-0500)] * denbuzze (~anonymous@ginger.caret.cam.ac.uk) has joined #fluid-work
[09:10:45 CDT(-0500)] <zafar> i havent decided on x yet, i think four should be enough like before
[09:11:27 CDT(-0500)] <jhung> If the samples are bad, will there be a way we can notify the user to repeat the process?
[09:12:15 CDT(-0500)] <zafar> i will see if it is possible to have that facility embedded in the code later, but initially aiming to get good samples to have the thing working
[09:12:46 CDT(-0500)] <jhung> That sounds good to me!
[09:14:55 CDT(-0500)] <jhung> So just to confirm, we're going to ask for 4 samples. Will there be some sort of accuracy rating as shown in the movie? What does that number really mean?
[09:15:36 CDT(-0500)] <zafar> close to 1 means good
[09:16:38 CDT(-0500)] <zafar> i am not sure if it is necessary to let the user see the rating, we can just prompt that the camera is calibrated and he/she can proceed
[09:16:51 CDT(-0500)] <jhung> true.
[09:17:15 CDT(-0500)] <jhung> The number itself doesn't mean much, but the user will want to know if their calibration can be better to get better exported books.
[09:17:42 CDT(-0500)] <zafar> it depends on the quality of the samples
[09:17:49 CDT(-0500)] <jhung> yeah.
[09:18:12 CDT(-0500)] <jhung> Not sure if there's a programmatic way we can tell the user or if this is a user process.
[09:20:27 CDT(-0500)] <zafar> well with good samples we can try to get a threshold rating value and if the user's value is less than that rating we can prompt that he/she can better the calibration result but still can proceed if wants
[09:22:32 CDT(-0500)] <jameswy> zafar: Can we just feed a continuous stream of frames and let the user know when we have a good sample set for calibration?
[09:25:45 CDT(-0500)] <zafar> that is interesting, i am not sure if that will increase the code complexity, at the moment I am just trying to capture some samples and calibrate on those basis and ofcourse the samples are considered good as the pattern is in full camera view, may be a thought for later
[09:26:29 CDT(-0500)] <zafar> again good samples are decided on the basis of corner points found in the pattern
[09:28:24 CDT(-0500)] <jhung> This sounds good to me. So to start I'm good with the idea of taking 4 samples. But in the future we may want a way of keep the calibration script running until a quality thresholh has been met.
[09:29:22 CDT(-0500)] <zafar> yes, we can probably decide on the basis of corner points found in the pattern
[09:29:50 CDT(-0500)] <jhung> Can you send a link to the pattern you are using?
[09:31:12 CDT(-0500)] <zafar> its a checker board pattern
[09:31:29 CDT(-0500)] <jhung> okay. So any will do.
[09:32:06 CDT(-0500)] <zafar> yes
[09:33:45 CDT(-0500)] <zafar> alright guys i am off for the day, talk again tomorrow, may be I have something else to ask or share
[09:33:59 CDT(-0500)] <jhung> Thanks zafar!
[09:33:59 CDT(-0500)] <Justin_o> zafar: hello, thanks for the update
[09:34:37 CDT(-0500)] <zafar> hello Justin, no prob
[09:34:44 CDT(-0500)] <zafar> see ya
[09:35:05 CDT(-0500)] <Justin_o> zafar: thanks... we should probably talk later about how to keep in sync with your progress
[09:59:06 CDT(-0500)] * EricDalquist (~dalquist@2607:f388:e:0:221:9bff:fe37:e768) has joined #fluid-work
[10:31:34 CDT(-0500)] * kasper (~kasper@189.130.79.156) has joined #fluid-work
[10:47:28 CDT(-0500)] * colinclark (~colin@142.150.154.148) has joined #fluid-work
[10:55:31 CDT(-0500)] <athena> hey colinclark - you have a minute for yet another pager question?
[10:55:44 CDT(-0500)] <colinclark> athena: sure, why not?
[10:55:47 CDT(-0500)] <colinclark>
[10:55:49 CDT(-0500)] <athena>
[10:56:00 CDT(-0500)] <athena> so i'd like to add some sort links to my pager
[10:56:08 CDT(-0500)] <athena> should i be able to do that even if it's not a table?
[10:56:33 CDT(-0500)] <athena> right now it's eating my "header" links, though perhaps i've just misconfigured something
[10:57:31 CDT(-0500)] * michelled (~michelled@142.150.154.101) has joined #fluid-work
[11:02:21 CDT(-0500)] * elicochran (~elicochra@dhcp-169-229-212-76.LIPS.Berkeley.EDU) has joined #fluid-work
[11:04:19 CDT(-0500)] <athena> ok now i have the link showing up, but it's not actually sorting
[11:35:24 CDT(-0500)] * colinclark_ (~colin@142.150.154.101) has joined #fluid-work
[11:35:31 CDT(-0500)] <athena> welcome back
[11:38:58 CDT(-0500)] * kasper (~kasper@189.130.79.156) has joined #fluid-work
[11:44:54 CDT(-0500)] <athena> hurray, it works!
[11:45:14 CDT(-0500)] <athena> colinclark: i do need some insight about a different issue if you've got time at some point though
[12:18:55 CDT(-0500)] * colinclark (~colin@142.150.154.101) has joined #fluid-work
[12:19:08 CDT(-0500)] * michelled (~michelled@142.150.154.101) has joined #fluid-work
[13:15:36 CDT(-0500)] <colinclark> ack, athena
[13:15:39 CDT(-0500)] <colinclark> i totally suck
[13:15:42 CDT(-0500)] <athena> you do not
[13:15:42 CDT(-0500)] <colinclark> it's been one of those weeks
[13:15:46 CDT(-0500)] <colinclark> i have a free moment now
[13:15:50 CDT(-0500)] <athena> dude i totally hear that
[13:15:53 CDT(-0500)] <athena> ok
[13:15:56 CDT(-0500)] <colinclark> What's up?
[13:15:59 CDT(-0500)] <athena> so at this point i have two questions
[13:16:01 CDT(-0500)] <colinclark> ok
[13:16:30 CDT(-0500)] <athena> 1. is it possible in the pager to have nested components? like can i do <a><img/></a>, and then set decorators on both the link and the image?
[13:16:54 CDT(-0500)] <athena> and 2. i really need to set decorators on the main iterated object - the equivalent of the td
[13:18:06 CDT(-0500)] <colinclark> Let me take a look at the code
[13:18:17 CDT(-0500)] <colinclark> I actually think you know Pager better than I do at this point
[13:18:22 CDT(-0500)] <colinclark> But I can at least take a look
[13:18:30 CDT(-0500)] <athena> thanks so much - i really do appreciate it
[13:18:43 CDT(-0500)] <athena> i think antranig once said that i couldn't do #2, but i did want to check
[13:18:49 CDT(-0500)] <athena> it's use a case we've run into a couple times you
[13:18:51 CDT(-0500)] <athena> er, now
[13:19:56 CDT(-0500)] <athena> if i can't do that, maybe i'm going to have to run some sort of cleanup function after the render?
[13:20:16 CDT(-0500)] * elicochran (~elicochra@2607:f140:400:6140:21b:63ff:fec8:1179) has joined #fluid-work
[13:21:29 CDT(-0500)] <Bosmon2> athena - Yes, nested components are fine - you've seen the "fluid decorator", right?
[13:21:34 CDT(-0500)] <colinclark> lol
[13:21:37 CDT(-0500)] <colinclark> he appears out of nowhere
[13:21:38 CDT(-0500)] <athena> ooh, is that what i need?
[13:21:43 CDT(-0500)] <athena> tada! it's magic
[13:21:48 CDT(-0500)] <Bosmon2> If you attach instances of the "fluid decorator" to the tree, it will instantiate any arbitrary component attached to the markup
[13:21:56 CDT(-0500)] <Bosmon2> Yes, it is indeed magic 
[13:22:05 CDT(-0500)] <colinclark> (the backstory, athena, is that Bosmon2 tried to pull me into another meeting)
[13:22:06 CDT(-0500)] <athena> you i meant you, but that sounds magical too
[13:22:13 CDT(-0500)] <athena> ah
[13:23:13 CDT(-0500)] <colinclark> athena: Have you used fluid decorators before?
[13:23:22 CDT(-0500)] <colinclark> There should be documentation, or I can dig up an example for you
[13:23:24 CDT(-0500)] <athena> nope
[13:23:31 CDT(-0500)] <athena> looking at the decorator listing page right now
[13:23:37 CDT(-0500)] <athena> though if you have an example that would be awesome
[13:24:01 CDT(-0500)] <athena> it looks like it wants another component?
[13:24:45 CDT(-0500)] <Bosmon2> Well, it takes all of the arguments necessary to instantiate your component
[13:25:13 CDT(-0500)] <athena> i'll try it out
[13:25:16 CDT(-0500)] <Bosmon2> There is this one: http://wiki.fluidproject.org/display/fluid/Renderer+Decorators
[13:25:50 CDT(-0500)] <Bosmon2> http://wiki.fluidproject.org/display/fluid/Renderer+Decorators#RendererDecorators-fluiddecorator
[13:26:00 CDT(-0500)] <athena> yep, found it!
[13:26:45 CDT(-0500)] <athena> hmmm
[13:27:07 CDT(-0500)] <athena> i think perhaps i didn't phrase my question very well, mostly because i'm not as up on my fluid terminology as i should be
[13:27:25 CDT(-0500)] <athena> so what i'd really like to do is have something like <a><img/></a>, and then set decorators on both the link and the image
[13:27:40 CDT(-0500)] <athena> so have some bit of nested component tree, which maybe doesn't actually require nested components
[13:27:59 CDT(-0500)] <Bosmon2> Well, that is also fine
[13:28:31 CDT(-0500)] <athena> what's the best way to do that?
[13:28:46 CDT(-0500)] <Bosmon2> Oh, I see
[13:29:16 CDT(-0500)] <Bosmon2> It is fine - you just write all the components as siblings, and supply the one for the <a> to have empty linktext - that is, undefined
[13:29:26 CDT(-0500)] <Bosmon2> Or you can just write the link as a UIOutput if it is not really "linky"
[13:29:36 CDT(-0500)] <athena> ah!
[13:29:36 CDT(-0500)] <Bosmon2> Just because the markup is nested, doesn't mean the components need to be nested
[13:29:41 CDT(-0500)] <Bosmon2> This is an old RSFism
[13:29:43 CDT(-0500)] <athena> ok, i think i'd tried to nest them and it got angry
[13:29:48 CDT(-0500)] <athena> that sounds easy enough
[13:29:50 CDT(-0500)] <athena> thanks!
[13:30:14 CDT(-0500)] <athena> did you have any suggestions on setting decorators on the main iterated element?
[13:32:30 CDT(-0500)] <Bosmon2> Which do you mean, the "main iterated element"?
[13:33:13 CDT(-0500)] <athena> so for a typical table-based set up, the td element that has rsf:id="row:"
[13:37:31 CDT(-0500)] <athena> i'd like to add some CSS classes, etc. to that main element
[13:40:32 CDT(-0500)] <Bosmon2> Ah
[13:45:12 CDT(-0500)] <athena> any ideas?
[13:46:34 CDT(-0500)] <Bosmon2> Just looking at the code
[13:46:41 CDT(-0500)] <athena> thanks so much
[13:47:06 CDT(-0500)] <athena> we'd originally written this using the renderer and decided to add paging features
[13:47:31 CDT(-0500)] <athena> it's really nice to be able to just change the markup a bit and suddenly have it doing paging very cool
[13:48:46 CDT(-0500)] <Bosmon2> I am worrying that the actual root element of each row might be unpleasantly hard to influence
[13:50:24 CDT(-0500)] <Bosmon2> So, look at the sequence around line 527 of Pager.js
[13:50:28 CDT(-0500)] <Bosmon2> There is a sequence
[13:50:37 CDT(-0500)] <Bosmon2> var tree = fluid.transform (blah blah),
[13:50:40 CDT(-0500)] <Bosmon2> var fullTree = {};
[13:50:40 CDT(-0500)] <Bosmon2> fullTree[options.row] = tree;
[13:51:11 CDT(-0500)] <athena> gotcha
[13:51:20 CDT(-0500)] <athena> so do i need to do some sort of post-processing?
[13:51:25 CDT(-0500)] <Bosmon2> Well
[13:51:53 CDT(-0500)] <Bosmon2> I think this might be a point of weakness in the design... but I guess you are patching the file anyway
[13:53:27 CDT(-0500)] <athena> we are?
[13:53:45 CDT(-0500)] <athena> so we've actually had this use case come up a few times - if there were a way to fix it long-term that'd be great
[13:53:51 CDT(-0500)] <athena> but i'll settle for a way to just make it work for now
[13:54:16 CDT(-0500)] <athena> i suppose worst-case scenario we could maybe just wrap all the content in an extra div and assign classes to that instead
[13:58:02 CDT(-0500)] <Bosmon2> Didn't you say you were patching it?
[13:58:07 CDT(-0500)] <Bosmon2> You had submitted a few patches
[14:00:33 CDT(-0500)] <Bosmon2> So, as it stands, there is nowhere in the workflow to apply a decorator to the entire row
[14:03:21 CDT(-0500)] <athena> i think i submitted something for the batched paging
[14:03:44 CDT(-0500)] <athena> though right now that's just implemented as a component, rather than patching fluid code
[14:03:49 CDT(-0500)] <athena> ok, thanks for the confirmation on that
[14:04:06 CDT(-0500)] <athena> so would you recommend post-processing or just a wrapper element?
[14:09:51 CDT(-0500)] <Bosmon2> I guess I would recommend a wrapper element
[14:09:53 CDT(-0500)] <Bosmon2> if you can get away with that
[14:10:07 CDT(-0500)] <Bosmon2> Could I ask you to make a JIRA for this
[14:10:26 CDT(-0500)] <Bosmon2> I want to "get all my ducks in a row" for when I finally get time to finish implementing "Pager II"
[14:10:39 CDT(-0500)] <Bosmon2> I mean, it's interesting to note that I sort of "solved" this problem for the HEADERS of the pager
[14:10:58 CDT(-0500)] <Bosmon2> You see that event that gets fired out, just before rendering it? That allows you to make any arbitrary adjustments to the component tree before it hits the markup
[14:11:06 CDT(-0500)] <Bosmon2> But this wasn't done for the actual pager contents itself
[14:11:21 CDT(-0500)] <colinclark> batched paging is in the incubator
[14:11:34 CDT(-0500)] <colinclark> and will make its way into Pager I in some form for CollectionSpace very soo
[14:11:36 CDT(-0500)] <colinclark> very soon
[14:11:39 CDT(-0500)] <colinclark> soo
[14:12:15 CDT(-0500)] <colinclark> And it looks like the Floe project will give us an opportunity to get Pager II really done sooner rather than later
[14:13:10 CDT(-0500)] <Bosmon2> The current workflow for me is is i) expanders, ii) 2-phase init and "component grades", iii) "final true Ioc"
[14:13:16 CDT(-0500)] <Bosmon2> Pager II depends on item iii)
[14:14:10 CDT(-0500)] <Bosmon2> athena: Actually I'm surprised that this is so bad.... didn't you succeed in getting "alternating row types" working at some point? This seems to imply that you had some control over ....... AAAH!
[14:14:12 CDT(-0500)] <Bosmon2> I remember now!
[14:14:18 CDT(-0500)] <Bosmon2> You used the "elision syntax ~" didn't you
[14:14:23 CDT(-0500)] <athena> sorry, got distracted for a minute
[14:14:35 CDT(-0500)] <athena> you know, that's actually a really good question
[14:14:44 CDT(-0500)] <Bosmon2> So that the "actual row" was a kind of "div" that was elided from the markup, and you made "two real alternating rows" using suffices like "row:even" and "row:odd"
[14:14:45 CDT(-0500)] <Bosmon2> So
[14:14:48 CDT(-0500)] <Bosmon2> You can use this trick again here
[14:14:51 CDT(-0500)] <athena> you're right - we did do something similar - i should go hunt down the source code
[14:15:04 CDT(-0500)] <Bosmon2> And then get control over the rendering of the genuine row element, the one that hits the markup
[14:15:12 CDT(-0500)] <athena> makes sense
[14:15:16 CDT(-0500)] <Bosmon2> Cool beans
[14:15:20 CDT(-0500)] <Bosmon2> Time for my shower finally
[14:15:25 CDT(-0500)] <athena> so essentially we get a wrapper element, but the wrapper doesn't actually end up showing up in the source code
[14:15:30 CDT(-0500)] <athena> sounds perfect
[14:15:45 CDT(-0500)] <athena> and yes, i'll make a JIRA
[14:15:52 CDT(-0500)] <athena> thanks so much for all your help! and yes, get on w/ your day
[14:20:59 CDT(-0500)] * elicochran (~elicochra@dhcp-169-229-212-76.LIPS.Berkeley.EDU) has joined #fluid-work
[16:42:14 CDT(-0500)] <athena> thanks for all the help Bosmon2! i think i'm in business now
[16:42:34 CDT(-0500)] <athena> it turns out that for that previous even/odd use case, we talked about using the elision syntax but it had a bug at the time
[16:42:44 CDT(-0500)] <athena> so we just did some post-processing instead
[16:42:53 CDT(-0500)] <athena> but now it works just beautifully - first time i've seen it in action
[16:45:59 CDT(-0500)] * anastasiac (~team@142.150.154.193) has left #fluid-work
[20:23:43 CDT(-0500)] * kasper (~kasper@189.130.79.156) has joined #fluid-work
[20:58:44 CDT(-0500)] * Bosmon4 (~a@67-41-201-71.hlrn.qwest.net) has joined #fluid-work
[22:31:36 CDT(-0500)] * michelled (~michelled@CPE001310472ade-CM0011aefd3ca8.cpe.net.cable.rogers.com) has joined #fluid-work
[22:45:54 CDT(-0500)] * Bosmon4 (~a@c-67-176-80-187.hsd1.co.comcast.net) has joined #fluid-work
Page Comparison
General
Content
Integrations