fluid-work IRC Logs-2010-10-06

[09:35:43 CDT(-0500)] <mlam> jhung: can you attach the pencil icon from your demo to the jira?
[09:35:58 CDT(-0500)] <jhung> k
[09:36:19 CDT(-0500)] <mlam> thanks
[09:37:08 CDT(-0500)] <jhung> done
[09:37:18 CDT(-0500)] <jhung> ^mlam
[09:39:30 CDT(-0500)] <mlam> thanks
[09:39:56 CDT(-0500)] <mlam> jhung, jameswy: is this valid text for the inline edit tooltip?
[09:39:56 CDT(-0500)] <mlam> "Press Escape to cancel, Enter or Tab to save"
[09:40:21 CDT(-0500)] <jameswy> mlam: Is the text editable on the integrator's side?
[09:40:35 CDT(-0500)] <mlam> yes
[09:41:07 CDT(-0500)] <jameswy> mlam: I think a better default might be to say "when finished" instead of "to save".
[09:41:20 CDT(-0500)] <mlam> ok
[09:47:16 CDT(-0500)] <justin_o> colinclark, mlam: just wondering if the alt text on the button is going to recreate the problem we are drying to solve
[09:48:02 CDT(-0500)] <justin_o> meaning that the problem was that we were getting something like "brown fox button"... with the alt text we will get "Edit text brown fox button" i would assume...
[10:17:26 CDT(-0500)] <jhung> Question about NVDA: Is there a quick way to enable / disable NVDA without having to close and re-open the application each time?
[10:28:32 CDT(-0500)] <golam> jhung: let me check
[10:51:50 CDT(-0500)] <jhung> colinclark, justin_o: I'm going to run out for an errand. Chat when I'm back (around 1p / 1:30p?)
[10:58:12 CDT(-0500)] <justin_o> jhung_afk: we'll probably be out till the dev meeting at 2pm
[11:12:37 CDT(-0500)] <colinclark> Hey justin_o and mlam
[11:12:47 CDT(-0500)] <colinclark> Sorry it's been so crazy... you guys had a question about Inline Edit?
[11:12:56 CDT(-0500)] <justin_o> colinclark: yep... thanks
[11:13:00 CDT(-0500)] <justin_o> okay... question 1
[11:13:44 CDT(-0500)] <justin_o> do you think that adding the alt text on the image, with the full editable text in it, will bring us back to the original problem...
[11:14:24 CDT(-0500)] <justin_o> originally we had something like "brown fox button", now i would assume we would get something like "Edit text brown fox image button" or something
[11:15:31 CDT(-0500)] <colinclark> justin_o: I think the original confusion was that the text was the button
[11:15:39 CDT(-0500)] <colinclark> That it wasn't clear that the button would allow you to "edit" the text
[11:15:47 CDT(-0500)] <colinclark> Our hope was that this alt text made that explicit
[11:16:01 CDT(-0500)] <colinclark> I guess one big risk with it is that it won't scale
[11:16:31 CDT(-0500)] <colinclark> For, say, rich text Inline Edit, which is typically used for multi-paragraph text, that'll be awfully long alt text
[11:16:42 CDT(-0500)] <colinclark> So I'm afraid this solution isn't quite baked
[11:16:42 CDT(-0500)] <colinclark> Bu
[11:16:51 CDT(-0500)] <colinclark> But I think it might make the interaction a bit more specific
[11:18:26 CDT(-0500)] <justin_o> colinclark: okay... i guess we should get some feedback about how people like it and we should think about what to do for the richtext case, but i guess it should be good for now...
[11:18:31 CDT(-0500)] <justin_o> colinclark: question 2...
[11:18:42 CDT(-0500)] <colinclark> justin_o: To follow up on that first question and your point about feedback...
[11:19:02 CDT(-0500)] <colinclark> I had promised to send an email out describing the interaction issues with Inline Edit
[11:19:12 CDT(-0500)] <colinclark> James sent me some background information, but I got really busy
[11:19:19 CDT(-0500)] <colinclark> Particularly getting prepped for Jan's thing
[11:19:39 CDT(-0500)] <colinclark> I think we should probably summarize the various interaction issues, and the different variations we've put together, along with their strengths and weaknesses
[11:20:02 CDT(-0500)] <colinclark> It's perhaps something that James and I could collaborate on, because it'll probably help people to understand what we're trying better
[11:21:52 CDT(-0500)] <justin_o> that's a good idea
[11:22:35 CDT(-0500)] <justin_o> for question 2: so we set the alt text in the renderer function for the button, but if someone passes in their own in the template they will have to manage this themselves... i suppose this is okay and if so, does it make sense to have the function that handles the updating of the alt text be defined outside of the renderer function?
[11:25:37 CDT(-0500)] <justin_o> colinclark: ^
[11:25:56 CDT(-0500)] <colinclark> justin_o: Yeah, it probably does
[11:26:17 CDT(-0500)] <colinclark> mlam: And I sort of hovered over a few areas of the code where this could be placed, and picked one nearly at random
[11:26:35 CDT(-0500)] <colinclark> It might take a bit of thinking to know just where it's best to put this alt text updater listener
[11:26:43 CDT(-0500)] <colinclark> The good news is that since it is a listener, it can go pretty much anywhere
[11:26:47 CDT(-0500)] <colinclark> "in theory"
[11:28:59 CDT(-0500)] <justin_o> colinclark: okay.. thanks
[11:29:18 CDT(-0500)] <colinclark> Let me know where you guys ultimately decide to put it
[11:29:26 CDT(-0500)] <colinclark> I had this feeling like there wasn't a place I was fully satisfied with
[11:29:50 CDT(-0500)] <colinclark> heidi_: So what did you end up with, in terms of your UI Options puzzle earlier today?
[11:29:57 CDT(-0500)] <colinclark> Did you get it working?
[11:29:58 CDT(-0500)] <justin_o> colinclark: I think we'll just leave it since you guys have gone over it already...
[11:30:34 CDT(-0500)] <heidi_> hey colinclark ... getting there. figuring out if i can get an event when the contents of an iframe are loaded
[11:30:51 CDT(-0500)] <heidi_> frame.ready will only happen when <iframe> happens, not its contents
[11:31:24 CDT(-0500)] <colinclark> heidi_: Yeah. I imagine there is no suitable event, but if you find one it'll be awesome
[11:31:29 CDT(-0500)] <heidi_> .load doesn't seem to work
[11:32:01 CDT(-0500)] <heidi_> yeah it might be a dead end road here... but i'm getting to read lots of documentation and understand more stuff which is generally a good thing
[11:33:00 CDT(-0500)] <heidi_> i also learned how to make an infite loop
[11:33:13 CDT(-0500)]

