fluid-work IRC Logs-2011-07-07

[08:24:21 CDT(-0500)] <heidi_> Justin_o i finished UIO testing w/ our components fyi. aside from several theming issues (cos our components need to use more fss!), the only biggie i found was with the browse/add more button in uploader. i think the size of it is fixed so when text size/line spacing is increased, it gets cut off and is no longer useable
[08:26:22 CDT(-0500)] <Justin_o> heidi_: (sad) that's a shame... is that possible to fix easily at all?
[08:26:51 CDT(-0500)] <heidi_> Justin_o i'm not sure cos i'm fuzzy on how the layering of that button works. i'm guessing tho, if you set the w/h to em's instead of px that would do it
[08:27:29 CDT(-0500)] <heidi_> Justin_o shall i file a jira for this and mark it a blocker?
[08:27:58 CDT(-0500)] <Justin_o> heidi_: please file a jira for it... we should probably chat with mlam and colinclark about it.. i guess file it as a blocker for now.. and we can readjust if needed
[08:28:09 CDT(-0500)] <heidi_> k
[08:28:54 CDT(-0500)] <heidi_> Justin_o and there's one theming issue that is sort of bad with pager - the hover over the page #s is invisible for all themes
[08:29:03 CDT(-0500)] <heidi_> that text
[08:29:25 CDT(-0500)] <Justin_o> you mean the tooltip that shows the range of items per page?
[08:30:51 CDT(-0500)] <heidi_> Justin_o yep
[08:31:26 CDT(-0500)] <Justin_o> heidi_: (sad) I think that should all come from the jquery ui theme
[08:31:34 CDT(-0500)] <Justin_o> i guess they're missing something
[08:34:15 CDT(-0500)] <heidi_> Justin_o i'll try to figure out what the class name is and i'll file a jira for that one too.... the other stuff i found i'll add to the testing jira, but think it will mostly be solved once we have our infusion theme/fss components in 1.5 or whenever
[08:45:00 CDT(-0500)] <heidi_> Justin_o http://issues.fluidproject.org/browse/FLUID-4326
[08:45:13 CDT(-0500)] <Justin_o> heidi_: great.. thanks
[08:45:33 CDT(-0500)] <Justin_o> heidi_: are you all wrapped up for the 1.4 release then..
[08:45:33 CDT(-0500)] <Justin_o> i
[08:45:50 CDT(-0500)] <Justin_o> guess you'll be needed to help with some of those issues you mentioned if they are left as blockers
[08:45:53 CDT(-0500)] <heidi_> Justin_o just going to rename the demo-theme, and then yes.
[08:46:37 CDT(-0500)] <Justin_o> heidi_: great.. well let me know if you are looking for anything to do.. i guess you'll be busy with other stuff though
[08:46:41 CDT(-0500)] <heidi_> Justin_o i'll change the UIO test page blocker to 'won't fix' for now since it's tricky. the testing was done which was the blockery part
[08:47:05 CDT(-0500)] <Justin_o> heidi_: okay.. thanks..
[08:47:24 CDT(-0500)] <Justin_o> i guess maybe file issues for the rest or comment on the infusion theme one
[08:47:34 CDT(-0500)] <heidi_> Justin_o not sure if you saw my comment about the scrollbar in fat panel w/ live preview
[08:47:49 CDT(-0500)] <Justin_o> heidi_: nope.. i don't think i did
[08:48:01 CDT(-0500)] <Justin_o> what's wrong
[08:48:09 CDT(-0500)] <Justin_o> is it that you get scrolling in the fatpanel?
[08:48:10 CDT(-0500)] <heidi_> Justin_o i merged in yr/mike's live preview work and noticed a scroll bar on the right side that shouldn't be there by default
[08:48:19 CDT(-0500)] <heidi_> in the fat panel itself
[08:48:21 CDT(-0500)] <Justin_o> hmm.. haven't seen that
[08:48:31 CDT(-0500)] <Justin_o> did you have any preferences set?
[08:48:34 CDT(-0500)] <heidi_> nope
[08:48:40 CDT(-0500)] <Justin_o> weird
[08:48:46 CDT(-0500)] <heidi_> i think mike had it too
[08:48:51 CDT(-0500)] <Justin_o> oh really
[08:48:59 CDT(-0500)] <Justin_o> okay.. i'll have to check in with him on that too i guess
[08:49:05 CDT(-0500)] <Justin_o> he's not in yet unfortunately
[08:49:12 CDT(-0500)] <heidi_> k
[08:55:17 CDT(-0500)] <Justin_o> huslage: i'm having some problems trying to moderate the Infusion-User's list
[08:55:29 CDT(-0500)] <Justin_o> i can log in and see the message, but can't seem to do anything with it
[08:55:35 CDT(-0500)] <huslage> what's the error?
[08:56:52 CDT(-0500)] <Justin_o> huslage: i want to discard a message.. so i select the "Discard" option and click the submit button, but it doesn't do anything.. it just sends me back to the main page
[08:57:25 CDT(-0500)] <huslage> ok Justin_o email me the URL and I'll look at it when I get back. i have to run to the bank
[08:58:16 CDT(-0500)] <Justin_o> huslage: sure thing.. thanks
[08:58:20 CDT(-0500)] <huslage> L)
[08:58:22 CDT(-0500)] <huslage> (smile)
[08:59:55 CDT(-0500)] <heidi_> Justin_o do you think "make inputs larger" should affect simple inline edit text areas ? it doesn't now
[09:01:27 CDT(-0500)] <Justin_o> heidi_: you mean when in edit mode
[09:01:30 CDT(-0500)] <heidi_> jameswy too ^
[09:01:37 CDT(-0500)] <heidi_> Justin_o i guess? not sure
[09:02:08 CDT(-0500)] <Justin_o> heidi_: i'm curious what james' thoughts on that would be, since he wants that to be the same size in both edit and view mode
[09:02:31 CDT(-0500)] <heidi_> just seems like an "input" and therefore should be affected
[09:02:58 CDT(-0500)] <heidi_> i don't think it's a blocker or anything, but maybe worth noting in a jira
[09:05:03 CDT(-0500)] <Justin_o> heidi_: yes.. good to file a jira for it
[09:05:16 CDT(-0500)] <heidi_> Justin_o see what jameswy thinks first...
[09:05:49 CDT(-0500)] <Justin_o> heidi_: up to you, you can file the jira first and close it if necessary.. or you can wait to see what james' says
[09:05:57 CDT(-0500)] <heidi_> k
[09:07:02 CDT(-0500)] <heidi_> Justin_o the hovers over page numbers are "tooltips" ?
[09:07:14 CDT(-0500)] <Justin_o> heidi_: yes
[09:07:28 CDT(-0500)] <heidi_> thanks
[09:08:23 CDT(-0500)] <jameswy> heidi_: That's a great question. I think this is an exceptional case where "Make inputs larger" should affect inline edit's appearance. "Make inputs larger" is intended to make inputs more easily interactable and visible, but in the case of inline edit, the input is practically equivalent to the text itself.
[09:08:33 CDT(-0500)] <jameswy> (Justin_o too ^)
[09:09:18 CDT(-0500)] <heidi_> jameswy okay, i'll file a jira for that then, thanks jameswy
[09:10:05 CDT(-0500)] <jameswy> So, in this case, I think the user would expect inline edit elements to be affected by text style adjustments and not the "Make inputs larger".
[09:10:18 CDT(-0500)] <jameswy> heidi_ ^
[09:10:36 CDT(-0500)] <heidi_> ahh... okay
[09:10:42 CDT(-0500)] <heidi_> hmm
[09:11:05 CDT(-0500)] <heidi_> jameswy your first line you said "I think this is an exceptional case where "Make inputs larger" should affect inline edit's appearance"
[09:11:08 CDT(-0500)] <heidi_> did you mean shouldn't ?
[09:11:20 CDT(-0500)] <jameswy> Aish, yes, typo.
[09:11:29 CDT(-0500)] <heidi_> haha okay. i was confused there
[09:11:51 CDT(-0500)] <jameswy> Worst kind of typo. The sort where I meant the exact opposite, (tongue)
[09:12:04 CDT(-0500)] <heidi_> so i won't file a jira ;P
[09:26:43 CDT(-0500)] <Justin_o_> jameswy: harris and I are still working on trying to get the ToC stuff working for when we have a one-to-one mapping of level to indentation
[09:26:59 CDT(-0500)] <Justin_o_> i think the last time we showed you we had the double bullets
[09:27:49 CDT(-0500)] <Justin_o> jameswy: we're still trying to work around this but it may not be possible to have it working perfectly across all browsers
[09:27:54 CDT(-0500)] <Justin_o> harriswong: ^
[09:31:10 CDT(-0500)] <jameswy> harriswong: How hard is the problem? (and where'd Justin_o go?)
[09:31:45 CDT(-0500)] <harriswong> jameswy: he is touring someone at the moment..
[09:32:29 CDT(-0500)] <harriswong> jameswy: we talked to antranig yesterday and justin_o said that we will have to rewrite the tree.
[09:33:25 CDT(-0500)] <harriswong> jameswy: then, we will hide the extra "li" with a "list-style-type:none"; but in IE6 and 7, there will be a gap
[09:33:52 CDT(-0500)] <jameswy> harriswong: I see... So, no known solution for IE6/7?
[09:34:47 CDT(-0500)] <harriswong> jameswy: don't have one as of now. To clairfy, the "gap" i mentioned is an empty line from the skipped one(s)
[09:36:31 CDT(-0500)] <harriswong> > Human
[09:36:32 CDT(-0500)] <harriswong> >> [empty line]
[09:36:32 CDT(-0500)] <harriswong> >>> CATT
[09:39:49 CDT(-0500)] <jameswy> harriswong: I see... Hm.
[09:40:21 CDT(-0500)] <jameswy> Not ideal at all. But, they're IE6/7 users... life isn't ideal for them anyways?
[09:40:39 CDT(-0500)] <jessm> ^ lol
[09:44:12 CDT(-0500)] <harriswong> jameswy: lol as long as both you and justin_o are fine with it; he did mention that we might have to just ship with that until the renderer can skip a level, or something like that.
[09:45:15 CDT(-0500)] <harriswong> jameswy: the only visually ugliness i see is when you have a h1 and a h6 immediately after it, you will then be skipping 5 lines on IE6/7
[09:46:41 CDT(-0500)] <jameswy> harriswong: Right, but any skip would be ugly. If you have a TOC that's consistent throughout except for one or two skips, those skips really stand out.
[09:48:07 CDT(-0500)] <harriswong> jameswy: true, but life wasn't ideal for them to begin with right? ;P
[09:48:53 CDT(-0500)] <jameswy> Haha. Exactly.
[09:51:28 CDT(-0500)] <harriswong> jameswy: we can do a negative padding/margin but it is more like a hack, it might affect other things too.
[10:00:11 CDT(-0500)] <cindyli> michelled: heidi_, just sent a pull request (https://github.com/fluid-project/infusion/pull/99) for 4324 to replace "reset" button with "reset and apply" in full w/o preview demo
[10:01:09 CDT(-0500)] <heidi_> thanks cindyli
[10:03:50 CDT(-0500)] <cindyli> np, heidi_
[10:04:29 CDT(-0500)] <heidi_> jessm jhung who's making the final decision about IDI back-end and when is that happening? jon did you play with concrete5 at all?
[10:06:02 CDT(-0500)] <jhung> heidi_: I think the decision will be made once we've explored the options. So right now it's looking like Media Wiki for the wiki, but the CMS is still being researched.
[10:06:20 CDT(-0500)] <heidi_> jhung is there a timeline for the research period?
[10:06:27 CDT(-0500)] <jhung> heidi_: huslage is going to make a Concrete 5 installation for us to play with.
[10:07:22 CDT(-0500)] <jhung> heidi_: maybe that's a jameswy question. I assume as soon as possible so we can begin implementing the designs that are already finished.
[10:07:47 CDT(-0500)] <heidi_> jhung do we have a date for when we want this site up?
[10:08:41 CDT(-0500)] <jhung> I think jameswy said early Sept. jessm, can you give a more specific date?
[10:09:18 CDT(-0500)] <heidi_> oh ok, that's good. i thought jameswy had said end of THIS month would mean... yeah decision should be made like today/tomorrow and then pedal to the metal (smile)
[10:09:49 CDT(-0500)] <jhung> heidi_: oh. My information is dated, so maybe you have more recent info than I do.
[10:10:53 CDT(-0500)] <jhung> heidi_: well, I think we can safely begin work on the wiki portion. Maybe that's a good place to start.
[10:11:18 CDT(-0500)] <heidi_> jhung yeah that sounds good. and we have mockups/content for that?
[10:11:21 CDT(-0500)] <jhung> It's also the portion of the site that will get the most traffic, so it makes sense if we start that now even if we haven't decided on a CMS.
[10:11:59 CDT(-0500)] <jhung> heidi_: content jessm may be able to provide. there are mockups... let me find them...
[10:12:23 CDT(-0500)] <jessm> heidi_: jhung: colinclark is working on a reply to that thread for backend
[10:12:44 CDT(-0500)] <jessm> there's a bit of thinking going into the piecing things together but ensuring they're decoupled meaningfully as we start
[10:12:52 CDT(-0500)] <jessm> heidi_: the date for the IDI site was end of June
[10:13:17 CDT(-0500)] <jessm> Sept. is for the main event press release and kick off event, we need the site up this month
[10:13:32 CDT(-0500)] <jessm> we've scoped out what will go up now and what will be built as we go
[10:13:37 CDT(-0500)] <jessm> it's not all at the same time
[10:13:43 CDT(-0500)] <jhung> heidi_: here's the wireframe for styling and colours http://wiki.fluidproject.org/display/fluid/IDI+website+mockups
[10:13:58 CDT(-0500)] <jessm> jhung: wrt content, yes, i'm on the hook for some, but the cluster leads and institution reps are too
[10:14:18 CDT(-0500)] <jhung> heidi, here's a mockup for the wiki portion http://wiki.fluidproject.org/display/fluid/IDI+Website+Wiki+-+Clusters
[10:14:35 CDT(-0500)] <jhung> heidi, this too http://wiki.fluidproject.org/display/fluid/IDI+Website+Wiki+-+Cluster+Page
[10:14:37 CDT(-0500)] <heidi_> jessm so does jhung's suggestion of getting the wiki going asap sound like a good place to start? i can wrap up fluid and start getting into it this aft
[10:15:40 CDT(-0500)] <heidi_> jhung thanks for the links, i'll take a look
[10:16:18 CDT(-0500)] <jessm> heidi_: check with colinclark first re: the architectural vision
[10:16:26 CDT(-0500)] <jessm> heidi_: after that i'm sure we can get to a plug-n-chug
[10:16:29 CDT(-0500)] <jhung> heidi: no prob. Do you have the document about the research clusters? That's basically how the wiki will be structured and administered.
[10:16:33 CDT(-0500)] <jessm> on the designs and the backend
[10:16:43 CDT(-0500)] <heidi_> jhung i don't have that
[10:16:49 CDT(-0500)] <heidi_> i don't think
[10:16:57 CDT(-0500)] <jhung> heid_: okay, I'll email that to you.
[10:17:02 CDT(-0500)] <jhung> ^heidi
[10:17:08 CDT(-0500)] <heidi_> jessm okay cool i'll wait to hear what colinclark suggests
[10:17:20 CDT(-0500)] <heidi_> and look over these wireframes/content in the meantime
[10:21:43 CDT(-0500)] <jhung> heidi_ email coming your way. Feel free to ping me if you want to go over this stuff.
[10:22:11 CDT(-0500)] <heidi_> jhung thanks
[10:24:27 CDT(-0500)] <heidi_> jessm re: the scoping what goes up now, and what gets built as we go - is that in the wiki anywhere?
[10:25:04 CDT(-0500)] <jessm> heidi_: i think jhung put some priorities together?
[10:25:20 CDT(-0500)] <jessm> heidi_: the design was done with teh priorities in mind too
[10:26:13 CDT(-0500)] <heidi_> ok
[10:30:24 CDT(-0500)] <jessm> heidi_: the basic idea is to create the space, the ability for folks to connect and to leave the scaffolding open enough to accommodate the more "advanced" features we'll need to build into it
[10:30:37 CDT(-0500)] <jessm> we also need to build it as self-sustaining as possible
[10:30:55 CDT(-0500)] <jessm> keeping in mind considerations for upgrades, etc. but i think colinclark is going to wax poetic about that
[10:30:59 CDT(-0500)] <jessm> so, i'll zip it
[10:31:11 CDT(-0500)] <colinclark> lol
[10:31:15 CDT(-0500)] <colinclark> no pressure, colinclark
[10:31:17 CDT(-0500)] <colinclark> (tongue)
[10:31:27 CDT(-0500)] <heidi_> hehe
[10:32:17 CDT(-0500)] <jessm> (big grin)
[11:16:23 CDT(-0500)] <anastasiac> colinclark, can you clarify a point about the Uploader's dependency on ModelTransformation? It's only required with the backward compatibility stuff, and it should never be included in MyInfusion, right?
[11:16:35 CDT(-0500)] <anastasiac> oh, colinclark isn't here right now...
[11:17:43 CDT(-0500)] <anastasiac> colinclark, can you clarify a point about the Uploader's dependency on ModelTransformation? It's only required with the backward compatibility stuff, and it should never be included in MyInfusion, right?
[11:20:01 CDT(-0500)] <colinclark> sorry, in a meeting
[11:20:07 CDT(-0500)] <colinclark> but i can respond later
[11:20:16 CDT(-0500)] <anastasiac> k, thanks - sorry about that, i forgot
[11:20:35 CDT(-0500)] <colinclark> So, I believe ModelTransformation will be built into any custom framework build
[11:20:45 CDT(-0500)] <colinclark> Uploader has a series of *Compatibility.js files
[11:20:45 CDT(-0500)] <colinclark> th
[11:20:52 CDT(-0500)] <colinclark> those should never be included in builds
[11:21:01 CDT(-0500)] <colinclark> users should link them in as needed
[11:21:11 CDT(-0500)] <colinclark> so we don't want them automatically linked
[11:21:22 CDT(-0500)] <anastasiac> ok, that's what I'm seeing. thanks for the confirmation.
[11:21:34 CDT(-0500)] <anastasiac> I'll clarify the language int he uploader readme
[11:21:38 CDT(-0500)] <anastasiac> it's not quite right
[11:21:43 CDT(-0500)] <colinclark> by the way, never apologize for pinging me in the channel
[11:21:46 CDT(-0500)] <colinclark> even when i'm in a meeting
[11:21:48 CDT(-0500)] <colinclark> it's fine
[11:21:52 CDT(-0500)] <colinclark> i multitask (smile)
[11:21:59 CDT(-0500)] <anastasiac> really???
[11:23:51 CDT(-0500)] <colinclark> (tongue)
[11:29:59 CDT(-0500)] <jessm> anastasiac: i'm curious, so i'll make sure - - this readme you have in your repo is for 1.4 in particular, yes?
[11:30:16 CDT(-0500)] <anastasiac> jessm, yes, that's the idea
[11:30:41 CDT(-0500)] <jessm> anastasiac: so, i'll inevitably kick up a convo we've already had, but here goes anyway
[11:30:44 CDT(-0500)] <jessm> https://github.com/fluid-project/infusion/blob/infusion-1.3.1/README.txt
[11:30:54 CDT(-0500)] <jessm> that's the infusion 1.3 readme that shipped, right?
[11:31:21 CDT(-0500)] <anastasiac> yes
[11:32:04 CDT(-0500)] <jessm> so, i'm going to go out on a limb and not outright advocate for copy/paste, but suggest that readmes can be constructed very closely to the readme that came before them
[11:32:16 CDT(-0500)] <jessm> so, 1.4 i'd imagine would start the same way, have the same headings, etc.
[11:32:22 CDT(-0500)] <anastasiac> jessm, normally, yes. but since then we've redesigned the readme
[11:32:38 CDT(-0500)] <jessm> hrm, was that part of our "do we need two readmes" convo?
[11:32:51 CDT(-0500)] <anastasiac> we now have a readme that is relatively generic describing the project itself and a "release notes" that is specific to the release
[11:32:55 CDT(-0500)] <jessm> i'm sorry, i'm probably forgetting something i myself said
[11:33:01 CDT(-0500)] <jessm> right
[11:33:03 CDT(-0500)] <jessm> ok, thanks
[11:33:16 CDT(-0500)] <anastasiac> you'll see most of what was in the old readme is now in the release notes, jessm
[11:33:25 CDT(-0500)] <jessm> that would explain why it looks so different
[11:33:42 CDT(-0500)] <jessm> anastasiac: are the release notes in draft too yet?
[11:33:43 CDT(-0500)] <anastasiac> the only thing release specific in the readme is the "what are we working on now" section - that's the only thing that would change from release to release
[11:33:51 CDT(-0500)] <jessm> yes
[11:34:01 CDT(-0500)] <jessm> done so we wouldn't have to constantly tweak two docs
[11:34:04 CDT(-0500)] <anastasiac> jessm, I have done my best to update the release notes for 1.4, so yes, they're ready for review
[11:34:12 CDT(-0500)] <jessm> cool
[11:34:21 CDT(-0500)] <jessm> will you be so kind as to pass that url too?
[11:34:38 CDT(-0500)] <anastasiac> sure - they're right there beside the readme in my branch
[11:34:55 CDT(-0500)] <anastasiac> https://github.com/acheetham/infusion/blob/FLUID-4251-readmeReleaseNotes/ReleaseNotes.txt
[11:35:16 CDT(-0500)] <jessm> ah, my bad – now i see them
[11:35:17 CDT(-0500)] <jessm> thanks
[11:39:41 CDT(-0500)] <heidi_> hey Justin_o so fat panel's css has a bunch of jquery tab styling in it , and doesn't include the default-theme theme file. do you think i should strip it out of fat panel, and add that theme css dependency?
[11:40:09 CDT(-0500)] <heidi_> i like not having to include it, but it's also not great to have that bit of css copied
[11:40:10 CDT(-0500)] <heidi_> thoughts?
[11:40:37 CDT(-0500)] <Justin_o> heidi_: i think the fatpanel's css does need some refactoring.. for one the iframe and the parent page styles are mixed together..
[11:41:11 CDT(-0500)] <Justin_o> not sure exactly about what you mean about the fat panel tabs stuff..
[11:41:28 CDT(-0500)] <Justin_o> you want to move that into the default theme styling?
[11:41:44 CDT(-0500)] <heidi_> Justin_o the jquery ui tab styling that is in the default theme file is also in fatpanel.css
[11:42:00 CDT(-0500)] <heidi_> iframe and parent page styles?
[11:43:11 CDT(-0500)] <Justin_o> heidi_: okay so if it's duplicated i think we should remove it
[11:43:28 CDT(-0500)] <heidi_> Justin_o and add that extra dependency to fat panel
[11:43:43 CDT(-0500)] <Justin_o> yes... i think that makes sense
[11:43:47 CDT(-0500)] <heidi_> thing is i think including that theme file might mess up other stuff
[11:43:59 CDT(-0500)] <heidi_> since it has more than tab styling in it
[11:44:03 CDT(-0500)] <heidi_> i'm not sure
[11:44:20 CDT(-0500)] <Justin_o> heidi_: as for the parent and iframe stuff.. the sliding panel styling is mixed with the uiOptions styling ... one lives on the parent page, the other in the iframe.. so we should split these i think
[11:45:33 CDT(-0500)] <Justin_o> heidi_: what do the other jquery ui widgets on that page use?
[11:46:52 CDT(-0500)] <heidi_> Justin_o slider and that might be it.
[11:47:13 CDT(-0500)] <Justin_o> heidi_: okay.. does the slider have a jquery style sheet ?
[11:48:08 CDT(-0500)] <huslage> i return
[11:48:13 CDT(-0500)] <huslage> not quite alive
[11:48:38 CDT(-0500)] <heidi_> Justin_o i merged in FLUID-4307 to get fat panel working and see you've already created a fatpanel sliding panel css - is that what you mean?
[11:48:43 CDT(-0500)] <heidi_> huslage good morning (smile)
[11:49:03 CDT(-0500)] <huslage> hey heidi_
[11:49:12 CDT(-0500)] <huslage> did my email get out?
[11:49:15 CDT(-0500)] <huslage> i wasn't sure
[11:49:23 CDT(-0500)] <huslage> my phone crashed after i sent it
[11:49:31 CDT(-0500)] <heidi_> yep i got it
[11:49:34 CDT(-0500)] <huslage> k
[11:49:58 CDT(-0500)] <Justin_o> heidi_: hmm.. maybe don't remember making that
[11:50:20 CDT(-0500)] <heidi_> Justin_o maybe mlam made it? FatPanelSlidingPanel.css
[11:50:44 CDT(-0500)] <heidi_> why do you think they need to be seperate?
[11:50:45 CDT(-0500)] <mlam> heidi_: no, I didn't create the .css file
[11:51:06 CDT(-0500)] <heidi_> weird - magic file
[11:51:36 CDT(-0500)] <huslage> Justin_o ??
[11:51:38 CDT(-0500)] <Justin_o> heidi_: they should be separate because they aren't used together.. so we'd be loading in a large css file in the parent page and never using it
[11:51:46 CDT(-0500)] <Justin_o> huslage: hello
[11:51:51 CDT(-0500)] <huslage> msged you
[11:52:10 CDT(-0500)] <Justin_o> huslage: sorry.. missed that
[11:52:10 CDT(-0500)] <heidi_> Justin_o should both be used in the iframe, not parent?
[11:52:14 CDT(-0500)] <heidi_> *shouldn't
[11:52:20 CDT(-0500)] * huslage impatient (smile)
[11:52:49 CDT(-0500)] <Justin_o> heidi_: no.. the sliding panel is in the parent page
[11:53:00 CDT(-0500)] <heidi_> Justin_o ahh got it
[11:53:42 CDT(-0500)] <Justin_o> heidi_: okay.. do you think that's strange... should probably get some feedback on if that was the correct approach
[11:53:59 CDT(-0500)] <Justin_o> heidi_: oh and i saw the scroll bar issue that you were mentioning
[11:54:12 CDT(-0500)] <Justin_o> mlam: do you have any thoughts on when that may have got in
[11:56:23 CDT(-0500)] <heidi_> Justin_o looks like that css is you: https://github.com/mlam/infusion/blob/FLUID-4307/src/webapp/components/uiOptions/css/FatPanelSlidingPanel.css
[11:57:18 CDT(-0500)] <Justin_o> heidi_: thanks for tracking that down.. i need to work on my memory (smile)
[11:57:42 CDT(-0500)] <heidi_> (wink)
[11:58:45 CDT(-0500)] <mlam> Justin_o: I have no idea.
[11:58:49 CDT(-0500)] <heidi_> Justin_o i might leave fat panel tab styling as is - the tabs are different enough that including a theme, then over-riding seems unnecessary
[11:59:27 CDT(-0500)] <heidi_> Justin_o however if we had jquery.ui.tabs.css i'd use that ... but we don't have that in lib now
[12:07:16 CDT(-0500)] <Justin_o> heidi_: okay.. i'm not sure i fully understand the whole situation
[12:08:35 CDT(-0500)] <mlam> heidi_: Justin_o: just catching up on the logs from the morning..
[12:09:13 CDT(-0500)] <mlam> heidi_: Yes, I believe the styling for the Upload button in the html5 version is fixed. I believe jameswy helped with the styling to get it to lay over the input perfectly
[12:09:51 CDT(-0500)] <mlam> Justin_o: about the fat panel, yah, I did notice a scroll bar on the right side of the iframe. but i thought that was intentional
[12:10:36 CDT(-0500)] <Justin_o> mlam: probably not by default.. maybe when textsize or something has changed
[12:10:46 CDT(-0500)] <Justin_o> i don't remember seeing that there before, but i may have just ignored it
[12:11:02 CDT(-0500)] <mlam> Justin_o: oh ok
[12:11:21 CDT(-0500)] <Justin_o> mlam: by the way, how is the !important stuff coming
[12:11:45 CDT(-0500)] <mlam> Justin_o: still reading into rhino
[12:11:58 CDT(-0500)] <Justin_o> mlam: ah okay
[12:12:11 CDT(-0500)] <Justin_o> mlam: so i'll take a look at the scrolling stuff while you do that
[12:12:24 CDT(-0500)] <mlam> of the 3 tasks we talked about yesterday, i'm on the last, which happens to be the largest piece
[12:13:54 CDT(-0500)] <mlam> the ant target is all set up. we now have a target in the build file called cssGenerator which merges 3 js files into one, and once the rhino stuff is done, then it should run that as well to inject the !important tags in
[12:14:11 CDT(-0500)] <heidi_> mlam you mean the jira i filed this morning about the uploader button size? the issue happens when font/line spacing are increased - the size is in px and should be em
[12:14:47 CDT(-0500)] <mlam> heidi_: yes
[12:15:11 CDT(-0500)] <heidi_> mlam it's fixed? in a particular branch i can test?
[12:15:50 CDT(-0500)] <mlam> oh no no, it's not fixed
[12:16:17 CDT(-0500)] <mlam> fixed as in the positioning and sizing are fixed, not the bug itself
[12:17:05 CDT(-0500)] <heidi_> mlam i'm not sure what you mean!
[12:17:11 CDT(-0500)] <heidi_> OH
[12:17:13 CDT(-0500)] <heidi_> that fixed
[12:17:25 CDT(-0500)] <heidi_> haha ahh... k. are you able to fix it or can i help with that?
[12:18:18 CDT(-0500)] <mlam> haha yah, sorry. I'm not sure if I can heidi_ . I've still got the "add more" button issue from my FLUID-3999 branch and then the !important work
[12:19:05 CDT(-0500)] <heidi_> mlam ok i'll grab that one then.
[12:19:11 CDT(-0500)] <mlam> ok, thanks!
[12:19:59 CDT(-0500)] <Justin_o> mlam: so Bosmon has come across another problem with the bridge, we didn't quite get something right.. did you want me to make the change, push to my branch, and then you can pull it down and then push it up to yours.. or would you like to just make the change yourself.. it's pretty small.. but we can skype about it if you like
[12:20:12 CDT(-0500)] <Bosmon4> michelled, cindyli - I was wondering for FLUID-4317 - why we don't just make the template prefix a normal option to the component?
[12:21:33 CDT(-0500)] <mlam> Justin_o: do you have time to make the change yourself?
[12:21:36 CDT(-0500)] <mlam> and also, what is the issue?
[12:21:50 CDT(-0500)] <Justin_o> mlam: i can make it, just need you to get it to your branch on github (smile)
[12:22:08 CDT(-0500)] <Justin_o> we just don't need the third arguement to our call to invokeGlobalFunction
[12:22:10 CDT(-0500)] <mlam> let me give you commit access to my fork
[12:22:20 CDT(-0500)] <Justin_o> mlam: thanks
[12:22:52 CDT(-0500)] <mlam> Justin_o: done
[12:23:07 CDT(-0500)] <Justin_o> mlam: thanks.. i'll try not to break it
[12:23:13 CDT(-0500)] <mlam> haha
[12:24:01 CDT(-0500)] <cindyli> Bosmon4, an option of fluid.uiOptions?
[12:24:11 CDT(-0500)] <Bosmon4> cindyli - yes
[12:24:13 CDT(-0500)] <cindyli> should i come over to talk? easier
[12:30:27 CDT(-0500)] <michelled> cindyli: I just noticed that the UIO store tests are broken - any chance you can look into it?
[12:30:49 CDT(-0500)] <heidi_> Justin_o so to recap re: tabs and fat panel css - i'm going to leave it as is, where a bit of jquery tabs styling exists in fatpanel. until we have our infusion theme, i think we can wait until then before adding in the default theme/over-riding it
[12:30:53 CDT(-0500)] <cindyli> yes, michelled, and i actually think it might be a hole in store test itself
[12:31:05 CDT(-0500)] <cindyli> another jira should be created for that, maybe
[12:32:50 CDT(-0500)] <michelled> cindyli: speaking of tests, it's probably worth writing a test for 4310
[12:33:11 CDT(-0500)] <michelled> wait cindyli - wrong jira number
[12:33:14 CDT(-0500)] <Justin_o> heidi_: okay.. i think that's fine, is there a jira for that
[12:33:20 CDT(-0500)] <michelled> I mean 4324
[12:33:26 CDT(-0500)] <heidi_> Justin_o nope will make one
[12:33:28 CDT(-0500)] <cindyli> michelled: 4310, the demo portal?
[12:33:32 CDT(-0500)] <cindyli> a test for that?
[12:33:36 CDT(-0500)] <Justin_o> heidi_: thanks
[12:33:52 CDT(-0500)] <michelled> no, I made a mistake cindyli 4324 - the change to uio no preview reset
[12:34:02 CDT(-0500)] <Justin_o> heidi_: do you have any thoughts on what i should do about the scroll bar, i'm just going to look into it now
[12:34:20 CDT(-0500)] <cindyli> oh, yes, michelled, we probably should write a test for each of 3 ui options demos
[12:34:43 CDT(-0500)] <heidi_> Justin_o i haven't looked into it but guessing some overflow prob might be happening?
[12:35:26 CDT(-0500)] <Justin_o> heidi_: okay.. thanks
[12:37:15 CDT(-0500)] <cindyli> michelled: not exactly demos, i mean the js scripts in "components/uiOptions/js" that are used by demos
[12:44:48 CDT(-0500)] <heidi_> Justin_o mlam you can take Slider.css out of the iframe for fat panel - it doesn't exist
[12:45:50 CDT(-0500)] <mlam> Justin_o: can you take that out with the invokeGlobalFunction change?
[12:50:55 CDT(-0500)] <Justin_o> mlam: sure
[12:50:58 CDT(-0500)] <Justin_o> heidi_: thanks
[12:51:01 CDT(-0500)] <mlam> thanks
[13:42:38 CDT(-0500)] <jhung> cindyli : do you want me to review pull request #99?
[13:43:59 CDT(-0500)] <cindyli> sure, jhung. thanks
[13:44:08 CDT(-0500)] <heidi_> anastasiac not sure if you'd be able to check the pull request for 4318 (renamed demo-theme to default-theme).
[13:44:22 CDT(-0500)] <anastasiac> heidi_, sure
[13:44:39 CDT(-0500)] <heidi_> i think i just find it unsettling that demo-theme was never used by anything!
[13:44:46 CDT(-0500)] <heidi_> but i'm pretty sure it's all good
[13:49:48 CDT(-0500)] <jhung> cindyli: took a quick look. I think you'll want someone else to take a look at the changes to the javascript for FLUID-4324. Otherwise the changes to HTML look fine. (smile)
[13:50:06 CDT(-0500)] <cindyli> thanks, jhung
[13:53:37 CDT(-0500)] <anastasiac> heidi_, can you help me remember? I thought the whole reason this theme came up in discussions was because Tabs was dependent on it.
[13:53:59 CDT(-0500)] <heidi_> anastasiac yep the new tabs component is, i meant nothing used it before
[13:54:35 CDT(-0500)] <anastasiac> ok, so the pull request you've submitted is only for the renaming, not for the new tabs css (which was the point of 4318)?
[13:54:52 CDT(-0500)] <heidi_> anastasiac there won't be a tabs.css
[13:55:19 CDT(-0500)] <anastasiac> which JIRA is the new tabs component being done under?
[13:55:41 CDT(-0500)] <heidi_> anastasiac new tabs component is already in master
[13:56:07 CDT(-0500)] <anastasiac> where is the dependence on the theme file encoded now?
[13:56:25 CDT(-0500)] <heidi_> but remember we were initially weirded out that demo-theme/jquery.ui.theme.css was req'd for tabs to work
[13:56:43 CDT(-0500)] <heidi_> but after our discussion about it still being a jquery ui component, we decided that dependency did make sense
[13:56:50 CDT(-0500)] <anastasiac> yes, I remember - I just can't fine that dependence anywhere
[13:56:54 CDT(-0500)] <heidi_> but to make it clearer and less weird, renamed demo-theme to default-theme
[13:56:54 CDT(-0500)] <anastasiac> find
[13:57:16 CDT(-0500)] <heidi_> anastasiac the only thing using the tabs component right now is the fat panel
[13:57:24 CDT(-0500)] <heidi_> and justin and i were talking about it earlier
[13:57:47 CDT(-0500)] <heidi_> that the fat panel.css right now includes it's own jquery ui tabs styling within it
[13:57:54 CDT(-0500)] <heidi_> which isn't great, and i'm making a jira for that
[13:58:05 CDT(-0500)] <heidi_> but it will be solved once we have a proper infusion theme
[13:58:40 CDT(-0500)] <heidi_> ie. jquery css will be taken out of fatpanel.css , and it will use infusion-theme theme file
[13:58:50 CDT(-0500)] <heidi_> something like that - kinda make sense?
[13:59:14 CDT(-0500)] <anastasiac> so currently, technically, Tabs doesn't depend on the theme file, it depends on something, and integrators could use the theme file or their own styles?
[13:59:44 CDT(-0500)] <heidi_> anastasiac in order for tabs to look like tabs out of the box, need that theme file. but yes can use their own if they want
[14:00:13 CDT(-0500)] <anastasiac> I ask because fat-panel uses tabs but doesn't use the theme file, so tabs isn't truly dependent
[14:00:57 CDT(-0500)] <heidi_> anastasiac it's a freaky case where we've included the jquery ui tabs styling within fatpanel.css - so those styles are still there/req'd but coming from itself instead of the theme file
[14:01:25 CDT(-0500)] <heidi_> which isn't great, that tabs styling shouldn't be duplicated, but we'll wait to fix that
[14:01:50 CDT(-0500)] <anastasiac> ok, so long as there's a jira about the duplication
[14:02:12 CDT(-0500)] <heidi_> yep. ill do that now and add it to 4318 jira
[14:04:18 CDT(-0500)] <Bosmon4> Hi there cindyli - colinclark and I talked a little more about the template prefix issue
[14:04:34 CDT(-0500)] <Bosmon4> He observed that the top-level options for FatPanel should actually conform to those of UIOptions itself
[14:04:50 CDT(-0500)] <Bosmon4> So it shouldn't matter that the output structure from FatPanel has the UIOptions component in an unexpected place
[14:05:09 CDT(-0500)] <heidi_> anastasiac fyi http://issues.fluidproject.org/browse/FLUID-4329
[14:05:39 CDT(-0500)] <anastasiac> thanks, heidi_
[14:07:23 CDT(-0500)] <cindyli> Bosmon4, sorry, what do u mean by "the top-level options for FatPanel should actually conform to those of UIOptions itself"?
[14:07:41 CDT(-0500)] <Bosmon4> cindyli - FatPanel actually accepts the plain UIOptions options, right?
[14:07:46 CDT(-0500)] <Bosmon4> All of its basic configuration?
[14:08:09 CDT(-0500)] <cindyli> no, slidingPanel is another sub-component
[14:08:12 CDT(-0500)] <cindyli> of fat panel
[14:09:12 CDT(-0500)] <huslage> https://chrome.google.com/webstore/detail/afpofdeegmmclngjmadpjaajacebkege
[14:09:27 CDT(-0500)] <Bosmon4> cindyli - Justin_o asserts that it does take the same options on input
[14:09:53 CDT(-0500)] <Justin_o> Bosmon4, cindyli: it takes the same options, but does have a few more of it's own as well
[14:10:17 CDT(-0500)] <Bosmon4> So it seems possible for the template prefix to be one of these options
[14:10:55 CDT(-0500)] <cindyli> Bosmon4, let me try
[14:11:03 CDT(-0500)] <Bosmon4> cindyli - thanks
[14:11:12 CDT(-0500)] <cindyli> np
[14:19:47 CDT(-0500)] <heidi_> jhung let's chat idi site tomorrow. i'm working on an uploader fix right nwo
[14:35:10 CDT(-0500)] <cindyli> Bosmon4, do u have a minute? can i show u my difficulty at making prefix an uioptions option
[14:35:16 CDT(-0500)] <Bosmon4> hello
[14:38:22 CDT(-0500)] <jessm> anastasiac: two comments on the first paragraph of the readme...
[14:38:33 CDT(-0500)] <jessm> 1. the mention of model and view might be confusing
[14:38:51 CDT(-0500)] <jessm> i remember us talking about audience on this readme and deciding it was a pretty tech-savvy crowd
[14:39:05 CDT(-0500)] <jessm> but i'm thinking as FSS grows it might appeal to more folks
[14:39:11 CDT(-0500)] <jessm> i dunno, it just caught my eye
[14:39:31 CDT(-0500)] <anastasiac> ok
[14:39:38 CDT(-0500)] <jessm> also... our use of terms like unobtrusive – seems fine where it is, but it occurs to me that technologists talk to each other in language that others don't understand
[14:39:51 CDT(-0500)] <jessm> for a readme that's cool – it's just something i'm more aware of lately
[14:40:00 CDT(-0500)] <anastasiac> good point
[14:40:12 CDT(-0500)] <jessm> my dad got a new computer and asked me what "R - S - S" meant – duh, there's no way my dad would know!
[14:40:16 CDT(-0500)] <jessm> it was a good reminder
[14:40:31 CDT(-0500)] <anastasiac> jessm, for model/view, do you think the sentence would work fine if I used "content" and "presentation" ?
[14:41:40 CDT(-0500)] <jessm> anastasiac: to me, yes. but i'd love to hear how the king or colinclark feel about it. i'm not as well tapped into the cultural use of model/view as they
[14:42:09 CDT(-0500)] <anastasiac> yeah, it's tricky choosing language that is adequate but not too techy
[14:42:35 CDT(-0500)] <anastasiac> the more I think about it, content/presentation isn't right there
[14:43:01 CDT(-0500)] <michelled> heidi_: I've merged in the 4307 branch which has the 3761 fixes
[14:43:16 CDT(-0500)] <michelled> heidi_: you have a comment on the 3761 JIRA - is it still valie?
[14:43:19 CDT(-0500)] <michelled> valid?
[14:43:37 CDT(-0500)] <anastasiac> jessm, actually, "a declarative and event-driven style" might not fit with the FSS audience, either
[14:43:52 CDT(-0500)] <anastasiac> hm
[14:43:58 CDT(-0500)] <heidi_> michelled i believe mlam or Justin_o is working on the scrollbar. the dropdown styles one i don't think is a prob, i think it was my end
[14:44:04 CDT(-0500)] <jessm> yeah, i don't think we need to speak to just one or the other or all necessarily
[14:44:21 CDT(-0500)] <jessm> if model/view is something we feel really identifies Infusion and needs to be prominently in there, then leave it be
[14:44:27 CDT(-0500)] <michelled> heidi_: I think I'll make a new JIRA for the scrollbar issue
[14:44:41 CDT(-0500)] <jessm> i wonder also if we can link to pages in our docs that explain these concepts?
[14:44:47 CDT(-0500)] <jessm> won't we have pages that do anyway?
[14:45:07 CDT(-0500)] <anastasiac> interesting suggestion. we do have some...
[14:45:48 CDT(-0500)] <heidi_> michelled sounds good
[14:48:06 CDT(-0500)] <Bosmon4> Hi cindyli - I made http://issues.fluidproject.org/browse/FLUID-4330 - could you check the version of the component you just showed me into your desktop into a branch with this number?
[14:48:07 CDT(-0500)] <Bosmon4> Thanks
[14:50:46 CDT(-0500)] <cindyli> sure. Bosmon4. thank YOU!
[14:58:31 CDT(-0500)] <michelled> anastasiac: I just put in what I think is the last big branch for 1.4
[14:58:42 CDT(-0500)] <michelled> any chance you can take a peek at the dependencies?
[14:58:42 CDT(-0500)] <anastasiac> I was just looking at the commit
[14:58:47 CDT(-0500)] <michelled> (smile)
[14:58:50 CDT(-0500)] <anastasiac> will do
[14:58:55 CDT(-0500)] <michelled> thx
[15:06:14 CDT(-0500)] <Bosmon4> Hi, cindyli, michelled - so I am now reviewing the ORIGINAL pull request for FLUID-4317
[15:06:26 CDT(-0500)] <Bosmon4> Now we have decided that this is broadly the right strategy
[15:07:06 CDT(-0500)] <Bosmon4> So, the main issue I have with it is that the configuration for the templateLoader uses an expander rather than a direct IoC reference
[15:07:22 CDT(-0500)] <Bosmon4> This is at line 242
[15:07:34 CDT(-0500)] <cindyli> Bosmon4, ic, the right way is via a demands block?
[15:08:12 CDT(-0500)] <cindyli> or curly brackets. trying
[15:13:27 CDT(-0500)] <Bosmon4> cindyli - yes, a demands block will be required
[15:13:36 CDT(-0500)] <Bosmon4> Since the EL reference will change depending on the context of the component
[15:13:47 CDT(-0500)] <cindyli> ok, thanks
[15:13:50 CDT(-0500)] <Bosmon4> The default value should probably just be the plain string "../html/"
[15:14:12 CDT(-0500)] <Bosmon4> And then the different integrations will supply a demands block to resolve the string onto their own configuration
[15:17:08 CDT(-0500)] <colinclark> jessm and anastasiac: I missed your earlier conversation
[15:17:15 CDT(-0500)] <colinclark> which mentioned words like model and view
[15:17:18 CDT(-0500)] <colinclark> and content and presentation
[15:17:26 CDT(-0500)] <colinclark> I'm missing some of the context to offer any useful insights
[15:17:49 CDT(-0500)] <colinclark> but I guess I am somewhat ambivalent about this issue of speaking a non-technological language
[15:17:52 CDT(-0500)] <colinclark> which I think is very important
[15:18:21 CDT(-0500)] <anastasiac> colinclark, the context is the opening paragraph(s) of the readme file
[15:18:21 CDT(-0500)] <colinclark> but I also think you need to speak in terms that developers can relate to and correspond with things they are already familiar
[15:18:22 CDT(-0500)] <colinclark> different content for different audiences, arguably
[15:18:32 CDT(-0500)] <colinclark> Or, dangerously, different Views for the Infusion Model (tongue)
[15:18:50 CDT(-0500)] <anastasiac> jessm was concerned about less techy audiences like FSS folks
[15:19:32 CDT(-0500)] <jessm> well, i didn't exactly call FSSers less techy, but suggested it's always a good reminder to unpack our language use
[15:20:12 CDT(-0500)] <jessm> when we say model/view does it make folks lean in or skip? i can't speak to that too well
[15:20:38 CDT(-0500)] <anastasiac> michelled, thanks for the ping about the dependencies. I've updated the uiOptions dependencies (and the build properties) to include the Tabs component - seems to work well with a custom build
[15:25:08 CDT(-0500)] <cindyli> Bosmon4: have a couple of questions on demands block for "fluid.uiOptionsTemplateLoader". if we added a default demands to feed in template prefix from "uiOptionsTemplatePath", when the integrator overwrites it, he has to include this part as only one demands block wins
[15:25:20 CDT(-0500)] <cindyli> does it defeat the purpose?
[15:25:47 CDT(-0500)] <Bosmon4> Hi, it does of the original, yes, which is why I suggested the default value should just be a string
[15:25:51 CDT(-0500)] <Bosmon4> We don't need "uiOptionsTemplatePath"
[15:25:55 CDT(-0500)] <Bosmon4> There should just be the demands block
[15:26:21 CDT(-0500)] <cindyli> ah, then we are back to the old issue
[15:26:26 CDT(-0500)] <Bosmon4> !
[15:26:30 CDT(-0500)] <cindyli> prefix and templates are in the same component
[15:27:08 CDT(-0500)] <colinclark> jessm and anastasiac: I think we should consider just a little bit who our audiences are...
[15:27:16 CDT(-0500)] <colinclark> so, for example, who uses a README file?
[15:27:31 CDT(-0500)] <jessm> the folks already ready to use the code
[15:27:35 CDT(-0500)] <colinclark> Someone visiting Github, or someone who has downloaded an Infusion package
[15:27:51 CDT(-0500)] <colinclark> I think that there most definitely should be a very easy-to-approach explanation of Infusion
[15:27:59 CDT(-0500)] <colinclark> well beyond the level of things like models and views, etc.
[15:28:04 CDT(-0500)] <colinclark> But I think it should probably be on our web site
[15:28:15 CDT(-0500)] <colinclark> On a page like "What is Infusion?"
[15:28:40 CDT(-0500)] <colinclark> perhaps with a companion "What is Infusion? (For Developers)" or something
[15:28:46 CDT(-0500)] <colinclark> I very well might be mistaken
[15:29:01 CDT(-0500)] <colinclark> but I'm imagining the audience for a README is going to be, by nature, a bit more technical
[15:29:15 CDT(-0500)] <colinclark> I really would like to build a small graphical authoring tool for the FSS
[15:29:26 CDT(-0500)] <colinclark> which will allow you, on a web page, to define grid layouts and other things
[15:29:42 CDT(-0500)] <colinclark> and then you click a button and get a version of the FSS plus some boilerplate markup, etc.
[15:30:00 CDT(-0500)] <colinclark> That's also where you'd want a different flavour of the Infusion description
[15:30:09 CDT(-0500)] <colinclark> Does all of this make some sense?
[15:31:21 CDT(-0500)] <jessm> yes
[15:31:25 CDT(-0500)] <anastasiac> colinclark, yes. it sounds like you're advocating leaving the readme as it is (i.e. with "model" and "view") and making sure that we have approachable text on the website. Is that right?
[15:31:27 CDT(-0500)] <jessm> so, my question
[15:31:37 CDT(-0500)] <colinclark> anastasiac: Yes, I think that's correct
[15:31:39 CDT(-0500)] <jessm> to the technical audience who is not me, does the use of model/view motivate?
[15:31:47 CDT(-0500)] <colinclark> that's a good question
[15:32:02 CDT(-0500)] <colinclark> I suppose there are lots of such folk right here
[15:36:06 CDT(-0500)] <colinclark> Just, randomly, here are some READMEs from comparable projects' Github repositories
[15:36:08 CDT(-0500)] <colinclark> https://github.com/documentcloud/backbone
[15:36:15 CDT(-0500)] <colinclark> https://github.com/sproutcore/sproutcore
[15:36:35 CDT(-0500)] <colinclark> https://github.com/jquery/jquery-ui
[15:36:57 CDT(-0500)] <colinclark> https://github.com/joyent/node
[15:37:46 CDT(-0500)] <jessm> backbone has bubble letters!
[15:38:03 CDT(-0500)] <jessm> and a really pithy readme
[15:38:04 CDT(-0500)] <jessm> cool
[15:39:28 CDT(-0500)] <jessm> sproutcore super simple too
[15:39:50 CDT(-0500)] <anastasiac> backbone certainly doesn't shy from some techy verbiage
[15:40:11 CDT(-0500)] <jessm> anastasiac: i think we can all agree to use technical language
[15:40:24 CDT(-0500)] <jessm> the question was – is it meaningful – a question i can't personally answer
[15:40:31 CDT(-0500)] <jessm> i'm interested in how short these readmes are
[15:41:25 CDT(-0500)] <jessm> maybe i should put it another way...
[15:42:00 CDT(-0500)] <jessm> if someone is already looking at the code, and reading the readme, is it important to them that "Infusion provides a rich set of APIs for creating loosely-coupled
[15:42:01 CDT(-0500)] <jessm> models and views using a declarative and event-driven style."
[15:42:09 CDT(-0500)] <jessm> or do they just blur through it
[15:44:54 CDT(-0500)] <anastasiac> jessm, my guess is that the readme will be read in order to decide whether or not to look at the code (smile)
[15:44:58 CDT(-0500)] <Bosmon4> jessm - I doubt anyone will actually take anything away from this text in any case (tongue)
[15:45:15 CDT(-0500)] <Bosmon4> anastasiac - I would guess exactly the opposite - the code will be read in order to decide whether or not to look at the readme (smile)
[15:45:28 CDT(-0500)] <jessm> that's what i'm wondering
[15:45:32 CDT(-0500)] <anastasiac> :-/
[15:45:35 CDT(-0500)] <jessm> so, what actually does the readme need to say??
[15:45:54 CDT(-0500)] <Bosmon4> Well, it needs to look sort of convincing, and not actually say anything inaccurate or outlandish (tongue)
[15:46:15 CDT(-0500)] <mlam> colinclark: just a quick verification question....for the Rhino-based !important injection, we want the load function to return a string containing all the contents of the file, right?
[15:46:16 CDT(-0500)] <Bosmon4> I think your text is very good
[15:47:15 CDT(-0500)] <colinclark> mlam: Yes, at the moment there's a very simple contract for this stylesheetStore or whatever I called it
[15:47:16 CDT(-0500)] <colinclark> load() and save() methods
[15:47:35 CDT(-0500)] <colinclark> load() takes an argument and returns a string containing the contents of the stylesheet
[15:48:07 CDT(-0500)] <colinclark> save() takes a string containing the new stylesheet's contents and a path
[15:48:14 CDT(-0500)] <Bosmon4> colinclark - shouldn't those be "get" and "put" methods?
[15:48:24 CDT(-0500)] <mlam> and save should then take the revised contents of a stylesheet as a string, then convert that string to a file and store the file on the filesystem ?
[15:48:28 CDT(-0500)] <Bosmon4> It looks to me that this exactly conforms to the DataSource API
[15:48:43 CDT(-0500)] <colinclark> Bosmon4: Sure
[15:48:47 CDT(-0500)] <colinclark> send me a pull request (wink)
[15:48:57 CDT(-0500)] <colinclark> or write this email for me
[15:48:57 CDT(-0500)] <colinclark> you pick
[15:49:07 CDT(-0500)] <colinclark> mlam: you've got it, yes
[15:49:18 CDT(-0500)] <mlam> ok, wicked.
[15:49:20 CDT(-0500)] <mlam> thanks
[16:06:07 CDT(-0500)] <colinclark_> jessm and anastasiac: Here's a real back of the envelope sort of sketch
[16:06:08 CDT(-0500)] <colinclark_> http://pastie.org/2179680
[16:06:19 CDT(-0500)] <colinclark_> simple, a bit more modest, and to the point
[16:06:21 CDT(-0500)] <colinclark_> those were my goals
[16:06:23 CDT(-0500)] <colinclark_> perhaps not quite there
[16:06:26 CDT(-0500)] <colinclark_> hack and slash away
[16:06:53 CDT(-0500)] <anastasiac> nice - shorter, which is good, I think
[16:07:41 CDT(-0500)] * jessm likes
[16:07:45 CDT(-0500)] <jessm> colinclark_: very nice
[16:08:34 CDT(-0500)] <colinclark_> In the spirit of paring back, here's this:
[16:08:35 CDT(-0500)] <colinclark_> http://pastie.org/2179693
[16:08:56 CDT(-0500)] <colinclark> and with that, back to emails and slides
[16:09:08 CDT(-0500)] <colinclark> thanks for reminding me that this needed to get looked at
[16:09:23 CDT(-0500)] <colinclark> anastasiac and jessm please feel free to make it your own
[16:09:28 CDT(-0500)] <jessm> colinclark: thanks for whipping it so quickly
[16:09:36 CDT(-0500)] <jessm> anastasiac: +1 to the latest one
[16:09:38 CDT(-0500)] <colinclark> let's go with "different, inclusive, and humble" as our new brand
[16:09:48 CDT(-0500)] <jessm> +1
[16:09:54 CDT(-0500)] <colinclark> Bosmon: ^
[16:10:08 CDT(-0500)] <jessm> anastasiac: how does this work – do you lift his pastie into github? as another rev?
[16:11:03 CDT(-0500)] <anastasiac> jessm, I'll edit and push another version to my github
[17:14:07 CDT(-0500)] <mlam> colinclark: I'm having this strange issue ...maybe it's a configuration thing....Rhino is already built into the system, right?
[17:14:18 CDT(-0500)] <colinclark> yes
[17:15:01 CDT(-0500)] <mlam> build.js is fine with an importClass() call, however if I try to make the same call in the CSSGenerator.js file, the tests for the CSSGenerator all fail
[17:15:58 CDT(-0500)] <colinclark> yes
[17:16:10 CDT(-0500)] <colinclark> The browser doesn't have an importClass() function
[17:16:13 CDT(-0500)] <colinclark> so it will fail
[17:16:28 CDT(-0500)] <colinclark> I can imagine the jQuery code might freak in Rhino, too
[17:16:36 CDT(-0500)] <colinclark> so you'll need to split these two strategies out into separate files
[17:16:42 CDT(-0500)] <colinclark> and only load the appropriate one for the given context
[17:16:54 CDT(-0500)] <colinclark> meaning, in Rhino, you'd link to RhinoStylesheetSource.js or whatever
[17:17:01 CDT(-0500)] <colinclark> and in the browser, you'd link to the other file
[17:18:26 CDT(-0500)] <mlam> oh ok