fluid-work IRC Logs-2011-04-25

[07:37:50 CDT(-0500)] <kasper> yura_: morning!
[07:37:56 CDT(-0500)] <yura_> kasper: morning
[07:38:01 CDT(-0500)] <kasper> you're up/in early today
[07:38:12 CDT(-0500)] <yura_> kasper: ya
[07:38:12 CDT(-0500)] <yura_>
[07:39:54 CDT(-0500)] <kasper> yura_: do you have any suggestions; on the QA server, I have installed collectionspace. In $JBOSS_HOME/server/cspace/conf/ I've edited settings.xml to point at localhost for all URLs
[07:40:12 CDT(-0500)] <kasper> but still going to qa.collectionspace.org seems to point to the nightly backend
[07:40:31 CDT(-0500)] <kasper> I've done a "grep nightly *" in $JBOSS_HOME/server/cspace/conf/ with no hits
[07:41:33 CDT(-0500)] <yura_> oh well i know that the app produces several xml files
[07:41:45 CDT(-0500)] <yura_> there's nightly-settings and local-settings
[07:41:51 CDT(-0500)] <yura_> but they both point at nightly
[07:42:36 CDT(-0500)] <yura_> kasper: ^
[07:43:05 CDT(-0500)] <kasper> yura_: oh - should probably have wrote that I made sure neither of those were there
[07:43:29 CDT(-0500)] <kasper> the thing is, I've done this a billion time (set up servers, changed conf)
[07:43:50 CDT(-0500)] <yura_> kasper: i never deployed all 3 layers
[07:43:57 CDT(-0500)] <yura_> only app and ui
[07:44:08 CDT(-0500)] <yura_> and i didnt really have to change any settings
[07:44:22 CDT(-0500)] <kasper> ok – I'll look some more! Thanks yura_
[07:44:51 CDT(-0500)] <yura_> sorry i coldnt help
[08:44:43 CDT(-0500)] <heidi_> hey cindyli , sorry i think i've asked this too many times, but what's the url to your github for the UIO work? i'm going to take a look at how the new fss is affecting it
[08:45:37 CDT(-0500)] <cindyli> not a problem. here it is: https://github.com/cindyli/infusion/tree/FLUID-4171
[08:46:22 CDT(-0500)] <heidi_> thanks
[09:40:38 CDT(-0500)] <jessm> heidi_: ping here
[09:40:49 CDT(-0500)] <heidi_> hey jessm
[09:40:52 CDT(-0500)] <jessm> heya
[09:41:03 CDT(-0500)] <jessm> heidi_: i'm wondering what's already on your plate for this week?
[09:41:32 CDT(-0500)] <heidi_> jessm finishing up fss stuff (early this week hopefully), then working with james on styling UIOptions for 1.4
[09:42:36 CDT(-0500)] <jessm> heidi_: cool
[09:43:00 CDT(-0500)] <heidi_> jessm need website help?
[09:44:11 CDT(-0500)] <jessm> heidi_: i'm sending an email to you, greggy1 ,jameswy and smriti and cc:ing idi-work re: some website-y things for this week and next; anyway, I'm trying to kick up a convo about who will do what.
[09:44:35 CDT(-0500)] <heidi_> jessm okay i'll stay tuned and see how i can help
[09:44:40 CDT(-0500)] <jessm> heidi_: thanks!
[09:45:00 CDT(-0500)] <greggy1> jessm: k, currently working on the things cathy asked for
[09:45:31 CDT(-0500)] <jessm> greggy1: great. i'm hoping my email just kicks up a conversation about how and who can take on these tasks
[09:49:18 CDT(-0500)] <jessm> weird, the email doesn't seem to have appeared
[09:49:43 CDT(-0500)] <jessm> and the list hasn't sent me an email reminder
[09:49:44 CDT(-0500)] <greggy1> jessm: I got it
[09:49:47 CDT(-0500)] <jessm> weird
[09:50:05 CDT(-0500)] <jessm> greggy1: yes, you were in the To: explicitly
[09:50:20 CDT(-0500)] <jessm> jamon: do you see any funkiness with idi-work?
[09:50:45 CDT(-0500)] <jamon> jessm: what am i looking for?
[09:50:56 CDT(-0500)] <jessm> jamon: i sent a message
[09:51:04 CDT(-0500)] <jessm> and i asked for a passwd reminder for my acct.
[09:51:28 CDT(-0500)] <jamon> when did you send?
[09:51:30 CDT(-0500)] <jamon> checking
[09:52:02 CDT(-0500)] <jessm> jamon: 10:46
[09:52:21 CDT(-0500)] <jamon> patience
[09:52:36 CDT(-0500)] <jamon> both show up in the logs
[09:52:53 CDT(-0500)] <jessm> why is it so slow? what's it doing with my message? fact checking??
[09:52:59 CDT(-0500)] <jamon> greylisting
[09:53:13 CDT(-0500)] <greggy1> jessm: heidi_: anyone know what the storuy is with Joomla and embeded scripts? I was trying to embed the universal subtitles version of the Jutta tips video, but apparently you can do that in Joomla.
[09:53:29 CDT(-0500)] <jessm> jamon: why greylisted?
[09:53:43 CDT(-0500)] <greggy1> ...can't do that
[09:53:49 CDT(-0500)] <greggy1> in Joomla
[09:54:07 CDT(-0500)] <heidi_> greggy1 can't include remote scripts? i'm not sure... might have to do it a module-y way?
[09:54:19 CDT(-0500)] <heidi_> smriti might know
[09:54:23 CDT(-0500)] <jamon> jessm: spam prevention
[09:54:26 CDT(-0500)] <jessm> jamon: and i've asked for a passwd reminder that hasn't come through either.
[09:54:39 CDT(-0500)] <jessm> jamon: does that mean you're moderating the list?
[09:54:49 CDT(-0500)] <jamon> jessm: it did go through, says to your ocad address
[09:54:49 CDT(-0500)] <greggy1> heidi_: thx heidi_, I'll ask her when she get online
[09:54:50 CDT(-0500)] <jamon> jessm: no
[09:55:51 CDT(-0500)] <jamon> jessm: greylisting works by telling a remote smtp server to come back and try again later
[09:56:02 CDT(-0500)] <jamon> spammers don't bother, legitimate smtp servers will retry
[09:56:07 CDT(-0500)] <heidi_> greggy1 http://www.joomlaperformance.com/component/option,com_easyfaq/task,view/id,53/Itemid,46/ not sure which version of joomla that's referencing tho
[09:56:13 CDT(-0500)] <jessm> jamon: is it greylisting me because of my domain?
[09:56:22 CDT(-0500)] <jamon> jessm: cuts spam by 80-90% in many cases
[09:56:24 CDT(-0500)] <jamon> jessm: likely
[09:56:41 CDT(-0500)] <jessm> jamon: ah, interesting. maybe i should send from my @ocad.ca email
[09:57:02 CDT(-0500)] <jessm> jamon: any idea why i haven't gotten the passwd. reminders I requested?
[09:57:24 CDT(-0500)] <jamon> 10:54 < jamon> jessm: it did go through, says to your ocad address
[09:57:25 CDT(-0500)] <heidi_> greggy1 http://docs.joomla.org/Adding_JavaScript
[09:58:22 CDT(-0500)] <jessm> jamon: got filtered as spam
[09:58:24 CDT(-0500)] <jessm> urgh
[09:58:35 CDT(-0500)] <jamon> unmark it to train their system
[09:58:39 CDT(-0500)] <heidi_> cindyli reverting back fixed UIO - thanks!
[09:59:00 CDT(-0500)] <cindyli> great heidi_
[09:59:30 CDT(-0500)] <heidi_> cindyli tho changing the sliders for text size and line spacing doesn't seem to affect the preview. but maybe it's cos you're still working on that?
[09:59:57 CDT(-0500)] <cindyli> yes, heidi_, michelled_ is working on that
[10:00:37 CDT(-0500)] <jessm> jamon: one of the passwd reminders never got to me – to my @gmail add
[10:01:20 CDT(-0500)] <heidi_> cindyli it seems the background colours are changing ok. that was the issue right? or was it something else
[10:01:54 CDT(-0500)] <jamon> jessm: there wasn't a request sent for that address
[10:02:24 CDT(-0500)] <jessm> jamon: ggggrrrrr, ok, sorry, got it
[10:02:53 CDT(-0500)] <jamon>
[10:03:03 CDT(-0500)] <cindyli> heidi_: it's about the contrast options: "high contrast" and "high contrast reverted"
[10:03:34 CDT(-0500)] <jessm> jamon: you have to fail authenticating, then put just the email add. back in and click on email reminder – weird interaction – clearly too much for my Monday a.m. brain
[10:03:37 CDT(-0500)] <heidi_> cindyli seem ok. what was the prob?
[10:03:41 CDT(-0500)] <cindyli> heidi_: the preivous behaviours of these themes are the whole background changed to white or black, now only the heading parts get changed
[10:04:15 CDT(-0500)] <heidi_> hm, changing for me - not you cindyli? i'm in demos/uiOptions/html/uiOptions.html
[10:04:32 CDT(-0500)] <cindyli> heidi_: trying..
[10:04:36 CDT(-0500)] <jamon> jessm: http://lists.idrc.ocad.ca/mailman/listinfo/idi-work at the bottom, the edit options button, then password reminder button at the bottom of the next page
[10:05:13 CDT(-0500)] <cindyli> heidi_: that might because it doesn't have a background image, or color, try src/webapp/standalone-demos/uiOptions/html/UIOptions.html
[10:05:21 CDT(-0500)] <heidi_> ok
[10:05:45 CDT(-0500)] <heidi_> cindyli ah yes i see now. okay thanks!
[10:05:50 CDT(-0500)] <cindyli> np
[10:06:24 CDT(-0500)] <jessm> jamon: yes, so you put your email add in, and then try a passwd. on teh next page, it fails to auth, and then doesn't hold onto the email add but still shows the passwd. reminder link. anyway, it's me, not the list. i've got it together now. thanks for the info re: greylisting. i'll send from @ocad to try to combat that
[10:06:49 CDT(-0500)] <jamon> jessm: we must be looking at different pages
[10:06:52 CDT(-0500)] <jamon> ah well
[10:49:49 CDT(-0500)] <heidi_> cindyli is there a UIO "to-do" list for 1.4 on the wiki? kind of like our fss one? (http://wiki.fluidproject.org/display/fluid/FSS+1.4+-+1.5+Roadmap)
[10:50:57 CDT(-0500)] <cindyli> i have a list of all the jiras related to UIO, but don't think we have everything packed in one page. do we, michelled_?
[10:51:14 CDT(-0500)] <heidi_> cindyli is that list on the wiki?
[10:51:27 CDT(-0500)] <cindyli> heidi_: no, in my local
[10:51:37 CDT(-0500)] <heidi_> jameswy and i will prob add to it, for planning our styling work
[10:51:59 CDT(-0500)] <cindyli> heidi_: ic. sending u the jira list
[10:52:12 CDT(-0500)] <heidi_> cindyli okay thanks. i'll put it up somewhere if there isn't one yet
[10:52:12 CDT(-0500)] <michelled_> cindyli, heidi_: http://wiki.fluidproject.org/display/fluid/UI+Options+1.4+Roadmap
[10:52:16 CDT(-0500)] <heidi_> aha..
[10:52:44 CDT(-0500)] <heidi_> cindyli perhaps update that page then?
[10:52:49 CDT(-0500)] <michelled_> not everything in the tasks lists has associated JIRAs
[10:52:55 CDT(-0500)] <cindyli> aha, great, michelled_
[10:53:22 CDT(-0500)] <cindyli> michelled_: the jir list i have is much longer than this, should i add them all in?
[10:53:38 CDT(-0500)] <michelled_> cindyli: no, I don't think we expect to do them all for 1.4
[10:53:59 CDT(-0500)] <heidi_> cindyli maybe just paste your list in if you don't have much time. this can be a rough planning space for the next 2 weeks
[10:54:01 CDT(-0500)] <michelled_> cindyli: you could add any JIRAs that you expect to finish for 1.4
[10:54:02 CDT(-0500)] <cindyli> oh, ic, the ones on the road map is in high priority?
[10:54:23 CDT(-0500)] <michelled_> heidi_: the list cindyli is referring to is just a laundry list from JIRA
[10:54:40 CDT(-0500)] <michelled_> just do a browse in JIRA for all issues related to UIO and you'll find them
[10:54:52 CDT(-0500)] <heidi_> gotcha. then i second your suggestion to just add 1.4 jiras
[11:42:13 CDT(-0500)] <cindyli> Bosmon: have time to chat about a problem I had after merging in the changes you made during the weekend, probably due to the changes on renderer component?
[12:23:00 CDT(-0500)] <heidi_> cindyli we're going to have to try to brainstorm a way to allow themes in UIO to override default background settings without using !important. right now the background style from "fl-uiOptions-previewContent" wins
[12:23:27 CDT(-0500)] <cindyli> ok, heidi_
[12:24:07 CDT(-0500)] <heidi_> cindyli one thought is for UIO to set background: none !important when a theme changes... so it has a clean slate. not sure where that would fit in the UIO code
[12:24:26 CDT(-0500)] <heidi_> i'll play around to try to think of other suggestions...
[12:25:25 CDT(-0500)] <heidi_> cindyli looks like there is a clearClashingClasses function already
[12:25:27 CDT(-0500)] <cindyli> thx heidi_. i will try to find the place in UIO to fit your thought
[12:25:32 CDT(-0500)] <heidi_> it could prob fit in there maybe...
[12:25:53 CDT(-0500)] <cindyli> we could try
[12:26:03 CDT(-0500)] <heidi_> in ui enhancer line 190
[12:26:10 CDT(-0500)] <heidi_> yeah... i'll try
[12:26:10 CDT(-0500)] <cindyli> ya,
[12:26:46 CDT(-0500)] <heidi_> it's not a class tho, it's a specific style
[12:34:41 CDT(-0500)] <Bosmon> Hi jamon - is there a URL which shows the result of the testswarm test cases?
[12:36:18 CDT(-0500)] <fatimaohussain> Hello, I am developing a screen recording applet for Open VULab project (YorkU). I do test the code on my own but i would like to do some automated rigourous testing. I was wondering if there is any free/open source software available with which i can run my applet several times and record any errors. Thanks
[12:59:12 CDT(-0500)] <Bosmon> Hi cindyli - sure
[12:59:27 CDT(-0500)] <Bosmon> Yes, I was afraid that the changes might have disrupted the current UIOptions work
[12:59:45 CDT(-0500)] <cindyli> ha, u know where goes wrong?
[12:59:47 CDT(-0500)] <Bosmon> There have been various changes to the API, but I could only verify uses of them that were already in trunk
[13:00:10 CDT(-0500)] <Bosmon> I can't guess quite that much - you will need to give me a clue
[13:00:23 CDT(-0500)] <Bosmon> My best guess is that you may have a conflict with the "afterRender" event
[13:00:24 CDT(-0500)] <cindyli> understand, my problem is the page is not rendered any more,
[13:00:32 CDT(-0500)] <Bosmon> Ah, I see
[13:00:34 CDT(-0500)] <jameswy> fluid-everyone: We'll be going over UI options in a minute, over Skype. Who wants/needs to be invited?
[13:00:44 CDT(-0500)] <cindyli> i traced in and found the tree passed into that.render is empty
[13:00:50 CDT(-0500)] <cindyli> produceTree is never called
[13:00:56 CDT(-0500)] <Bosmon> That's odd
[13:01:09 CDT(-0500)] <Bosmon> Since my change was meant to PROMOTE the use of produceTree, not to break it
[13:01:11 CDT(-0500)] <cindyli> as u've known that my produceTree is assigned in preInit
[13:01:14 CDT(-0500)] <cindyli> not sure if related
[13:01:14 CDT(-0500)] <Bosmon> Ah!!
[13:01:28 CDT(-0500)] <Bosmon> I forgot I told you to do that
[13:01:32 CDT(-0500)] <michelled_> jameswy: me please
[13:01:43 CDT(-0500)] <cindyli> jameswy: call me pls into ui options meeting
[13:01:53 CDT(-0500)] <heidi_> jameswy me
[13:02:01 CDT(-0500)] <mlam> jameswy: count me in
[13:02:10 CDT(-0500)] <Bosmon> cindyli: Ok, I will give you ANOTHER workaround - whilst I fix the result of the previous one
[13:02:22 CDT(-0500)] <cindyli> ok, Bosmon
[13:02:25 CDT(-0500)] <Bosmon> You should now pass the name of the function as an argument to the "produceTree" option
[13:02:31 CDT(-0500)] <Bosmon> This was what the API was always intended to be
[13:02:36 CDT(-0500)] <Bosmon> Only before the weekend this was broken
[13:02:57 CDT(-0500)] <Bosmon> So in the component's options, produceTree: "my.produce.function"
[13:02:57 CDT(-0500)] <cindyli> let me try, Bosmon
[13:03:27 CDT(-0500)] <Bosmon> I'd like to join too, jameswy
[13:08:34 CDT(-0500)] <cindyli> Bosmon: the workaround works perfectly. THANKS.
[14:29:29 CDT(-0500)] <colinclark> mlam and Bosmon: What's the latest with the Uploader, dudes?
[14:29:47 CDT(-0500)] <mlam> colinclark: Just waiting for Bosmon's review
[14:30:26 CDT(-0500)] <Bosmon> Ok, sorry
[14:30:34 CDT(-0500)] <Bosmon> I will go and review
[14:30:41 CDT(-0500)] <mlam> Thanks Bosmon
[14:31:56 CDT(-0500)] <colinclark> Thanks Bosmon
[14:32:05 CDT(-0500)] <colinclark> Once you're done that, let's chat here a bit about next steps for options chewing, Bosmon
[14:32:13 CDT(-0500)] <colinclark> picking up our conversation from last week
[14:32:29 CDT(-0500)] <heidi_> michelled_ i added notes from the meeting to the bottom of http://wiki.fluidproject.org/display/fluid/UI+Options+1.4+Roadmap ...miss anything?
[15:04:20 CDT(-0500)] <colinclark> jameswy: Should we update this page to point to your latest and greatest designs? http://wiki.fluidproject.org/display/fluid/User+Interface+Options+Wireframes
[15:07:02 CDT(-0500)] <Bosmon> Hi mlam - the tests look much better factored now, cool
[15:07:13 CDT(-0500)] <Bosmon> I wonder if you remember our chat on Friday about "orthogonality"?
[15:07:59 CDT(-0500)] <mlam> I thought about our chat with regards to orthogonality, and it seemed difficult since the set up for both flash and html5 are so different
[15:08:19 CDT(-0500)] <Bosmon> Yes - but I wonder if the repeated code in your test cases still looks a little suspicious to you
[15:08:30 CDT(-0500)] <mlam> so to loop through the different uploading strategies and the different setups in one clean swoop didn't seem possible.
[15:08:43 CDT(-0500)] <Bosmon> Well, let's start in small steps
[15:08:50 CDT(-0500)] <jameswy> colinclark: Sounds like a good idea. I'll do that.
[15:09:03 CDT(-0500)] <Bosmon> So, from line 422 to line 455 you have 6 tests which are all very similar
[15:09:17 CDT(-0500)] <Bosmon> They all start with line 1) set up something in the environment
[15:09:23 CDT(-0500)] <Bosmon> 2) instantiate something
[15:09:25 CDT(-0500)] <Bosmon> 3) check something
[15:09:56 CDT(-0500)] <mlam> right
[15:09:59 CDT(-0500)] <Bosmon> Can you think of a way to deal with those 6 tests, along the lines that we were talking last week?
[15:12:29 CDT(-0500)] <mlam> Create a function that takes in an uploader along with a function that sets the environmental variables and a function that determines what test to run?
[15:13:06 CDT(-0500)] <mlam> and in that function, execute the 2 functions?
[15:13:48 CDT(-0500)] <Bosmon> Yes, that would get rid of a lot of the duplication - do you want to sketch it out here?
[15:14:33 CDT(-0500)] <mlam> Ok, sure
[15:14:53 CDT(-0500)] <Bosmon> So - remember the aim with test code is the same as with real code
[15:15:04 CDT(-0500)] <Bosmon> You want to make the task of someone who invents a "new thing" as easy as possible
[15:15:23 CDT(-0500)] <Bosmon> So - someone either invents a new uploader configuration, or they invent a new kind of test case
[15:15:34 CDT(-0500)] <Bosmon> You want to provide them with as far as possible a "one stop shop"
[15:15:48 CDT(-0500)] <Bosmon> That is, one place they can add their "new thing in", that doesn't require them to do any cut and paste
[15:16:06 CDT(-0500)] <mlam> var genericTestFunction = function (uploader, setUploaderEnv, runTests) {
[15:16:07 CDT(-0500)] <mlam> setUploaderEnv();
[15:16:07 CDT(-0500)] <mlam> runTests(uploader);
[15:16:07 CDT(-0500)] <mlam> }
[15:16:15 CDT(-0500)] <mlam> ew, that did not come up right.
[15:16:29 CDT(-0500)] <Bosmon> Well, it's close enough
[15:16:43 CDT(-0500)] <Bosmon> So, what would the code calling this function look like?
[15:18:44 CDT(-0500)] <mlam> I guess for html5, genericTestFunction (fluid.uploader($(container)), setHTML5Env, checkHTML5IntegrationTests)
[15:19:03 CDT(-0500)] <mlam> so each test would be a one liner
[15:19:41 CDT(-0500)] <Bosmon> Ok - so - Socrates asks - if it looked like that - would there actually be very much total savings in code?
[15:20:05 CDT(-0500)] <mlam> Yes, I would save 2 lines of code every single time i wanted to add a new test
[15:20:06 CDT(-0500)] <Bosmon> So - here is a Socratic question - how MANY calls would you really like to see to "genericTestFunction" in your testing file?
[15:20:27 CDT(-0500)] <Bosmon> That is, how many calls would you like to see written out
[15:20:36 CDT(-0500)] <Bosmon> Or ok, put it another way - what is the minimum number you think you could achieve
[15:20:42 CDT(-0500)] <mlam> as many times as there are integration tests, so in our case 6
[15:20:55 CDT(-0500)] <Bosmon> Do you think you could do better than that?
[15:22:24 CDT(-0500)] <mlam> It wouldn't work if I set up all uploaders first before running these tests because the static env. variables would counteract with each other, no?
[15:22:33 CDT(-0500)] <Bosmon> That's right
[15:22:47 CDT(-0500)] <mlam> then, no. This is probably the best that i could do
[15:22:47 CDT(-0500)] <Bosmon> So this suggests that the function needs a little adjustment itself - but I think that's a separate issue
[15:23:06 CDT(-0500)] <Bosmon> Do you think you could write an expression of the test cases that just has ONE call to "genericTestFunction"?
[15:24:09 CDT(-0500)] <mlam> I'm not sure, but I think you're implying yes.
[15:24:32 CDT(-0500)] <Bosmon> I think you could do it
[15:25:02 CDT(-0500)] <mlam> but how?
[15:26:06 CDT(-0500)] <Bosmon> So, I'm not sure what the "key innovation" is
[15:26:16 CDT(-0500)] <Bosmon> But one important element is to move the test case into the INSIDE of the function
[15:26:29 CDT(-0500)] <Bosmon> You can see this pattern used in a few of our framework test cases
[15:26:51 CDT(-0500)] <Bosmon> The second important element is to break out what you currently have written in code, into a configuration data structure
[15:27:07 CDT(-0500)] <Bosmon> So, schematically, the ONE test case should look like this:
[15:27:23 CDT(-0500)] <Bosmon> for (configuration in configurations) {
[15:27:42 CDT(-0500)] <Bosmon> for (integration in integrations) {
[15:27:56 CDT(-0500)] <Bosmon> issueTestCase(configuration, integration);
[15:27:57 CDT(-0500)] <Bosmon> }
[15:27:58 CDT(-0500)] <Bosmon> }
[15:28:03 CDT(-0500)] <Bosmon> Does that make sense?
[15:28:32 CDT(-0500)] <mlam> It makes sense, but how do you get all the configurations returned without the static env. variables interfering with each other?
[15:28:45 CDT(-0500)] <Bosmon> So, the actual call to the function which performs the test case doesn't literally show "checkHTML5IntegrationTests" but just a variable name
[15:29:05 CDT(-0500)] <Bosmon> Well, actually they are liable to interfere with each other right now - this was another stylistic point I was meaning to bring up again
[15:29:14 CDT(-0500)] <mlam> would we then have an array of html5 configurations then loop through them? and do the same for flash?
[15:29:19 CDT(-0500)] <Bosmon> It is best to put all manipulation of the static environment into a try {} finally {} block
[15:29:38 CDT(-0500)] <Bosmon> So that if a test misfires, you don't leave junk in the static environment - it makes the status of failed test cases easier to read
[15:29:54 CDT(-0500)] <Bosmon> So "configurations" includes things like HTML5, Flash, SingleFile
[15:30:08 CDT(-0500)] <Bosmon> and "integrations" includes things like "direct function", "Simple IoC" "IoC with demands"
[15:30:25 CDT(-0500)] <Bosmon> And you loop over these orthogonally, like in the nested loops above
[15:30:49 CDT(-0500)] <Bosmon> So, your issueTestCase function is a "one stop shop" - it does ALL the work necessary to set up the environment, instantiate the uploader, issue the test cases, and clean up afterwards
[15:31:35 CDT(-0500)] <Bosmon> So, say that you have N configurations and M integrations
[15:32:00 CDT(-0500)] <Bosmon> The advantage of this approach is that if someone invents a new one of either of these sets, the person who maintains the test cases just needs to add O(1) material into configuration
[15:32:16 CDT(-0500)] <Bosmon> Whereas the way they are written now, they have to add O(N) or O(M) stuff via cut and paste
[15:33:33 CDT(-0500)] <mlam> Ok, so the configurations and integrations will be global arrays and every time i set a configuration and an integration up, I add it to this array. Right?
[15:34:02 CDT(-0500)] <Bosmon> That's right, you've got it
[15:34:35 CDT(-0500)] <mlam> And the try/finally blocks will prevent any static env. clashing
[15:34:35 CDT(-0500)] <Bosmon> Hopefully global, but suitably namespaced arrays
[15:34:39 CDT(-0500)] <mlam> right
[15:34:45 CDT(-0500)] <Bosmon> Yup, that's right
[15:35:20 CDT(-0500)] <mlam> Ok. I'll have it ready for you when you're online tomorrow
[15:36:16 CDT(-0500)] <mlam> Thanks for taking a look Bosmon.
[15:36:24 CDT(-0500)] <mlam> and thanks for the pointers
[15:37:16 CDT(-0500)] <Bosmon> Ok, look forward to it
[15:37:17 CDT(-0500)] <Bosmon> np
[15:42:37 CDT(-0500)] <Bosmon> Oh, mlam, another tip - you can retain the readability of the test case message strings by separating out the different pieces of them into the different configuration areas - and the concatenating them together again when you come to actually issue the test case
[15:43:08 CDT(-0500)] <mlam> ok, cool
[15:45:08 CDT(-0500)] <mlam> Bosmon: so to unregister a typeTag from the static environment, I set the new value to ""?
[15:45:22 CDT(-0500)] <Bosmon> mlam - you should use the JavaScript "delete" operator
[15:45:59 CDT(-0500)] <mlam> ah ok
[15:46:06 CDT(-0500)] <mlam> thanks
[15:46:21 CDT(-0500)] <Bosmon> So for example, look at FluidIoCTests.js, line 308
[15:46:30 CDT(-0500)] <Bosmon> You can see an example of this techique in action
[15:47:59 CDT(-0500)] <mlam> got it