fluid-work IRC Logs-2011-03-03

[09:07:29 CST(-0600)] <Justin_o> michelled, colinclark: I'm looking at fixing up our "global" comment at the top of the js files
[09:07:38 CST(-0600)] <Justin_o> they are pretty inconsistent throughout
[09:07:45 CST(-0600)] <Justin_o> so i could collapse them all to a single line
[09:07:50 CST(-0600)] <colinclark> Justin_o: +1
[09:08:04 CST(-0600)] <colinclark> I tried to collapse any of the ones I encountered along the way for 1.3
[09:08:07 CST(-0600)] <Justin_o> or maybe try to organize it like javascript global, ours, third party ones
[09:08:35 CST(-0600)] <colinclark> One line is probably easiest, but in that order
[09:09:01 CST(-0600)] <jessm> Justin_o: michelled: jameswy i can see wiki, jira
[09:09:05 CST(-0600)] <jessm> still no chat server
[09:09:09 CST(-0600)] <jessm> jamon: ^
[09:09:18 CST(-0600)] <Justin_o> jessm: i was just able to connect to some external sites now too
[09:10:30 CST(-0600)] <Justin_o> colinclark: thanks, i'll do that
[09:14:24 CST(-0600)] <colinclark> jameswy: What do you imagine will go in your average Preview box for UI Options?
[09:14:27 CST(-0600)] <colinclark> Will there be such a thing?
[09:14:33 CST(-0600)] <colinclark> For 1.1
[09:14:45 CST(-0600)] <colinclark> Will implementers generally create their own preview?
[09:14:48 CST(-0600)] <colinclark> Will we ship a default?
[09:16:56 CST(-0600)] <jameswy> colinclark: We'll ship a default, composed of basic headers, text, and inputs.
[09:16:57 CST(-0600)] <jameswy> I think the preview should look artificial, and difficult to mistake as an actual website.
[09:16:57 CST(-0600)] <jameswy> Designs for that are on the way.
[09:17:45 CST(-0600)] <colinclark> Okay, cool
[09:17:48 CST(-0600)] <colinclark> that makes sense
[09:18:29 CST(-0600)] <colinclark> michelled and I are just going through the wireframes, JIRA, and the current state of affairs of UI Options to plan the 1.4 work
[09:19:07 CST(-0600)] <jameswy> Nice!
[09:22:42 CST(-0600)] <colinclark> jameswy: Did you actively get rid of the background images setting in UI Options for 1.4?
[09:22:51 CST(-0600)] <colinclark> Or has it been folded into a different preference?
[09:27:40 CST(-0600)] <jameswy> colinclark: It's been folded into the contrast selectors
[09:27:58 CST(-0600)] <jameswy> So, selecting a different contrast setting will force backgrounds off.
[09:28:05 CST(-0600)] <colinclark> k, cool
[09:28:12 CST(-0600)] <jameswy> Thanks for noting that--I'll make sure I make a note of it on the page
[09:28:18 CST(-0600)] <colinclark> thanks!
[09:28:41 CST(-0600)] <michelled> jameswy: I was just looking at some of the UI Options JIRAs. when you get a chance, can you take a peek at this one? It's about user confusion when using reset. http://issues.fluidproject.org/browse/FLUID-2838
[09:32:38 CST(-0600)] <colinclark> jameswy: Do you mind if I run past you my list of "major differences between the full-page and panel versions of UI Options?" list?
[09:32:42 CST(-0600)] <colinclark> Just to make sure I'm seeing it correctly
[09:33:20 CST(-0600)] <jameswy> colinclark: Yep
[09:33:36 CST(-0600)] <colinclark> 1. No preview in the panel versions
[09:33:53 CST(-0600)] <colinclark> 2. Each section of the full-page version is split out into its own menu in the panel versions
[09:34:07 CST(-0600)] <colinclark> 3. Save is automatic in the panel versions. Cancel is not present at all.
[09:34:42 CST(-0600)] <colinclark> That really seems to be the bulk of it
[09:34:48 CST(-0600)] <colinclark> anything else I'm missing, jameswy?
[09:35:46 CST(-0600)] <jameswy> colinclark: That sounds correct!
[09:35:51 CST(-0600)] <colinclark> Cool
[09:36:42 CST(-0600)] <jameswy> colinclark: I might note that design-wise, when we were thinking about the individual options (e.g., text size, simplify layout, etc.), we thought of them as modular pieces that could be moved around, extracted, etc.
[09:36:56 CST(-0600)] <colinclark> cool
[09:37:00 CST(-0600)] <colinclark> Code-wise, too (smile)
[09:37:34 CST(-0600)] <jameswy> There was also some thought into whether we could pull these individual Lego-pieces out to integrate into the page directly, without any UI options present.
[09:38:03 CST(-0600)] <jameswy> e.g., have the text slider bar module integrated into the content somewhere, independent of any UI options interface.
[09:39:44 CST(-0600)] <jameswy> michelled: Thanks for pointing me to that JIRA. The current positioning/wording feels appropriate to me for the time being, but I'll definitely think more around it.
[09:44:20 CST(-0600)] <michelled> thanks jameswy
[09:46:21 CST(-0600)] <Justin_o> michelled, colinclark: from what i can tell... jslint doesn't complain about globals that are core js functions.. should i pull them out of the global comment or do think it is usefull to see them there
[09:46:39 CST(-0600)] <michelled> like what?
[09:46:47 CST(-0600)] <colinclark> window, for example?
[09:48:40 CST(-0600)] <colinclark> jessm, jameswy: Have we officially decided on a branding for FLOE that involves mixed case?
[09:48:44 CST(-0600)] <colinclark> i.e. Floe?
[09:48:46 CST(-0600)] <colinclark> or floe?
[09:49:18 CST(-0600)] <jessm> colinclark: i think jameswy and i thought 'floe' was the way to go?
[09:49:21 CST(-0600)] <jessm> edgy, no?
[09:49:24 CST(-0600)] <colinclark> super hip
[09:49:26 CST(-0600)] <jessm> certainly not FLOE
[09:49:27 CST(-0600)] <Justin_o> colinclark: yes.. like document, Math, setTimeout
[09:49:29 CST(-0600)] <Justin_o> etc.
[09:49:37 CST(-0600)] <colinclark> maybe we could add some brackets or slashes to be very postmodern
[09:49:39 CST(-0600)] <colinclark> fl/oe
[09:49:41 CST(-0600)] <jessm> and perhaps permissibly Floe
[09:49:42 CST(-0600)] <colinclark> (fl)oe
[09:49:53 CST(-0600)] <jessm> fl(o)e
[09:49:55 CST(-0600)] <jessm> i like that one
[09:49:56 CST(-0600)] <Justin_o> michelled: see my comment to colinclark above
[09:49:56 CST(-0600)] <colinclark> hip hip hip
[09:50:19 CST(-0600)] <colinclark> Remind me to put on my black baret
[09:50:43 CST(-0600)] <jessm> colinclark: in my wiki slashing i've been changing all FLOEs to floe
[09:50:50 CST(-0600)] <colinclark> Justin_o: I'm guessing the "assume a browser" option causes the lack of complaint?
[09:50:59 CST(-0600)] <Justin_o> colinclark: ah.. that would make sense
[09:51:10 CST(-0600)] <colinclark> jessm: So if I'm creating a new FLOE development page, I should call it "floe development?"
[09:51:14 CST(-0600)] <jameswy> jessm: Ah! I thought we were going with "Floe". I can start using "floe" though.
[09:51:43 CST(-0600)] <michelled> Justin_o: I think that if our settings are already taking care of those global words then we should take them out of the global definition
[09:51:55 CST(-0600)] <michelled> it will simplfy the global definition
[09:52:06 CST(-0600)] <Justin_o> michelled, colinclark: that is true.. okay i'll yank them out
[09:52:11 CST(-0600)] <jessm> jameswy: i'm flexible – Floe or floe – do we need to settle on one? straws?
[09:52:12 CST(-0600)] <Justin_o> thanks
[09:52:30 CST(-0600)] <mlam> colinclark: are you going to be in the office today?
[09:52:37 CST(-0600)] <jessm> colinclark: indeed i'm being inconsistent – in the wiki nav i have Floe
[09:52:45 CST(-0600)] <colinclark> mlam: Yep, in time for the FSS meeting at the very latest
[09:52:52 CST(-0600)] <colinclark> Is it on fire or something?
[09:52:54 CST(-0600)] <colinclark> (tongue)
[09:53:02 CST(-0600)] <jessm> when it starts a sentence maybe "Floe" otherwise floe?
[09:53:08 CST(-0600)] <jameswy> I've never really felt comfortable with all lowercase for proper names--what's the rule for starting sentences?
[09:53:14 CST(-0600)] <jameswy> Exactly. anastasiac?
[09:53:15 CST(-0600)] <jameswy> ^
[09:53:33 CST(-0600)] <jessm> i'm comfortable slipping between Floe and floe – just not FLOE
[09:53:49 CST(-0600)] <jessm> jameswy: should i be encouraged to feel less comfortable?
[09:54:09 CST(-0600)] <mlam> colinclark: ok, cool . I've created a branch on gitHub with my model transformation work so far. I was wondering if you could take a look to make sure I'm on the right track, and if yes, help me hook everything up?
[09:54:22 CST(-0600)] <anastasiac> I think we should capitalize it at the beginning of a sentence. It's jarring, otherwise - harder for the brain to process. we're very accustomed to conventions
[09:54:47 CST(-0600)] <colinclark> mlam: sure
[09:54:50 CST(-0600)] <jessm> anastasiac: to complicate your rule look at floeproject.org and tell me if Floe News should be floe News or floe news
[09:54:57 CST(-0600)] <colinclark> let's do that this afternoon if you can wait that long
[09:55:02 CST(-0600)] <jameswy> jessm: it really doesn't matter to me, (smile)
[09:55:22 CST(-0600)] <anastasiac> jessm: "Floe News"
[09:55:38 CST(-0600)] <mlam> yup, for sure. I need to refactor my tests anyways
[09:55:59 CST(-0600)] <anastasiac> titles should be capitalized, and this is a title
[09:56:04 CST(-0600)] <jessm> i hereby declare us "fairly" comfortable with Floe and floe but not FLOE – Floe for headers and sentence starting – floe for edginess and hip uses (like the logo) on floeproject.org
[09:56:18 CST(-0600)] <jessm> can i get a witness?
[09:56:52 CST(-0600)] <colinclark> +1, jessm
[09:57:05 CST(-0600)] <anastasiac> I'm not horribly fond of the lowercase version, but I can witness (smile) Are we allowed to capitalize it in the middle of a sentence?
[09:57:21 CST(-0600)] <Justin_o> take a look at this
[09:57:21 CST(-0600)] <Justin_o> http://www.flickr.com/
[09:57:35 CST(-0600)] <Justin_o> the logo has all lower case, but the page title and links use Flickr
[09:57:37 CST(-0600)] <jessm> Justin_o: they do it too!
[09:57:56 CST(-0600)] <colinclark> I still prefer (fl)oe
[09:57:59 CST(-0600)] <jessm> i hereby declare us almost as cool as Flickr when it comes to capitalization
[09:58:02 CST(-0600)] <colinclark> or maybe with a but of uppercase flourish
[09:58:04 CST(-0600)] <colinclark> (fl)OE
[09:58:06 CST(-0600)] <jameswy> f|0E!
[09:58:08 CST(-0600)] <Justin_o> colinclark: how about fl-oe
[09:58:11 CST(-0600)] <Justin_o> make it more FSS like
[09:58:14 CST(-0600)] <colinclark> jameswy: yes!
[09:58:16 CST(-0600)] <jessm> Justin_o: ooohhh, pretty
[09:58:19 CST(-0600)] <colinclark> Justin_o: pretty hip
[09:58:20 CST(-0600)] <anastasiac> logos are different visually
[09:58:41 CST(-0600)] <jessm> so, we logo floe and use it in hipster situations and we Floe otherwise
[09:58:50 CST(-0600)] <colinclark> jessm: +1
[09:58:53 CST(-0600)] <jameswy> jessm: +1
[09:58:54 CST(-0600)] <anastasiac> I like (fl)oe - very cummings
[09:59:02 CST(-0600)] <jessm> and anastasiac you can decide depending on the context of the sentence if you want to be hip or capitalize
[09:59:13 CST(-0600)] <anastasiac> oh, I'm very un-hip in general
[09:59:32 CST(-0600)] <jessm> anastasiac: then we will keep you away from lowercase logos (wink)
[09:59:52 CST(-0600)] <anastasiac> logos are different than narrative text, though
[10:00:01 CST(-0600)] <jessm> yes
[10:00:06 CST(-0600)] <jessm> floe logo – Floe text
[10:00:42 CST(-0600)] <jessm> anastasiac: have you and jon combined heads yet on the mindmap and scenarios?
[10:00:43 CST(-0600)] <jameswy> And public hangings for FLOE.
[10:00:50 CST(-0600)] <jessm> +1
[10:00:55 CST(-0600)] <jessm> jhung: ^
[10:01:05 CST(-0600)] <jessm> jhung: ^^ – not the hanging bit (wink)
[10:01:07 CST(-0600)] <anastasiac> jessm, yes, we talked this morning and went over his stuff, brainstormed, etc.
[10:01:21 CST(-0600)] <jessm> anastasiac: cool – send out a link when you're ready for feedback
[10:01:34 CST(-0600)] <colinclark> jameswy: People are oddly obsessed with acronyms
[10:01:42 CST(-0600)] <anastasiac> jhung and erin are going to start working on a structural outline for the stuff
[10:01:43 CST(-0600)] <colinclark> there are those among us who still use FLUID consistently
[10:02:07 CST(-0600)] <jessm> colinclark: interestingly i think we have a 'fluid' logo and Fluid otherwise... pattern?
[10:02:20 CST(-0600)] <colinclark> Seems like!
[10:02:34 CST(-0600)] <colinclark> Yes, our canonical new logo is lower case
[10:02:55 CST(-0600)] <colinclark> it's hipper, too--monochrome
[10:02:56 CST(-0600)] * jessm can't wait until said 'fluid' logo is on fluidproject.org
[10:03:05 CST(-0600)] <jessm> erin and jameswy are on that i hope!
[10:03:15 CST(-0600)] <colinclark> yay!
[10:05:58 CST(-0600)] <jessm> anastasiac: i've been staring at these two things lately: https://github.com/acheetham/infusion/tree/FLUID-4120 and http://wiki.fluidproject.org/pages/viewpage.action?pageId=3900010 and humming quietly about planned redundancy – ideas?
[10:07:48 CST(-0600)] <colinclark> Speaking of FLUID-4120, anastasiac, I really like what you've done
[10:08:09 CST(-0600)] <colinclark> I'm wondering if I could fork your repo and make a few tweaks--mostly to copy about Infusion I wrote years ago and am now embarrassed of
[10:08:15 CST(-0600)] <colinclark> And then I think we're ready to push it on up to the project repo
[10:08:22 CST(-0600)] <anastasiac> well, for one thing jessm, FLUID-4120 is about Infusion, not Fluid: see http://fluidproject.org/products/infusion/ for some redundancy
[10:08:45 CST(-0600)] <anastasiac> colinclark, you could just to ahead and edit my branch, can't you?
[10:08:48 CST(-0600)] <jessm> anastasiac: see what is infusion on that page...
[10:09:42 CST(-0600)] <jessm> colinclark: i quite like the small section on "why use fluid infusion" on this page http://wiki.fluidproject.org/pages/viewpage.action?pageId=3900010 – it's something i don't think we have at the infusion homepage
[10:10:02 CST(-0600)] <anastasiac> yes, ok, sorry - didn't scroll. yes, this was planned redundancy. I was trying to not write a whole new, different description of Infusion
[10:10:08 CST(-0600)] <colinclark> cool
[10:10:31 CST(-0600)] <colinclark> anastasiac: Yep, I'll fork it, make some changes and then push them back up to your Infusion fork
[10:10:35 CST(-0600)] <colinclark> I had forgotten I have write access
[10:10:41 CST(-0600)] <jessm> colinclark: so, perhaps in the re-write of infusion we duplicate on the 1. infusion homepage, 2. on this page in the wiki, and 3. in github
[10:10:52 CST(-0600)] <colinclark> jessm: I'd really like to do that
[10:10:58 CST(-0600)] <colinclark> Was that an invitation? (tongue)
[10:11:00 CST(-0600)] <jessm> cool
[10:11:19 CST(-0600)] <jessm> colinclark: yes, i felt a kind of "shazam" in thinking about it
[10:11:23 CST(-0600)] <colinclark> (smile)
[10:11:29 CST(-0600)] <colinclark> "Make it so"
[10:11:45 CST(-0600)] <colinclark> Okay, so here's my list of writing tasks for this week and likely into early next week, then:
[10:11:51 CST(-0600)] <colinclark> 1. Polish up the GSoC project descriptions
[10:11:57 CST(-0600)] <michelled> jameswy: while you are thinking about the reset functionality, can you also look at 3873?
[10:12:02 CST(-0600)] <jessm> ^ that's very close with some jameswy love
[10:12:02 CST(-0600)] <colinclark> 2. Write some ModelTransformation documentation
[10:12:22 CST(-0600)] <colinclark> 3. Rewrite overviews of Infusion with jessm and anastasiac
[10:12:39 CST(-0600)] <colinclark> #3 written with planned redundancy in mind
[10:12:43 CST(-0600)] <colinclark> aka reuse
[10:12:43 CST(-0600)] <jessm> (wink)
[10:12:48 CST(-0600)] <michelled> jameswy: I meant 3973 "Selecting reset changes the preview pane to default, but user has to press "save and apply" for the changes to take effect"{color}
[10:13:31 CST(-0600)] <jameswy> michelled: Yep. Thanks!

