fluid-work IRC Logs-2011-05-31

Owned by Fluid IRC Log Bot
Last updated: May 31, 2011Version comment
23 min read

[07:34:29 CDT(-0500)] <Justin_o> heidi: hello
[07:34:39 CDT(-0500)] <heidi> hi Justin_o
[07:36:10 CDT(-0500)] <Justin_o> heidi: hi, I still haven't heard back from the guy about the clearfix license. Would you be able to spend some time this week to find an acceptable alternative that has a compatible open source licenses? I'm a bit worried that we won't hear back about the one we used, in time to get it in for this release
[07:37:18 CDT(-0500)] <heidi> Justin_o um, did we have another clearfix in our test that was close?
[07:38:34 CDT(-0500)] <Justin_o> heidi: i guess the old clearfix would be fine... but not sure what the license on that one was either
[07:40:59 CDT(-0500)] <heidi> Justin_o i don't really understand why we can't use it. he said it's fine. that's not enough ?
[07:41:04 CDT(-0500)] <Justin_o> heidi: what do you think of this one http://nicolasgallagher.com/micro-clearfix-hack/
[07:41:32 CDT(-0500)] <Justin_o> heidi: to cover ourselves we want to make sure that we have proper licenses.
[07:42:36 CDT(-0500)] <heidi> Justin_o it looks similar... can we add it to our test page?
[07:43:21 CDT(-0500)] <Justin_o> heidi: i could try to make a branch for that again
[07:43:48 CDT(-0500)] <heidi> Justin_o is the test page not in the clearfix branch?
[07:44:38 CDT(-0500)] <Justin_o> heidi: yes.. but didn't want to mess up that branch just yet, in case we hear back..
[07:45:02 CDT(-0500)] <heidi> Justin_o we could still add it to the test page as an option to consider... cos we have others we're not using there too right
[07:45:14 CDT(-0500)] <heidi> brb, hanging laundry on the line...
[07:46:03 CDT(-0500)] <Justin_o> heidi: (smile) good warm weather to hang laundry
[07:46:33 CDT(-0500)] <Justin_o> heidi: i stripped the other examples out when i moved it up to the demos.. didn't make much sense to have a demo showing styling we didn't actually have.
[08:05:12 CDT(-0500)] <heidi> Justin_o might be nice to test it as a ready back-up, and push the branch if need to?
[08:05:40 CDT(-0500)] <heidi> Justin_o can we pair later today to talk about the fatpanel js wrapper?
[08:06:51 CDT(-0500)] <Justin_o> heidi: checkout this branch https://github.com/jobara/infusion/tree/FLUID-4023-alternatives
[08:06:58 CDT(-0500)] <Justin_o> i've added the micro clearfix to the demo
[08:07:08 CDT(-0500)] <heidi> awesome
[08:07:11 CDT(-0500)] <heidi> will do
[08:07:52 CDT(-0500)] <Justin_o> heidi: I'll be spending most of today working on the stuff for colin's and my presentation tomorrow, but I think I'll have a bit of time to spare for pairing
[08:08:05 CDT(-0500)] <Justin_o> heidi: thanks for taking a look, let me know what you think
[08:08:16 CDT(-0500)] <Justin_o> the css is in the demo's css file
[08:09:20 CDT(-0500)] <heidi> Justin_o okay. also, np about pairing... i think if anything it'll be a "am i on the right track?" thing.
[08:11:28 CDT(-0500)] <Justin_o> heidi: okay... sorry that I don't have more time though.. it always seems like these conferences and things come up at times when we're all busy.. I hope to have some more time on the Thursday and Friday though
[08:12:15 CDT(-0500)] <heidi> yeah Justin_o ... actually maybe i'll come in on thurs instead of tomorrow so i can work with you in person, if that's cool
[08:12:45 CDT(-0500)] <Justin_o> heidi: sure that'll work for me
[08:13:04 CDT(-0500)] <Justin_o> and we can still pair a bit today if you like
[08:13:22 CDT(-0500)] <heidi> awesome thanks
[08:35:28 CDT(-0500)] <heidi> Justin_o where's the clearfix demo again?
[08:35:41 CDT(-0500)] <Justin_o> heidi: it's in the fss demos
[08:35:49 CDT(-0500)] <heidi> ah was looking in tests
[08:35:51 CDT(-0500)] <Justin_o> demos/fss/clearfix
[08:35:57 CDT(-0500)] <Justin_o> heidi: ah, yes.. moved it up
[08:36:52 CDT(-0500)] <heidi> Justin_o and for columns mixed, we were just going to scoot around that issue by using the old fl-fix right?
[08:37:08 CDT(-0500)] <Justin_o> heidi: yes.. i think so
[08:37:24 CDT(-0500)] <heidi> Justin_o cool, and microfix has a license?
[08:37:27 CDT(-0500)] <Justin_o> heidi: actually they mention it on the page for the micro fix too
[08:37:52 CDT(-0500)] <Justin_o> heidi: i think so.. there's a notice at the bottom that says all original code is dual licensed under MIT and GPLv2
[08:40:53 CDT(-0500)] <heidi> ok cool (smile)
[08:45:23 CDT(-0500)] <heidi> Justin_o micro is a lot less css, which is nice. i wonder what the diff between content: " " and content:"" is?
[08:45:41 CDT(-0500)] <heidi> did you test it on IEs?
[08:45:51 CDT(-0500)] <Justin_o> heidi: not yet, didn't get a chance
[08:46:39 CDT(-0500)] <Justin_o> heidi: as for the previous question.. i seems like old browsers pre-ff3.5 needed some actual content there that was hidden, but newer versions don't
[08:47:00 CDT(-0500)] <heidi> and we don't need to worry about pre-ff3.5? or is that bad
[08:47:04 CDT(-0500)] <Justin_o> since we don't have a-grade support below FF 3.6 i figured it should be okay
[08:47:08 CDT(-0500)] <heidi> ah
[08:47:19 CDT(-0500)] <Justin_o> i guess it's less than ideal, but may be alright
[08:49:38 CDT(-0500)] <heidi> Justin_o if we put a space in there and set font-size:0 it starts to look like the other unlicensed clearfix
[08:53:49 CDT(-0500)] <Justin_o> heidi: yes.. there's similarities between all of these, but i think there are still differences... we should definitely discuss this issue though before pushing it up
[08:54:44 CDT(-0500)] <Justin_o> michelled: do you have any thoughts on this stuff... heidi and i are looking at another clearfix option it's in my branch at https://github.com/jobara/infusion/tree/FLUID-4023-alternatives in the clearfix demo's css file
[08:55:26 CDT(-0500)] <heidi> Justin_o do you have IE handy?
[08:56:56 CDT(-0500)] <michelled> Justin_o, heidi: if this works the same it certainly looks nice and clean
[08:57:03 CDT(-0500)] <michelled> not much code there at all (smile)
[08:57:14 CDT(-0500)] <michelled> pulkit: how are things going?
[08:57:14 CDT(-0500)] <Justin_o> heidi: i could pull up a vm
[08:57:55 CDT(-0500)] <pulkit> hi michelled
[08:58:26 CDT(-0500)] <pulkit> I uploaded the code to github
[08:58:33 CDT(-0500)] <michelled> great - I just saw your e-mail
[08:58:44 CDT(-0500)] <michelled> pulkit: it would be better to send those emails to the fluid-work list
[08:58:47 CDT(-0500)] <pulkit> I have implmented the selector that allows for user to select the portion to be cropped from image
[08:58:51 CDT(-0500)] <michelled> that way jhung will also see your questions
[08:59:11 CDT(-0500)] <pulkit> yes. sure
[08:59:23 CDT(-0500)] <michelled> jhung: are you around?
[08:59:26 CDT(-0500)] <pulkit> I will send the mail to fluid-work list also
[08:59:32 CDT(-0500)] <jhung> michelled. yep.
[08:59:43 CDT(-0500)] <michelled> pulkit: why don't you just ask him here (smile)
[08:59:53 CDT(-0500)] <jhung> pulkit, what's up?
[08:59:54 CDT(-0500)] <michelled> jhung: pulkit had a question about tagging
[09:00:15 CDT(-0500)] <pulkit> hi jhung
[09:00:55 CDT(-0500)] <jhung> pulkit, hi. Hope I can help. (smile)
[09:01:09 CDT(-0500)] <pulkit> I am not sure about what tagging does in image editor
[09:01:22 CDT(-0500)] <pulkit> Does tagging refer to the user writing some text on the image? Or is it something like tagging people on social networks?
[09:02:11 CDT(-0500)] <jhung> pulkit: Can you point me to the document / context in which this tagging is mentioned?
[09:03:12 CDT(-0500)] <pulkit> jhung: http://wiki.fluidproject.org/display/fluid/Google+Summer+of+Code+with+the+Fluid+Project
[09:03:35 CDT(-0500)] <pulkit> jhung: Its on this page. Under the heading Image Editor
[09:03:37 CDT(-0500)] <jhung> ah got it.
[09:04:42 CDT(-0500)] <jhung> pulkit: perhaps "tagging" isn't the right word to describe this functionality.
[09:05:19 CDT(-0500)] <jhung> pulkit: what it should say is "marking up or annotating a visual image using text, or other rich content".
[09:05:52 CDT(-0500)] <pulkit> ok. thanks (smile)
[09:06:15 CDT(-0500)] <jhung> pulkit: so basically you should be able to draw a region on an image, and then add text, another image, links, etc to the annotation. So when someone views that image and mouses over or keyboard focuses the region, they will see the annotation.
[09:07:02 CDT(-0500)] <jhung> pulkit: does that make sense?
[09:07:12 CDT(-0500)] <jhung> Not sure if I explained that well. (tongue)
[09:08:06 CDT(-0500)] <pulkit> jhung: I think so. But then that functionality will only be available when the image is open in the image editor
[09:08:43 CDT(-0500)] <pulkit> jhung: when the user saves the image to his system, should it still be annotated with annotations appearing on mouse over?
[09:09:03 CDT(-0500)] <jhung> pulkit: possibly. Unless there's a standard format out there that describes coordinates and content.
[09:10:13 CDT(-0500)] <jhung> pulkit: yes I think the annotations should travel with the image unless the user specifies not to.
[09:12:06 CDT(-0500)] <pulkit> jhung: But then, they would appear as normal text on the image, right?
[09:14:15 CDT(-0500)] <jhung> pulkit, hmmm I think I may need to draw this up a little. Can you give me a few minutes to whip something up?
[09:14:46 CDT(-0500)] <pulkit> jhung, yes sure. Take your time.
[09:32:36 CDT(-0500)] <michelled> pulkit: it looks like you've got a great start on the ImageEditor
[09:32:48 CDT(-0500)] <michelled> I haven't had a chance to try it out yet but I took a glance at the code
[09:33:07 CDT(-0500)] <michelled> you're even using grades (smile)
[09:33:19 CDT(-0500)] <pulkit> Thanks michelled
[09:34:57 CDT(-0500)] <pulkit> michelled:I tried to follow most of the conventions which were in the Uploader component
[09:36:21 CDT(-0500)] <michelled> pulkit: are you planning on turning the CropperUI into a component as well? I think it would be a good idea
[09:37:31 CDT(-0500)] <pulkit> Yes. I think it could be useful
[09:38:21 CDT(-0500)] <pulkit> and I could rename it to Selector instead of CropperUI
[09:38:54 CDT(-0500)] <michelled> too bad the name selector is so overloaded in this context
[09:39:02 CDT(-0500)] <michelled> perhaps we can find another name
[09:39:17 CDT(-0500)] <pulkit> yes. sure
[09:45:16 CDT(-0500)] <Justin_o> heidi, michelled: I tried out the micro clearfix in IE6, IE7, IE8, Chrome, FF3.6 (Win XP), Safari 5 (Mac OS X), FF4, IE9 (Win 7)
[09:45:19 CDT(-0500)] <Justin_o> all were working
[09:45:42 CDT(-0500)] <heidi> great, thanks for testing
[09:45:45 CDT(-0500)] <michelled> that's great new
[09:45:49 CDT(-0500)] <michelled> nes
[09:45:54 CDT(-0500)] <michelled> news (big grin)
[09:48:02 CDT(-0500)] <heidi> hey mlam the auto-save thing merged into the big UIO branch right?
[09:48:10 CDT(-0500)] <heidi> how does it work? it's an option for UIO?
[09:48:11 CDT(-0500)] <mlam> yah, it is
[09:48:26 CDT(-0500)] <mlam> heidi: yah, it's a component option for UIO
[09:48:43 CDT(-0500)] <mlam> set the autoSave option to true, and it'll save whenever a change is made
[09:49:21 CDT(-0500)] <heidi> cool i see
[09:49:26 CDT(-0500)] <heidi> thanks mlam
[09:49:33 CDT(-0500)] <mlam> yw
[09:49:53 CDT(-0500)] <mlam> let me know if you guys need some tweaking if it isn't what you guys are looking for
[09:50:08 CDT(-0500)] <heidi> mlam cool i'm gonna use it soon so i'll keep ya posted
[09:50:29 CDT(-0500)] <mlam> ok
[09:51:57 CDT(-0500)] <Justin_o> heidi: do you know if the clearfix is needed for UIO anytime soon.. I think we're just going to go with the micro clearfix if you are happy with it
[09:52:17 CDT(-0500)] <Justin_o> but i'm wondering if I can wait to clean up the branch till thursday or if you'll need it sooner
[09:52:32 CDT(-0500)] <heidi> Justin_o the layouts use it but not sure how dependent on them. it can wait till thurs, jameswy is gonna do clean up then
[09:52:43 CDT(-0500)] <Justin_o> heidi: thanks..
[09:58:19 CDT(-0500)] <jhung> pulkit, I have added a comment to this page, including a mock-up: http://wiki.fluidproject.org/display/fluid/Google+Summer+of+Code+with+the+Fluid+Project
[09:58:46 CDT(-0500)] <pulkit> thanks jhung. I will have a look at it.
[10:00:04 CDT(-0500)] <jhung> colinclark: got a sec to chat about the image gallery uploader?
[10:07:34 CDT(-0500)] <cindyli> heidi: i pushed the changes for the left-over issues that you pointed out in 4216, the implementation of the multipliers etc, into the mreging branch 4267.
[10:07:53 CDT(-0500)] <heidi> cindyli awesome i'll take a look in a bit
[10:07:55 CDT(-0500)] <heidi> thanks
[10:08:30 CDT(-0500)] <cindyli> thanks, heidi, one more thing is that i noticed the dropdown list box looks a bit odd
[10:08:34 CDT(-0500)] <cindyli> u might still be working on it
[10:08:57 CDT(-0500)] <cindyli> i was playing with the latest version of 4267
[10:08:57 CDT(-0500)] <heidi> cindyli yeah there's more tweaking to do, on thurs. did you add classnames to the options?
[10:09:25 CDT(-0500)] <cindyli> what classnames? to what options?
[10:10:02 CDT(-0500)] <heidi> for the dropdowns. forget if it was in my list. we talked about adding classes to each option so we can style them, ex. for fonts - each option will be in that font
[10:10:03 CDT(-0500)] <cindyli> oh, u mean to the <select> on the template?
[10:10:33 CDT(-0500)] <cindyli> yes, yes, ic, i forgot that part
[10:10:48 CDT(-0500)] <cindyli> doing it now.
[10:10:55 CDT(-0500)] <heidi> thanks!
[10:12:47 CDT(-0500)] <colinclark> jhung: I would love to talk to you about the Image Gallery
[10:12:54 CDT(-0500)] <cindyli> moreover, heidi, other than the dropdowns, other parts of the ui look great in browsers other than IE. the descriptions for the second checkboxes in the last 2 sections were wrapped and not displayed in IE
[10:12:56 CDT(-0500)] <colinclark> I'm sort of in the midst of a little personal demo sprint
[10:13:07 CDT(-0500)] <colinclark> for the conference presentation Justin_o and I are giving tomorrow
[10:13:07 CDT(-0500)] <cindyli> i was using full page with preview
[10:13:22 CDT(-0500)] <heidi> cindyli cool yeah, still a bit of tweaking/testing to do
[10:13:26 CDT(-0500)] <colinclark> jhung: Can I postpone for a bit, while I try to finish... errr, rather, start, this demo?
[10:13:42 CDT(-0500)] <heidi> but good to hear we're close!
[10:13:50 CDT(-0500)] <jhung> colinclark: no prob. I'm going to start with some styling work on that, if that's cool with you.
[10:13:50 CDT(-0500)] <cindyli> great, as long as it's on ur list. thanks, heidi
[10:14:07 CDT(-0500)] <colinclark> jhung: Go for it, yes!
[10:14:15 CDT(-0500)] <colinclark> cindyli knows that code and markup pretty well, too
[10:14:17 CDT(-0500)] <jhung> cool
[10:14:18 CDT(-0500)] <colinclark> having written most of it (wink)
[10:14:34 CDT(-0500)] <jhung> colinclark: okay. I'll ping cindyli if needed.
[10:15:01 CDT(-0500)] <cindyli> ya, jhung, let me know if u think anything i can help.
[10:15:13 CDT(-0500)] <jhung> thanks!
[10:15:18 CDT(-0500)] <cindyli> np
[10:49:03 CDT(-0500)] <michelled> cindyli, heidi, mlam: I think it would be good if we could make a quick list of what we should check when we integrate into the 4267 branch.
[10:49:13 CDT(-0500)] <michelled> I'm not certain what the state of everything is expected to be
[10:49:20 CDT(-0500)] <michelled> so, should the tests all pass at this point?
[10:49:54 CDT(-0500)] <mlam> I think the tests should always pass, michelled.
[10:50:26 CDT(-0500)] <heidi> as far as i know they should pass
[10:50:47 CDT(-0500)] <cindyli> i agree. but actually they are not. sorry
[10:51:24 CDT(-0500)] <cindyli> as said, we have an asynchronous template loading issue that fails the ui options tests
[10:51:55 CDT(-0500)] <cindyli> it has a separate jira and my next step
[10:52:20 CDT(-0500)] <cindyli> we have another jira regarding the ui options tests hang on chrome, ie, that is my next next step
[10:52:20 CDT(-0500)] <heidi> colinclark cindyli couldn't quite make out everything at stand up, but <option> can be styled... we can check how supported in our browsers it is. but regardless, i think no style on them would be better than trying to use the rich drop down plugin, which had in my opinion pretty serious accessibility issues, and we don't have time to refactor it
[10:52:31 CDT(-0500)] <colinclark> Sorry the audio sucked so much
[10:52:32 CDT(-0500)] <michelled> (smile)
[10:52:42 CDT(-0500)] <colinclark> heidi: What were the accessibility problems, heidi?
[10:52:45 CDT(-0500)] <michelled> cindyli: which of the demos should work right now?
[10:52:49 CDT(-0500)] <colinclark> And which version of the plugin were you using?
[10:52:59 CDT(-0500)] <colinclark> I've never had much luck in terms of styling a dropdown...
[10:53:03 CDT(-0500)] <cindyli> michelled: full page with preivew
[10:53:09 CDT(-0500)] <colinclark> you're saying the options inside the dropdown can be styled, though, heidi?
[10:53:17 CDT(-0500)] <cindyli> src/webapp/demos/uiOptions/FullPreviewUIOptions/html/uiOptions.html
[10:53:45 CDT(-0500)] <cindyli> as i rmb, heidi mentioned fat panel should be working too
[10:53:47 CDT(-0500)] <heidi> yes, but not sure if it works in all the browsers we support, but i think that's ok. if i recall correctly, the options weren't readable by screen readers
[10:53:54 CDT(-0500)] <heidi> with the rich plugin
[10:54:30 CDT(-0500)] <michelled> cindyli, heidi: Is there anything else that should be working right now in that branch?
[10:54:38 CDT(-0500)] <colinclark> That's probably a relatively straightforward ARIA fix
[10:54:45 CDT(-0500)] <colinclark> but do whatever seems easiest
[10:54:51 CDT(-0500)] <heidi> cindyli the panel isn't pretty right now as tabs aren't being applied to it. not sure if live preview is working
[10:54:52 CDT(-0500)] <colinclark> I'm cool either way
[10:55:48 CDT(-0500)] <heidi> colinclark the way you interacted with the dropdown was really different than the norm too, if i remember right. the way to open/choose things. don't think that's great. but yeah easiest would be to style with css for now.
[10:56:07 CDT(-0500)] <colinclark> heidi: You're sure that works on the Mac?
[10:56:31 CDT(-0500)] <cindyli> michelled: in summary, the things need to work: 3 demos that we are sure one is working, not other 2 though.
[10:56:36 CDT(-0500)] <cindyli> tests: ui options tests have problem, but tests for ui options and slider are working.
[10:56:44 CDT(-0500)] <cindyli> integration tests: fail
[10:56:53 CDT(-0500)] <heidi> colinclark styling options? works for ff and safari
[10:56:54 CDT(-0500)] <cindyli> sorry, integration demo
[10:57:00 CDT(-0500)] <colinclark> heidi: Cool
[10:57:36 CDT(-0500)] <michelled> thx cindyli - I'm going to comment on the JIRA with those expectations
[10:57:50 CDT(-0500)] <heidi> colinclark ultimately the rich dropdown allows a lot more customizations which would be rad, but just don't think we have time ... good thing to add later for sure
[10:58:01 CDT(-0500)] <colinclark> makes sense to me, heidi
[10:58:09 CDT(-0500)] <cindyli> sorry, michelled, another correction about tests: the working tests are ui enhancer and slider
[10:58:38 CDT(-0500)] <michelled> thx
[10:58:48 CDT(-0500)] <michelled> mlam: hadn't you merged something into the 4267 branch?
[10:59:10 CDT(-0500)] <mlam> I merged in the auto-save option
[10:59:21 CDT(-0500)] <michelled> what branch is that - it's not listed on the JIRA
[10:59:30 CDT(-0500)] <mlam> it's FLUID-4221
[10:59:35 CDT(-0500)] <mlam> it was on the UIO roadmap
[10:59:49 CDT(-0500)] <michelled> was it a branch in your repo?
[10:59:56 CDT(-0500)] <mlam> I didn't merge it in though. I just made the changes directly into the FLUID-4267 branch
[11:00:01 CDT(-0500)] <michelled> ok
[11:05:54 CDT(-0500)] <cindyli> heidi: colinclark, so, what's the conclusion for styling dropdown <option>?
[11:06:07 CDT(-0500)] <heidi> cindyli same as before, add in classnames
[11:06:12 CDT(-0500)] <colinclark> cindyli: heidi's the boss (smile)
[11:06:33 CDT(-0500)] <cindyli> ok, bosses:-D
[11:06:40 CDT(-0500)] <heidi> hehe
[11:17:58 CDT(-0500)] <michelled> cindyli, heidi, mlam, Justin_o, colinclark: Here's what I wrote on the JIRA about our expectations for the merge branch:
[11:18:05 CDT(-0500)] <michelled> * UI Enhancer and Slider tests pass
[11:18:06 CDT(-0500)] <michelled> * Full Preview UI Options demo is fully working
[11:18:06 CDT(-0500)] <michelled> * UI Options tests fail
[11:18:06 CDT(-0500)] <michelled> * Fat Panel UI Options demo is working in FF
[11:18:06 CDT(-0500)] <michelled> * Integration demos are not working
[11:18:11 CDT(-0500)] <michelled> does that look right to you?
[11:18:55 CDT(-0500)] <heidi> fat panel is not working - tabs aren't being applied. working on that now
[11:19:07 CDT(-0500)] <Justin_o> michelled: you mean current state?
[11:19:09 CDT(-0500)] <michelled> heidi: ok, I'll edit the comment
[11:19:13 CDT(-0500)] <michelled> Justin_o: yes
[11:19:16 CDT(-0500)] <Justin_o> okay
[11:19:23 CDT(-0500)] <heidi> michelled full without preview should be working too, but both need minor css tweaks still
[11:20:21 CDT(-0500)] <michelled> ok, updated current state is:
[11:20:21 CDT(-0500)] <michelled> * UI Enhancer and Slider tests pass
[11:20:22 CDT(-0500)] <michelled> * Full Preview UI Options demo is working
[11:20:22 CDT(-0500)] <michelled> * Full without preview demo is working
[11:20:22 CDT(-0500)] <michelled> * UI Options tests fail
[11:20:22 CDT(-0500)] <michelled> * Fat Panel UI Options demo is not working
[11:20:23 CDT(-0500)] <michelled> * Integration demos are not working
[11:22:20 CDT(-0500)] <heidi> michelled - looks right, good call on the status report for the branch!
[11:22:45 CDT(-0500)] <michelled> (smile)
[11:22:54 CDT(-0500)] <michelled> cindyli, heidi, Justin_o, mlam: when you push to the merge branch, please do the following 3 things:
[11:23:00 CDT(-0500)] <michelled> 1. make sure everything that was working is still working
[11:23:08 CDT(-0500)] <michelled> 2. update the JIRA to state what branch you've merged or if you made the change directly what JIRA it was for
[11:23:13 CDT(-0500)] <michelled> 3. comment on the JIRA with the branch expectations after your push
[11:23:29 CDT(-0500)] <heidi> michelled - can you add that to do list to the jira
[11:23:48 CDT(-0500)] <michelled> for sure (smile)
[11:24:03 CDT(-0500)] <heidi> cool (smile)
[11:36:19 CDT(-0500)] <EricDalquist> Bosmon: you have a few minutes for a pager/renderer question?
[11:50:04 CDT(-0500)] <heidi> anastasiac not sure if my old dev intro doc would help with explaining what a component is etc: http://wiki.fluidproject.org/display/fluid/Developer+Introduction+to+Infusion+Framework
[11:50:27 CDT(-0500)] <heidi> i hope to work on this some more soon, now that i've helped write components myself... i 'get it' a bit more
[11:50:31 CDT(-0500)] <anastasiac> heidi, thanks - that's the first link I directed care to (smile)
[11:50:37 CDT(-0500)] <heidi> ah cool
[11:50:51 CDT(-0500)] <heidi> still confusing tho huh?
[12:00:51 CDT(-0500)] <mlam> michelled: the UIO tests are passing, but only with the use of break points. There's a rendering error in which some markup isn't found . What can we do to allow the component set up in our tests to finish before running a test?
[12:01:33 CDT(-0500)] <michelled> mlam: I think cindyli is working on a fix for that
[12:01:48 CDT(-0500)] <michelled> otherwise you should be able to use qunit stop and start
[12:01:56 CDT(-0500)] <cindyli> yes, mlam
[12:01:58 CDT(-0500)] <mlam> ok, thanks
[12:10:13 CDT(-0500)] <yura_> care: http://nightly.collectionspace.org:8180/collectionspace/ui/html , https://source.collectionspace.org/collection-space/src/ui/trunk/
[12:12:18 CDT(-0500)] <care> ty
[13:04:19 CDT(-0500)] <lahabana> hi everybody
[13:05:26 CDT(-0500)] <lahabana> I've got a question about FSS for components
[13:08:00 CDT(-0500)] <anastasiac> care: http://wiki.fluidproject.org/display/fluid/How+to+Create+a+Fluid+Component
[13:08:10 CDT(-0500)] <care> tx
[13:08:17 CDT(-0500)] <lahabana> thx
[13:11:21 CDT(-0500)] <jhung> cindyli, justin_o: about the image uploader demo, when does it need to be done? Reason I ask is because I don't have a server to test on and I will be in the office tomorrow...
[13:12:54 CDT(-0500)] <cindyli> jhung: in bug parade period that literally ends this friday, maybe?
[13:14:00 CDT(-0500)] <jhung> cindyli: hmm okay. I'll wait for justin_o, or colinclark to respond.
[13:14:06 CDT(-0500)] <jhung> ^speaking of the devel. (big grin)
[13:14:22 CDT(-0500)] <jhung> devil... although "devel" works too.
[13:14:29 CDT(-0500)] <cindyli> haha
[13:14:41 CDT(-0500)] <cindyli> yes, they are in better positions to answer
[13:15:03 CDT(-0500)] <jhung> cindyli, i'm thinking that if you're free tomorrow morning, we can get it done quickly.
[13:15:18 CDT(-0500)] <cindyli> certainly. my pleasure
[13:15:33 CDT(-0500)] <colinclark> fluid-everyone: Any suggestions for sites you think are particularly cool examples of HTML5 in action?
[13:15:33 CDT(-0500)] <colinclark> We
[13:15:33 CDT(-0500)] <colinclark> '
[13:15:40 CDT(-0500)] <colinclark> There's certainly a lot
[13:15:45 CDT(-0500)] <colinclark> send me your favourites
[13:15:51 CDT(-0500)] <colinclark> for our presentation tomorrow
[13:16:52 CDT(-0500)] <michelled> colinclark: I was looking at meyerweb yesterday and he did a post on HTML5 examples: http://meyerweb.com/eric/thoughts/2011/04/14/my-own-private-html5-survey/
[13:17:23 CDT(-0500)] <jhung> colinclark: the image uploader demo. Can it wait until tomorrow morning? I don't have a server to test on, and I will be in the office. cindyli and I can wrap it in the morning.
[13:17:54 CDT(-0500)] <colinclark> sure
[13:18:47 CDT(-0500)] <jhung> colinclark: coolness. cindyli, so we'll pair tomorrow morning on this. (smile)
[13:19:11 CDT(-0500)] <Justin_o> jhung: just needs to be ready in time for testing
[13:19:12 CDT(-0500)] <cindyli> sure, jhung
[13:19:52 CDT(-0500)] <jhung> justin_o: roger that. It will be ready.
[13:21:04 CDT(-0500)] <Justin_o> jhung: excellent (smile)
[13:22:28 CDT(-0500)] <michelled> cindyli: after your last commit did the UIEnhancer tests work?
[13:22:53 CDT(-0500)] <cindyli> whoa, didn't try it out. sorry
[13:23:01 CDT(-0500)] <cindyli> trying now, michelled
[13:23:05 CDT(-0500)] <michelled> ok
[13:24:25 CDT(-0500)] <michelled> also, did you intend to do type coercion on line 107?
[13:24:41 CDT(-0500)] <cindyli> not working, sigh..
[13:25:42 CDT(-0500)] <cindyli> michelled: what's wrong with that line?
[13:26:06 CDT(-0500)] <michelled> I was wondering if you intended to use '==' instead of '==='
[13:26:29 CDT(-0500)] <cindyli> ah, perfect. that's an issue. correcting. thanks!
[13:26:29 CDT(-0500)] <michelled> the double equal does type coercion
[13:27:15 CDT(-0500)] <cindyli> yes, slipped out of my attention.
[13:30:33 CDT(-0500)] <Bosmon> EricDalquist - now I do!
[13:33:42 CDT(-0500)] <Bosmon> ERRIC THER HALF-A-BEE!!
[13:44:17 CDT(-0500)] <michelled> cindyli, heidi: the full preview UI Options has a js file that it never loads and has lots of js in the template
[13:44:37 CDT(-0500)] <heidi> michelled which file?
[13:44:42 CDT(-0500)] <heidi> oh
[13:44:59 CDT(-0500)] <heidi> i know what you're talking about - yeah that's all going to change once we add the "flavours" (similar to reorderers) of UIO
[13:45:13 CDT(-0500)] <heidi> the demo will just call fluid.fullPreviewUIOptions(); then
[13:45:36 CDT(-0500)] <michelled> heidi: so for now you expect the js in the template to be the start up script
[13:45:37 CDT(-0500)] <michelled> ?
[13:46:00 CDT(-0500)] <heidi> yeah, i'm not sure why it was done that way vs. in the js file, but we'll change it anyway
[13:46:20 CDT(-0500)] <michelled> so what's the script in the uiOptions.js then?
[13:46:29 CDT(-0500)] <michelled> heidi: is that meant 'for the future'
[13:46:31 CDT(-0500)] <michelled> ?
[13:46:36 CDT(-0500)] <heidi> michelled not sure
[13:46:43 CDT(-0500)] <heidi> i think the script in the html should be in the js
[13:47:19 CDT(-0500)] <michelled> cindyli: do you know?
[13:48:06 CDT(-0500)] <cindyli> michelled: one sec, let me have a look
[13:48:54 CDT(-0500)] <michelled> looks like a copy paste thing
[13:48:59 CDT(-0500)] <cindyli> michelled: ic, that js was from the old and removed ui options demo
[13:49:02 CDT(-0500)] <michelled> the js actually has sliding panel stuff in there
[13:49:13 CDT(-0500)] <michelled> let's try not to mess up this branch like this
[13:49:21 CDT(-0500)] <michelled> it's going to be really hard to code review this
[13:49:30 CDT(-0500)] <cindyli> haha, agree
[13:50:05 CDT(-0500)] <cindyli> back to that js, i think we should use it.
[13:50:29 CDT(-0500)] <cindyli> because the current demo is more like the old standalone demo, without really applying settings to the whole page
[13:50:58 CDT(-0500)] <cindyli> this js would make the demo more like a real-world case. what do u think, michelled and heidi
[13:51:28 CDT(-0500)] <michelled> I think we should try not to put javascript into the html files (smile)
[13:51:35 CDT(-0500)] <heidi> cindyli it will all be replaced by fluid.fullPreviewUIOptions();
[13:51:35 CDT(-0500)] <michelled> so I'm all for using the js file
[13:51:47 CDT(-0500)] <heidi> and if it's just one line, i think putting it at the bottom is ok?
[13:52:12 CDT(-0500)] <michelled> will it also require the 30 lines of demands though?
[13:52:15 CDT(-0500)] <cindyli> oh, that's the plan?! ok. we can get rid of it then
[13:52:31 CDT(-0500)] <heidi> michelled there will be a FullPreviewUIOptions.js in components
[13:52:36 CDT(-0500)] <heidi> that it will include
[13:53:05 CDT(-0500)] <michelled> and the demands will be in there heidi?
[13:53:11 CDT(-0500)] <heidi> yep
[13:53:21 CDT(-0500)] <michelled> ok
[13:53:45 CDT(-0500)] <cindyli> with the current structure, we do need lots of demands, one template each at least
[14:52:55 CDT(-0500)] <Bosmon> cindyli - we shouldn't need one demand per template, unless the user is overriding each one individually
[14:53:00 CDT(-0500)] <Bosmon> There just needs to be an option per template
[14:53:46 CDT(-0500)] <cindyli> Bosmon: that's possible, right?
[14:53:52 CDT(-0500)] <Bosmon> I believe so, yes
[14:53:59 CDT(-0500)] <cindyli> not each of the templates, but one or two
[14:54:16 CDT(-0500)] <Bosmon> Well, there needs to be a COMPONENT per template - but those can just be written out inline
[14:54:40 CDT(-0500)] <Bosmon> But not a demands block per template in the original implementation
[14:54:56 CDT(-0500)] <cindyli> oh, ic ic
[14:55:29 CDT(-0500)] <Bosmon> Although I guess this comes back to our last Friday's discussion "when should I write a demands block, rather than a compound tree of options"
[14:55:55 CDT(-0500)] <Bosmon> To which one answer is just one about readability... files with large fistfuls of demands blocks are hard to get around
[14:56:24 CDT(-0500)] <cindyli> agree.
[14:56:51 CDT(-0500)] <cindyli> how to write out inline?
[14:57:02 CDT(-0500)] <Bosmon> Well, just with subcomponents and options
[14:57:34 CDT(-0500)] <Bosmon> I'm sorry I didn't review your impl in too much detail yet - is the latest checked in somewhere?
[14:58:01 CDT(-0500)] <Bosmon> One way of doing it might be to make a structure like
[14:58:02 CDT(-0500)] <cindyli> one sec, let me dig out
[14:58:05 CDT(-0500)] <Bosmon> components: {
[14:58:09 CDT(-0500)] <Bosmon> fooTemplateLoader: {
[14:58:16 CDT(-0500)] <Bosmon> type: "templateLoader",
[14:58:28 CDT(-0500)]

<Bosmon> options:

Unknown macro: { .... fooTemplateLoaderOptions }

[14:58:28 CDT(-0500)] <Bosmon> etc.
[14:58:45 CDT(-0500)] <Bosmon> Then people can just issue demands blocks against ["fluid.UIOptions", "fooTemplateLoader"]
[14:58:57 CDT(-0500)] <cindyli> ah. cool
[14:59:00 CDT(-0500)] <Bosmon> Remember that a MEMBER name can be context-forming in a demands block as well as a type name
[14:59:26 CDT(-0500)] <cindyli> that's right.
[14:59:27 CDT(-0500)] <cindyli> btw, the latest: https://github.com/michelled/infusion/blob/FLUID-4267/src/webapp/components/uiOptions/js/UIOptions.js
[14:59:32 CDT(-0500)] <Bosmon> Thanks
[14:59:40 CDT(-0500)] <cindyli> thank YOU
[15:00:48 CDT(-0500)] <Bosmon> I see there is still lots of UIEnhancer material here - is that planned for a different branch?
[15:01:07 CDT(-0500)] <cindyli> yes, michelled's working on a bunch of jiras for that
[15:01:11 CDT(-0500)] <Bosmon> ok, cool
[15:01:24 CDT(-0500)] <Bosmon> So this branch is targetted at ... template loading.... and what else?
[15:01:42 CDT(-0500)] <cindyli> for all
[15:02:22 CDT(-0500)] <michelled> Bosmon: this branch is the merge branch for all the ongoing uio work
[15:02:26 CDT(-0500)] <cindyli> this is a big merging branch from all other branches that different ppl have completed
[15:02:30 CDT(-0500)] <michelled> http://issues.fluidproject.org/browse/FLUID-4267
[15:02:49 CDT(-0500)] <cindyli> the one targetted for template loading is in my github
[15:02:56 CDT(-0500)] <cindyli> one sec
[15:03:11 CDT(-0500)] <cindyli> actually, almost same UIOptions.js
[15:03:14 CDT(-0500)] <heidi> cindyli your template loading changes will affect how i'm doin stuff so keep me posted if things change!
[15:03:23 CDT(-0500)] <cindyli> sure, heidi
[15:05:18 CDT(-0500)] <cindyli> Bosmon: branch for template loading - https://github.com/cindyli/infusion/tree/FLUID-4234
[15:05:51 CDT(-0500)] <Bosmon> Oh wow
[15:05:59 CDT(-0500)] <Bosmon> Direct transfer of code back from CSpace (tongue)
[15:07:24 CDT(-0500)] <Bosmon> And perhaps not some of the best CSpace code, either (tongue) .....
[15:08:25 CDT(-0500)] <cindyli> oh, no
[15:08:25 CDT(-0500)] <Bosmon> Ok - so, what I suggest is this... this original style was written in CSpace before we had the possibility for "direct injection"
[15:08:43 CDT(-0500)] <Bosmon> I would take the "fluid.specBuilder" components and turn them into GENUINE subcomponents of UIOptions
[15:09:06 CDT(-0500)] <Bosmon> And then in the "resources" block inject them from there....
[15:09:30 CDT(-0500)] <Bosmon> Unless the specBuilders are genuine subcomponents, noone could write demands blocks which target them
[15:09:42 CDT(-0500)] <Bosmon> Since if they only exist within "expanders" they are destroyed before anyone gets a chance to see them
[15:10:22 CDT(-0500)] <cindyli> ok
[15:10:24 CDT(-0500)] <Bosmon> It's interesting that I had already made specBuilder at least some KIND of component, but it really needs to be an even more proper one
[15:10:36 CDT(-0500)] <Bosmon> You should get rid of all that weird "fluid.invoke" junk which is lying around in there (tongue)
[15:10:48 CDT(-0500)] <cindyli> haha
[15:10:49 CDT(-0500)] <Bosmon> Remember that this is practically prehistoric, almost pre-IoC code
[15:10:58 CDT(-0500)] <Bosmon> So don't take the particular strategy you see there as a reliable guide
[15:11:55 CDT(-0500)] <Bosmon> I imagine this was written some time like... perhaps, last November, yura_?
[15:13:13 CDT(-0500)] <Bosmon> So, in your "resources" block you should just write something like this:
[15:13:16 CDT(-0500)] <Bosmon> resources: {
[15:16:11 CDT(-0500)]

<Bosmon> fooTemplate: "

Unknown macro: {uiOptionsTemplateLoader}

.foo.template"


[15:16:14 CDT(-0500)] <Bosmon> Something like this
[15:16:24 CDT(-0500)] <Bosmon> You will need to put all the template loader subcomponents into a different component somewhere
[15:16:37 CDT(-0500)] <Bosmon> To avoid load-time issues
[15:23:03 CDT(-0500)] <cindyli> Bosmon: have a few things to clarify
[15:23:39 CDT(-0500)] <Bosmon> cindyli - sure
[15:23:40 CDT(-0500)] <cindyli> all the templates will be from uiOptionsTemplateLoader, so one demand block is enough
[15:23:56 CDT(-0500)] <cindyli> right?
[15:25:03 CDT(-0500)] <Bosmon> Certainly there can be a one-demand-block version, yes
[15:25:09 CDT(-0500)] <cindyli> these templates will be injected into each of template loader component where it's needed
[15:25:13 CDT(-0500)] <Bosmon> But are you referring to the integrator of the component, or the author?
[15:25:22 CDT(-0500)] <cindyli> author
[15:25:33 CDT(-0500)] <Bosmon> author in theory gets away with zero demand blocks
[15:25:36 CDT(-0500)] <Bosmon> Unless they really want one
[15:25:49 CDT(-0500)] <cindyli> understand
[15:27:01 CDT(-0500)] <cindyli> what i mean is, for instant, in the "resources" block of "textControls" i will have,
[15:27:40 CDT(-0500)] <cindyli> template: {
[15:27:40 CDT(-0500)]

<cindyli> url: "

Unknown macro: {uiOptionsTemplateLoader}

.options.templates.textTemplate"


[15:27:40 CDT(-0500)] <cindyli> }
[15:29:41 CDT(-0500)] <Bosmon> Yes, that is possible
[15:30:05 CDT(-0500)] <Bosmon> Although I think we were proposing a model where these URLs didn't go through "options" but were in fact derived through a subcomponent of the uiOptionsTemplateLoader?
[15:30:17 CDT(-0500)] <Bosmon> We want to be able to use a proper subcomponent to get the work done of looking up the URL
[15:30:22 CDT(-0500)] <Bosmon> So that the user has something to issue a demands block against
[15:31:12 CDT(-0500)] <cindyli> ok, not the options of the template loader component
[15:31:21 CDT(-0500)] <Bosmon> Right
[15:31:28 CDT(-0500)] <Bosmon> We imagine the "template loader component" is just a shell
[15:31:33 CDT(-0500)] <Bosmon> As so many of these IoC-driven components are
[15:31:56 CDT(-0500)] <Bosmon> It contains a batch of these components that we imagined, that are derived from cleaning up the "fluid.specBuilder" components
[15:32:04 CDT(-0500)] <Bosmon> So that they become genuine components again
[15:32:14 CDT(-0500)] <cindyli> so, we make use the same idea of url expander but turning it into a component that takes multiple template urls instead of relative path
[15:32:28 CDT(-0500)] <Bosmon> Just one URL
[15:32:33 CDT(-0500)] <Bosmon> I mean, just one URL per instance
[15:32:43 CDT(-0500)] <Bosmon> Each subcomponent is responsible for resolving one of the URLs that UIOptions requires
[15:32:44 CDT(-0500)] <cindyli> yes
[15:33:38 CDT(-0500)]

<cindyli> when u say *resolving", do u mean injecting the template via "

Unknown macro: {uiOptionsTemplateLoader}

.templates.textTemplate


[15:33:45 CDT(-0500)] <cindyli> or calling fetchResource()
[15:34:06 CDT(-0500)] <cindyli> calling fetchResouce() should still happen only once at "fluid.uiOptions", right?
[15:34:10 CDT(-0500)] <Bosmon> Well, neither - although both of these things happen in the workflow
[15:34:12 CDT(-0500)] <Bosmon> Yes, that's correct
[15:34:31 CDT(-0500)] <cindyli> ok
[15:34:33 CDT(-0500)] <Bosmon> The "specBuilder" does some kind of "magic work" inside itself to derive the URL, which is what I mean by "resolving" ...
[15:34:47 CDT(-0500)] <Bosmon> And if the user wants to change the "magic work", they can write a demands block targetted at just this component
[15:34:49 CDT(-0500)] <cindyli> understood
[15:35:33 CDT(-0500)] <cindyli> cool. i will polish up the code. thanks, Bosmon