[11:33:17 CDT(-0500)] <heidi_> duhh
[11:35:33 CDT(-0500)] <colinclark>
[13:03:32 CDT(-0500)] <jhung> where is the Dev meeting? Skype or Breeze?
[13:51:32 CDT(-0500)] <Justin_o_> jamon: I think we need to update our set of tested browsers in testswarm... noticing that it is a bit out of date
[13:57:36 CDT(-0500)] <jamon> Justin_o_: testswarm itself is out of date too
[13:59:08 CDT(-0500)] <Justin_o_> jamon: yes... that's also true.. but i've heard that there were problems with it not respecting the difference between a browser run in one os versus another. i.e. FF3 on win xp and FF3 on mac os would be considered the same browser. Not sure if this has been corrected or not yet
[14:02:09 CDT(-0500)] <jamon> Justin_o_: want to work on it tomorrow with me?
[14:02:24 CDT(-0500)] <Justin_o_> jamon: sure... please ping me when you are free
[14:04:11 CDT(-0500)] <jamon> Justin_o_: any time after coffee tomorrow works
[14:04:24 CDT(-0500)] <Justin_o_> jamon: okay... sounds good
[14:09:32 CDT(-0500)] <jhung> justin_o, colinclark: you guys have time to chat about Tabs demo?
[14:09:47 CDT(-0500)] <justin_o> jhung: colinclark is just on his way to grab lunch
[14:10:24 CDT(-0500)] <justin_o> jhung: he should be back in about 20 minutes
[14:10:31 CDT(-0500)] <jhung> justin_o: colinclark eats? I thought he sustains himself through the nutrients drifting in the office air.
[14:10:53 CDT(-0500)] <jhung> justin_o: ok
[14:10:58 CDT(-0500)] <justin_o> jhung:
[14:38:24 CDT(-0500)] <colinclark> jhung, Justin_o, anastasiac: 1 minute to grab some water, then we'll chat about a11y demos?
[14:38:33 CDT(-0500)] <anastasiac> sure
[14:38:36 CDT(-0500)] <jhung> k
[14:44:30 CDT(-0500)] <colinclark> Justin_o: Are you going to join us, too?