[10:16:17 CST(-0600)] <Justin_o> colinclark: is this a bug
[10:16:18 CST(-0600)] <Justin_o> https://github.com/fluid-project/infusion/blob/master/src/webapp/components/inlineEdit/js/InlineEditIntegrations.js
[10:16:24 CST(-0600)] <Justin_o> if you look at the bottom of the file
[10:16:48 CST(-0600)] <Justin_o> the FCKeditor_OnComplete function calls fluid.inlineEdit.FCKEditor.complete.fire(editorInstance);
[10:16:59 CST(-0600)] <Justin_o> this is outside of the closure
[10:17:04 CST(-0600)] <Justin_o> which there is a comment for
[10:17:09 CST(-0600)] <colinclark> Justin_o: I don't think so, no
[10:17:12 CST(-0600)] <colinclark> Let me remind myself, though
[10:17:19 CST(-0600)] <Justin_o> but the inlineEdit is hanging off of fluid instead of fluid_1_4
[10:18:05 CST(-0600)] <Justin_o> assuming this never changes i guess it's fine, but I would imagine it wouldn't support our versioning scheme
[10:20:21 CST(-0600)] <colinclark> Justin_o: I will attempt an argument
[10:20:25 CST(-0600)] <colinclark> (smile)
[10:20:29 CST(-0600)] <colinclark> So, I think it's not a bug
[10:20:41 CST(-0600)] <colinclark> The old version of FCKEditor is pretty funny
[10:20:48 CST(-0600)] <colinclark> it requires this global function to be present
[10:21:12 CST(-0600)] <colinclark> So, we might as well think of FCKEditor as being specifically incompatible with the notion of multiple versions of Infusion
[10:21:21 CST(-0600)] <colinclark> It's totally not portal-friendly, in other words
[10:21:29 CST(-0600)] <Justin_o> colinclark: ah...
[10:21:31 CST(-0600)] <Justin_o> interesting
[10:21:32 CST(-0600)] <colinclark> So we're falling back on the best case scenario in this context, I think
[10:21:47 CST(-0600)] <colinclark> Using the latest loaded version of Infusion
[10:22:01 CST(-0600)] <Justin_o> colinclark: so CKEditor doesn't have this problem?
[10:22:09 CST(-0600)] <colinclark> Justin_o: No, it doesn't
[10:22:13 CST(-0600)] <colinclark> So, yes, I'm now convinced
[10:22:24 CST(-0600)] <colinclark> So, even if the file used our versioned namespace
[10:22:28 CST(-0600)] <colinclark> fluid_1_4
[10:22:35 CST(-0600)] <colinclark> Imagine two instances of this file get loaded into a portal
[10:22:52 CST(-0600)] <colinclark> In this order, let's say: Infusion 1.4 first, then Infusion 1.3
[10:23:35 CST(-0600)] <colinclark> The first time Infusion loads, this FCKeditor_OnComplete() function will be bound to the fluid_1_4 code
[10:23:40 CST(-0600)] <colinclark> Then, 1.3 will get loaded
[10:23:49 CST(-0600)] <colinclark> rebinding FCKeditor_OnComplete() to fluid_1_3
[10:24:09 CST(-0600)] <colinclark> Meaning, by using the generic fluid namespace, this code is being explicit about how it works
[10:24:22 CST(-0600)] <colinclark> It doesn't pretend to be multi version resistant
[10:24:25 CST(-0600)] <colinclark> Does that make sense, Justin_o?
[10:24:57 CST(-0600)] <Justin_o> colinclark: okay... so i'll accept that.. and pose a new question.. can we drop support for FCKEditor
[10:26:09 CST(-0600)] <colinclark> Did we deprecate it in 1.2 or 1.3?
[10:26:38 CST(-0600)] <Justin_o> colinclark: i don't remember.. it is still in sneak peek i think
[10:26:45 CST(-0600)] <colinclark> ok
[10:26:58 CST(-0600)] <colinclark> Should we specifically deprecate it for 1.4, then remove it in 1.5?
[10:27:07 CST(-0600)] <colinclark> I may have already deprecated it, let me check
[10:27:32 CST(-0600)] <colinclark> yes, I did
[10:27:59 CST(-0600)] <colinclark> "Support for FCKEditor 2.x is now deprecated. We recommend the use of the simpler and more accessible CKEditor 3 instead."
[10:45:29 CST(-0600)] <Justin_o> colinclark: that's great, when did you do that
[10:45:35 CST(-0600)] <Justin_o> was that for 1.2?
[10:49:20 CST(-0600)] <colinclark> Here's the UI Options roadmap that michelled, jameswy, and I collaborated on this morning: http://wiki.fluidproject.org/display/fluid/UI+Options+1.4+Roadmap
[10:49:20 CST(-0600)] <colinclark> michelled and I are gonna go ahead and toss the accordion right away--so cool!
[10:49:35 CST(-0600)] <colinclark> Justin_o: I don't fully remember
[10:49:41 CST(-0600)] <colinclark> It was whenever I added support for CKEditor
[10:49:43 CST(-0600)] <colinclark> it must have been 1.2
[10:54:04 CST(-0600)] <Justin_o> colinclark: thanks.. so i'll file a jira about dropping fckeditor support
[10:54:54 CST(-0600)] <colinclark> great
[11:59:50 CST(-0600)] <Justin_o> fluid-everyone: the FSS talk is going to start soon... anyone else interested in being skyped in, please let me know
[12:00:06 CST(-0600)] * jessm waves, me me me
[12:00:16 CST(-0600)] <Justin_o> jessm: I have you my list (smile)
[14:12:44 CST(-0600)] <harriswong1> justin_o: I think this #FLUID-3987 is now fixed along with the error handler. I have realigned the button in IE8
[14:13:11 CST(-0600)] <Justin_o> harriswong1: nice work
[14:13:20 CST(-0600)] <Justin_o> will you send along a pull request soon
[14:14:06 CST(-0600)] <harriswong1> justin_o: i thought it's dependent on the flash error thing, should i still send a pull?
[14:14:13 CST(-0600)] <Justin_o> ah
[14:14:16 CST(-0600)] <Justin_o> forgot about that
[14:14:36 CST(-0600)] <Justin_o> i suppose you could still ask for the pull request and then add that info in.. since you will be heading out on vacation soon
[14:14:45 CST(-0600)] <Justin_o> i'll poke colin to see if he has an opinion
[14:15:18 CST(-0600)] <harriswong1> Justin_o: okie.
[14:16:17 CST(-0600)] <colinclark> harriswong1: Do you want to chat tomorrow, and we can walk through your latest code?
[14:16:24 CST(-0600)] <colinclark> I have a bit of feedback before you head off on vacation
[14:17:04 CST(-0600)] <harriswong1> colinclark: sure
[14:17:23 CST(-0600)] <colinclark> cool
[14:35:36 CST(-0600)] <Justin_o> colinclark, mlam: what is FormData? is it a native javascript function?
[14:35:48 CST(-0600)] <colinclark> It's a browser API
[14:36:15 CST(-0600)] <colinclark> In modern browsers--FF4, Chrome and Safari 4+
[14:36:30 CST(-0600)] <Justin_o> colinclark: okay.. thanks...
[14:36:56 CST(-0600)] <Justin_o> colinclark: so it would be like calling document?
[14:37:53 CST(-0600)] <harriswong1> colinclark: i have pushed the latest FLUID-3878 commits to github
[14:38:03 CST(-0600)] <colinclark> You mean in terms of globals, Justin_o?
[14:38:29 CST(-0600)] <Justin_o> colinclark: yes.. sorry.. should have made that clear
[14:39:11 CST(-0600)] <colinclark> yes, it's a method on window, Justin_o
[14:39:15 CST(-0600)] <colinclark> or rather
[14:39:18 CST(-0600)] <colinclark> an object on window
[14:40:26 CST(-0600)] <Justin_o> colinclark: okay.. thanks
[14:41:12 CST(-0600)] <cindyli> Justin_o: i'm done with achecker. now looking for work in fluid
[14:41:21 CST(-0600)] <colinclark> yay!
[14:42:53 CST(-0600)] <Justin_o> cindyli: (smile) that's great..
[14:43:02 CST(-0600)] <Justin_o> I think we can find something for you
[14:43:45 CST(-0600)] <cindyli> ok
[14:44:40 CST(-0600)] <Justin_o> cindyli: it would be great to replace the current uploader server, i think colin may have mentioned it briefly in a meeting here or there
[14:45:08 CST(-0600)] <Justin_o> we should probably meet with colinclark, mlam, and myself to discuss it.. any time tomorrow good for everyone
[14:45:30 CST(-0600)] <mlam> Anytime is good for me, Justin_o
[14:45:39 CST(-0600)] <cindyli> Justin_o: good for me
[14:46:15 CST(-0600)] <Justin_o> colinclark: do you have a preferred time?
[14:46:48 CST(-0600)] <colinclark> i'm flexible
[14:47:19 CST(-0600)] <Justin_o> colinclark, mlam, cindyli: how about tomorrow morning some time
[14:47:40 CST(-0600)] <cindyli> cindyli: sure. anytime
[14:47:53 CST(-0600)] <mlam> Same here
[14:48:01 CST(-0600)] <mlam> morning sounds good.
[14:48:32 CST(-0600)] <Justin_o> colinclark: do you have time in the morning?
[14:49:09 CST(-0600)] <colinclark> sure, as long as we define "morning" in relative terms
[14:50:12 CST(-0600)] <Justin_o> colinclark: i'll let you define morning, since i think it's quite different from my view (smile)
[14:50:19 CST(-0600)] <colinclark> lol
[14:50:27 CST(-0600)] <colinclark> 10:00 am?
[14:50:35 CST(-0600)] <Justin_o> sounds good to me
[14:50:37 CST(-0600)] <mlam> Ok
[14:51:49 CST(-0600)] <cindyli> ok
[14:51:49 CST(-0600)] <Justin_o> cindyli: ^
[14:51:54 CST(-0600)] <Justin_o> okay.. 10 it is
[14:51:57 CST(-0600)] <Justin_o> i'll add it to the calendar
[14:52:46 CST(-0600)] <Justin_o> cindyli: if you are looking for work between now and then, maybe you could work with jamon to get the daily build of the builder running again.. i can help too if needed
[14:53:13 CST(-0600)] <cindyli> cindyli: sure, will talk with jamon
[14:53:44 CST(-0600)] <Justin_o> cindyli: thanks
[14:53:53 CST(-0600)] <mlam> colinclark: do you have time this afternoon to look over my file type inclusion work?
[14:53:54 CST(-0600)] <cindyli> np
[14:54:06 CST(-0600)] <colinclark> mlam: I'm screwed this aft
[14:54:11 CST(-0600)] <colinclark> Send me a URL and I'll look
[14:54:15 CST(-0600)] <colinclark> we'll chat tomorrow
[14:54:16 CST(-0600)] <mlam> ok
[14:54:22 CST(-0600)] <colinclark> It's Day of Uploader for me tomorrow
[14:54:28 CST(-0600)] <colinclark> And you're first on the list
[14:54:53 CST(-0600)] <mlam> cool (smile)
[14:55:02 CST(-0600)] <mlam> colin, link in the channel or via email?
[14:55:55 CST(-0600)] <mlam> colinclark: https://github.com/mlam/infusion/tree/FLUID-3886
[14:56:19 CST(-0600)] <colinclark> that's cool
[14:56:31 CST(-0600)] <colinclark> thanks, mlam
[14:56:38 CST(-0600)] <mlam> np
[15:00:19 CST(-0600)] <colinclark> greggy, jessm: Our Fluid Google Summer of Code projects have shaped up nicely: http://wiki.fluidproject.org/display/fluid/Google+Summer+of+Code+with+the+Fluid+Project
[15:00:32 CST(-0600)] <colinclark> greggy: What else do you need from us to get these off to Google?
[15:00:46 CST(-0600)] <jessm> colinclark: shiny things! i want to do that this summer
[15:00:51 CST(-0600)] <colinclark> me too!
[15:00:53 CST(-0600)] <colinclark> I'm so jealous
[15:00:58 CST(-0600)] <colinclark> these projects are awesome
[15:01:09 CST(-0600)] <colinclark> I mean, who doesn't want to make an accessible image editing app using HTML5?
[15:01:18 CST(-0600)] <colinclark> Or make personalizable themes for MediaWiki and Drupal?
[15:02:51 CST(-0600)] <jessm> greggy: do you need them somewhere other than where they are?
[15:03:21 CST(-0600)] <greggy> colinclark: create a fluid section below the ATuroe section, and copy the extire pages and attachement over to wiki.atutor.ca
[15:03:35 CST(-0600)] <greggy> ...ATutor
[15:03:42 CST(-0600)] <colinclark> greggy: I couldn't figure out how to create an account on your wiki
[15:03:54 CST(-0600)] <colinclark> I could log in, but of course I don't have an account
[15:03:57 CST(-0600)] <colinclark> Is it a private wiki?
[15:04:34 CST(-0600)] <greggy> colinclark: hmm, let me see
[15:08:13 CST(-0600)] <greggy> colinclark: http://wiki.atutor.ca/signup.action
[15:08:30 CST(-0600)] <colinclark> where'd you discover that? (smile)
[15:31:45 CST(-0600)] <jessm> anastasiac: in my heart of hearts i believe that those very long bug parade emails don't have to be done the way we do them – i believe there must be a better way
[15:32:16 CST(-0600)] <anastasiac> yes, we should talk to Justin_o about ways to improve that
[15:32:21 CST(-0600)] <jessm> anastasiac: e.g. http://issues.fluidproject.org/sr/jira.issueviews:searchrequest-rss/temp/SearchRequest.xml?jqlQuery=project+%3D+FLUID+AND+fixVersion+%3D+%221.4%22+AND+resolution+%3D+Unresolved+AND+priority+%3D+Blocker+ORDER+BY+key+DESC&amp;tempMax=1000
[15:32:42 CST(-0600)] <colinclark> jessm: That's a good heart you've got
[15:32:49 CST(-0600)] <colinclark> those emails are so onerous to prepare
[15:32:49 CST(-0600)] <anastasiac> jessm, there was work on a "bug parade component" a while back - maybe time to ressurect it
[15:32:50 CST(-0600)] <jessm> i bet we can configure that RSS feed
[15:32:55 CST(-0600)] <colinclark> having served once or twice as proxy king
[15:33:25 CST(-0600)] <jessm> anastasiac: i'm all about making apps do the work for us – i won't settle on building our own until i know jira can't do it
[15:33:39 CST(-0600)] <anastasiac> good point
[15:34:09 CST(-0600)] <jessm> anastasiac: i bet i could even do it (tongue) – pride commeth...
[15:34:41 CST(-0600)] <anastasiac> (smile)
[15:34:41 CST(-0600)] <jessm> anastasiac: do an RSS feed of critical and blocker bugs that shows jira #s and level of completion – it's JIRAs job
[15:35:25 CST(-0600)] <jessm> anastasiac: also, i tweet the release news to @FluidProject – we're huge on Twitter (wink)
[15:40:04 CST(-0600)] <jessm> blimey! http://confluence.atlassian.com/display/DOC/Using+the+RSS+Feed+Builder
[15:43:05 CST(-0600)] <jessm> hrm, maybe not