fluid-work IRC Logs-2010-02-23

[17:15:31 EST(-0500)] <jessm> colinclark: sure
[17:15:40 EST(-0500)] <colinclark> There is another bug implicit in Sveto's email to the list today...
[17:16:08 EST(-0500)] <colinclark> As an aside, I'm getting a bit frustrated by patches that include fixes for multiple issues in one. They make it really hard to review and assess the fix, since there will be side effects
[17:16:23 EST(-0500)] <colinclark> Anyway, I don't actually know if someone's encountered this...
[17:16:30 EST(-0500)] <colinclark> and I don't think Sveto actually filed a bug for it
[17:16:42 EST(-0500)] <colinclark> But it appears that we may implicitly have a 25 artifact limit for a My Collection
[17:17:01 EST(-0500)] <jessm> colinclark: seems so from Sveto's email
[17:17:01 EST(-0500)] <colinclark> Meaning, if users have collected more than 25 artifacts, they'll only see 25 of them
[17:17:08 EST(-0500)] <colinclark> Probably the first 25, but it's ambiguous
[17:17:29 EST(-0500)] <colinclark> We could take a fragment of Sveto's patch that fixes it...
[17:17:30 EST(-0500)] <colinclark> b
[17:17:35 EST(-0500)] <colinclark> but it will require additional testing
[17:17:36 EST(-0500)] <colinclark> or we could leave it
[17:17:39 EST(-0500)] <colinclark> any thoughts?
[17:17:45 EST(-0500)] <colinclark> It appears trivial to implement and to test
[17:17:53 EST(-0500)] <jessm> colinclark: if it's trivial....
[17:18:21 EST(-0500)] <colinclark> i'll take a look and see what can be done
[17:18:25 EST(-0500)] <colinclark> Step 1, file the bug
[17:18:30 EST(-0500)] <colinclark> Step 2, implement the change
[17:18:45 EST(-0500)] <colinclark> Step 3, collect a whole ton of artifacts and see what happens
[17:18:48 EST(-0500)] <colinclark> thanks, jessm
[17:18:58 EST(-0500)] <jessm> colinclark: i'm happy to collect
[17:22:03 EST(-0500)] <colinclark> k
[17:25:54 EST(-0500)] <colinclark> jessm: super big favour?
[17:26:01 EST(-0500)] <jessm> colinclark: yep
[17:26:08 EST(-0500)] <colinclark> can you collect 26 items and verify that this is indeed a bug?
[17:26:14 EST(-0500)] <jessm> yes
[17:26:17 EST(-0500)] <colinclark> thanks
[17:26:20 EST(-0500)] <jessm> did you rebuild?
[17:26:24 EST(-0500)] <jessm> or did you not have to?
[17:26:37 EST(-0500)] <jessm> colinclark: ^
[17:30:27 EST(-0500)] <colinclark> jessm: jameswy rebuilt recently
[17:30:31 EST(-0500)] <colinclark> but the bug should just be in there
[17:38:31 EST(-0500)] * anastasiac (~team@142.150.154.193) has left #fluid-work
[17:40:24 EST(-0500)] <jessm> colinclark: only collects 25
[17:40:39 EST(-0500)] <jessm> colinclark: and only shows first 25
[17:41:36 EST(-0500)] <colinclark> jessm: thanks
[17:43:16 EST(-0500)] * clown (~clown@142.150.154.101) has left #fluid-work
[02:57:48 EST(-0500)] * denbuzze (~anonymous@ginger.caret.cam.ac.uk) has joined #fluid-work
[03:09:50 EST(-0500)] * christianv (~anonymous@ginger.caret.cam.ac.uk) has joined #fluid-work
[07:40:41 EST(-0500)] * boyan (~boyan@62.44.108.2) has joined #fluid-work
[08:11:49 EST(-0500)] * anastasiac (~team@142.150.154.193) has joined #fluid-work
[08:54:47 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[09:01:56 EST(-0500)] * jessm (~Jess@c-71-232-3-151.hsd1.ma.comcast.net) has joined #fluid-work
[09:17:57 EST(-0500)] <jessm> justin_o: yura: how's it going?
[09:18:03 EST(-0500)] <jessm> which issues are you tackling?
[09:19:54 EST(-0500)] <justin_o> jessm: hello.. I was working on 424 but am waiting to hear back on some things from the list
[09:20:16 EST(-0500)] <justin_o> jessm: yura just stepped out for coffee he is working on 351 and i might help him with that a bit
[09:20:41 EST(-0500)] <jessm> justin_o: thanks – when yura gets back let's check in on progress
[09:21:11 EST(-0500)] * jameswy (~jameswy@142.150.154.196) has joined #fluid-work
[09:21:14 EST(-0500)] <jessm> justin_o: what are you waiting to hear back about on 424?
[09:21:48 EST(-0500)] <justin_o> jessm: the appropriate use of alt text
[09:22:43 EST(-0500)] <jessm> justin_o: am i missing your thread on the list? I don't see an email about alt text
[09:23:42 EST(-0500)] <jameswy> jessm: "FE 0.3 bug(s): Fluid Engage an exhibition, home QA test plan" is the title of the thread on alt text.
[09:25:30 EST(-0500)] <jessm> jameswy: are you waiting for Everett to reply to Tona?
[09:27:17 EST(-0500)] <jessm> yikes, justin_o, that was meant for you ^
[09:27:52 EST(-0500)] <jessm> justin_o: i'm wondering what we're waiting for, since we don't have descriptive text as i understand it
[09:29:20 EST(-0500)] * athena (~athena@adsl-99-90-243-15.dsl.wlfrct.sbcglobal.net) has joined #fluid-work
[09:36:22 EST(-0500)] <justin_o> jessm: yes... waiting on what everett's response to tona will be
[09:37:17 EST(-0500)] <jessm> justin_o: so, what are the possibilities w/ a response? We don't have descriptive text, right? We only have artifact titles
[09:37:37 EST(-0500)] <yura> jessm: justin_o did you want to chech in on our progress?
[09:37:44 EST(-0500)] <jameswy> jessm: possibilities include of alt text include: "artifact name", "image of artifact name", and "".
[09:38:07 EST(-0500)] <justin_o> jessm: i suppose we could do image title for the artifact page, and maybe something like Sample artifact: Title on the exhibition about page
[09:39:57 EST(-0500)] <jessm> justin_o: how does the empty alt affect the feedback we got from Everett already?
[09:40:07 EST(-0500)] <jessm> i'm not sure how i see how it combats redundancy
[09:41:11 EST(-0500)] <jessm> yura: yes, what's the status of 351?
[09:41:54 EST(-0500)] <justin_o> jessm: having alt="" should tell the screen reader to ignore it...
[09:42:30 EST(-0500)] <justin_o> i should try this though to see if safari on the iPhone supports this
[09:42:39 EST(-0500)] <jessm> justin_o: yes
[09:42:56 EST(-0500)] <jessm> justin_o: and perhaps do some tests so that when/if we hear from Everett we're ready to go
[09:44:59 EST(-0500)] <jameswy> jessm: Jorge made us a snazzy new McCord mobile application icon. Do we want to replace the file of the current FE one?
[09:48:17 EST(-0500)] <justin_o> jessm: sure, can do
[09:48:44 EST(-0500)] <jessm> yura: go ahead and tell us about your progress in here
[09:49:04 EST(-0500)] <jessm> jameswy: we certainly can
[09:51:25 EST(-0500)] <jameswy> jessm: done. reopened 404.
[09:51:30 EST(-0500)] <jameswy> And attached.
[09:51:49 EST(-0500)] <jessm> justin_o: can you poke yura to update in the channel?
[09:52:17 EST(-0500)] <justin_o> jessm: sorry he just ran off to a phone call... i'll poke him when he gets back though
[09:52:36 EST(-0500)] <jessm> justin_o: k, thanks
[09:52:40 EST(-0500)] <jessm> jameswy: roger that
[09:53:45 EST(-0500)] * colinclark (~colin@bas2-toronto09-1176406027.dsl.bell.ca) has joined #fluid-work
[09:54:09 EST(-0500)] <yura> hi jessm, sorry, yes, i submitted a patch yesterday and Colin took a look at it and gave me some feedback, it's very close, just 2 issues left: 1 - add spinner onto the home page , 2 - investigate why it spins for a short period of time only
[09:54:35 EST(-0500)] <jessm> yura: great, so you're on track for a quick fix in the next hour or so, eh?
[09:56:22 EST(-0500)] * EricDalquist (~dalquist@2607:f388:e:0:221:9bff:fe37:e768) has joined #fluid-work
[09:57:27 EST(-0500)] <yura> jessm: I hope so
[09:57:31 EST(-0500)] <jameswy> jessm: also, related to home screen icons, I filed ENGAGE-438--bug where the default name of the application is "Home"
[09:57:33 EST(-0500)] <yura> it looks that way
[09:57:55 EST(-0500)] <jessm> justin_o: when you're finished with testing on 424, can you do a quick fix on the build icon for 404?
[09:58:26 EST(-0500)] <justin_o> jessm: actually i am working on that at the moment... should have it in shortly
[09:58:50 EST(-0500)] <jessm> justin_o: is it also a similar place where 438 gets fixed?
[09:59:02 EST(-0500)] <jessm> jameswy: weird that it says home – mine still says fluid nightly
[09:59:49 EST(-0500)] <jameswy> jessm: It's only on the first add. The name of the application never updates, although the icon does.
[09:59:59 EST(-0500)] <justin_o> jessm that would be a change to the markup and/or code to get 438 working
[10:00:10 EST(-0500)] <colinclark> yura: You seem pretty optimistic... have you found any insights into your spinner going away so quickly?
[10:00:11 EST(-0500)] <justin_o> not sure it is necessary for 0.3b
[10:00:22 EST(-0500)] <justin_o> jessm: ^
[10:00:30 EST(-0500)] <jessm> justin_o: agreed, if it's not a quick fix, let's leave it
[10:00:39 EST(-0500)] <jessm> this release is getting mucky
[10:00:41 EST(-0500)] <justin_o> jessm: okay
[10:00:57 EST(-0500)] <jessm> 424, 404, and 351
[10:01:02 EST(-0500)] <jessm> justin_o: yura: ^
[10:01:07 EST(-0500)] <justin_o> okay
[10:02:01 EST(-0500)] * clown (~clown@142.150.154.101) has joined #fluid-work
[10:03:04 EST(-0500)] <justin_o> jameswy, jessm: can you test the home screen icon and close off 404 if it works
[10:03:28 EST(-0500)] <justin_o> justin_o: forgot to rebuild.. will do it now
[10:03:45 EST(-0500)] <jameswy> Hahaha.
[10:03:50 EST(-0500)] <jameswy> He just talked to himself,
[10:04:12 EST(-0500)] <justin_o> jameswy: sorry... just wanted to make sure i remembered
[10:05:14 EST(-0500)] <jameswy> justin_o: Sure, sure,
[10:11:10 EST(-0500)] * boyan (~boyan@62.44.108.2) has left #fluid-work
[10:14:50 EST(-0500)] * boyan (~boyan@62.44.108.2) has joined #fluid-work
[10:21:29 EST(-0500)] <jessm> jameswy: 438 is customizable by Hugues or whomever adds it to the home screen
[10:21:34 EST(-0500)] <jessm> jameswy: maybe tell hugues?
[10:25:24 EST(-0500)] <jessm> jameswy: the icon looks great
[10:50:27 EST(-0500)] <yura> colinclark: it seems that the styling works fine , i m inclined to say that the window.location changes really fast
[10:50:37 EST(-0500)] <colinclark> yack
[10:50:40 EST(-0500)] <yura> colinclark: and I addressed your comment on the jira too
[10:50:46 EST(-0500)] <colinclark> yura: meaning, this approach just won't really work?
[10:51:14 EST(-0500)] <yura> well i m still trying to see if there are ways to do it
[10:54:51 EST(-0500)] <colinclark> ok
[10:59:33 EST(-0500)] <colinclark> yura: Let's check in in about half an hour
[11:00:22 EST(-0500)] <jameswy> jessm, justin_o: 404 looks good. Issue closed.
[11:00:42 EST(-0500)] <colinclark> to see what we should do about 351
[11:01:50 EST(-0500)] <jameswy> jessm: re: 438 - Yep, it's customizable by the user (at add time only), though they do have to edit the field when really it should be there by default. Not necessary for 0.3 like justin_o said, but I've written it up anyways to keep an eye on for the future.
[11:02:48 EST(-0500)] <jessm> jameswy: yes, and "at add time" will be an Hugues thing – perhaps you can just let him know about this in advance
[11:03:14 EST(-0500)] <jameswy> jessm: roger that.
[11:04:12 EST(-0500)] <jessm> justin_o: what's the approach going to be for 424 wrt Everett's latest email?
[11:06:19 EST(-0500)] <jessm> jameswy: from everett's latest email about code entry there are a number of a11y issues to file, you have them?
[11:09:40 EST(-0500)] <jameswy> jessm: I haven't filed them yet
[11:16:08 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[11:24:00 EST(-0500)] <yura> colinclark: so justin_o and I looked at it more closely and it is indeed the change of the window.locatin that happens that fast, I tried putting it on inital load as well, but it seems as it's too late for the image to load in time there
[11:24:19 EST(-0500)] <colinclark> yep, i figured that would be the outcome, yura
[11:24:52 EST(-0500)] * yura (~Fluid@142.150.154.164) has left #fluid-work
[11:25:33 EST(-0500)] <jameswy> jessm: It looks to me like Everett's last email only had one issue to file, which I've filed as ENGAGE-440
[11:30:22 EST(-0500)] <justin_o> colinclark, jessm: okay... so i talked with jameswy about the image on the exhibition about page and he told me that that wasn't an artifact often, so the alt text on that should just be the title of the exhibition as well for now... so i have changed all of the museum related images to be the title... either the title of the artifact or the exhibition
[11:32:26 EST(-0500)] <colinclark> let's stand up, then chat a bit about it
[11:41:14 EST(-0500)] * boyan (~boyan@62.44.108.2) has left #fluid-work
[11:46:04 EST(-0500)] * yura (~Fluid@142.150.154.164) has joined #fluid-work
[11:46:05 EST(-0500)] <colinclark> justin_o, yura, jameswy, jessm: let's meet in breeze to talk through our freeze
[11:46:14 EST(-0500)] <jessm> k
[11:46:16 EST(-0500)] <justin_o> colinclark: okay
[11:46:16 EST(-0500)] <colinclark> yura: let's meet in breeze to talk through the freeze
[11:46:35 EST(-0500)] <yura> colinclark: sure
[12:08:14 EST(-0500)] <colinclark> justin_o: I'm reviewing 424 now
[12:09:10 EST(-0500)] <colinclark> justin_o: Can you resolve it when you get a chance?
[12:10:26 EST(-0500)] <justin_o> colinclark: working on that now
[12:10:52 EST(-0500)] <colinclark> thanks so much
[12:11:29 EST(-0500)] <justin_o> colinclark: done
[12:11:36 EST(-0500)] <colinclark> justin_o: Is the only way to set alt text on an image to use an attr decorator?
[12:13:23 EST(-0500)] <justin_o> seems like it... i had tried to use link text from the uiBound but that just added it as text in the markup
[12:13:31 EST(-0500)] <justin_o> so you would get the title repeated twice on the page
[12:14:01 EST(-0500)] <yura> colinclark: should I rebuild then and start testing?
[12:14:30 EST(-0500)] <colinclark> yura: lemme finish reviewing justin_o's patch before I call a freeze
[12:14:42 EST(-0500)] <yura> thanks
[12:14:46 EST(-0500)] <justin_o> sorry.. not uiBound... uiLink
[12:14:49 EST(-0500)] <justin_o> colinclark: ^
[12:15:01 EST(-0500)] <colinclark> k
[12:18:24 EST(-0500)] * EverettZ (~chatzilla@bas4-toronto06-1242458424.dsl.bell.ca) has joined #fluid-work
[12:19:03 EST(-0500)] <EverettZ> colinclark: Hey, I've asked before, but just for an update, is Fluid currently implementing jQuery UI autocomplete anywhere?
[12:19:16 EST(-0500)] <colinclark> EverettZ: No, not yet
[12:19:30 EST(-0500)] <colinclark> EverettZ: I've been helping where I can with a11y testing for autocomplete, but haven't been as involved as I'd like
[12:19:30 EST(-0500)] <EverettZ> colinclark: thinking of working on an upstream patch to make autocomplete accessible in Drupal / whatever else is using it.
[12:19:38 EST(-0500)] <colinclark> EverettZ: Makes sense to me
[12:20:29 EST(-0500)] <EverettZ> colinclark: are there any jQuery UI components that Fluid uses that could use work upstream?
[12:20:55 EST(-0500)] <colinclark> EverettZ: Let me think about it. Juggling a few too many things to give you a real response at the moment.
[12:21:00 EST(-0500)] <colinclark> maybe justin_o has some thoughts
[12:21:05 EST(-0500)] <EverettZ> colinclark: sounds good
[12:21:55 EST(-0500)] <justin_o> colinclark, EverettZ: just trying to think which ones we use
[12:22:44 EST(-0500)] <justin_o> EverettZ: we do make use of the dialog, i think you had some comments about that one earlier...
[12:23:34 EST(-0500)] <EverettZ> justin_o: yes, unfortunately the comments are 'broke don't use' and 'can't be fixed'.
[12:23:43 EST(-0500)] <EverettZ> justin_o: perhaps that's a little extreme
[12:24:31 EST(-0500)] <justin_o> EverettZ: okay... also just checked.. it seems that we use from jquery ui, the dialog, accordion, and slider. All probably as part of infusion's UI Options component
[12:24:31 EST(-0500)] <colinclark> EverettZ: Maybe a little. But it does raise a major issue with the very concept of the ARIA application role
[12:24:45 EST(-0500)] <colinclark> EverettZ: Ah, slider!
[12:24:48 EST(-0500)] <EverettZ> justin_o: but it boils down to AT not respecting aria and / or not respecting the js/css techniques used to create modality
[12:25:04 EST(-0500)] <colinclark> EverettZ: There were a few patches Alison had created that we still haven't gotten upstream in jQuery UI for whatever reason
[12:25:41 EST(-0500)] <colinclark> justin_o: I've reviewed your ENGAGE-424 patch
[12:25:47 EST(-0500)] <colinclark> justin_o: I think I like it, with one caveat
[12:25:51 EST(-0500)] <EverettZ> justin_o: colinclark Ok, I'll take a look at slider and autocomplete.
[12:25:58 EST(-0500)] <colinclark> And, to be clear, I think we can probably live with it for now
[12:26:15 EST(-0500)] <justin_o> EverettZ: are you able to get patches off of jira?
[12:26:16 EST(-0500)] <colinclark> By setting the alt text of all images in a nav list to the title of the item, we do something that can be slightly misleading
[12:26:49 EST(-0500)] <justin_o> colinclark: yes.. i think something more ideal would have been to expect alt text in the model and then default to the title when not present
[12:26:57 EST(-0500)] <EverettZ> justin_o: likely not, but I'm going to start by talking to Alison about it, so I expect she can send me the patches
[12:26:59 EST(-0500)] <colinclark> take a look at this artifact, justin_o: http://localhost:8080/artifacts/view.html?db=mccord&amp;accessNumber=M13321&amp;lang=en
[12:27:11 EST(-0500)] <colinclark> in the Media section of the cabinet
[12:27:16 EST(-0500)] <justin_o> colinclark: using the default image option would be a problem
[12:27:37 EST(-0500)] <colinclark> ok, we can live with this
[12:27:42 EST(-0500)] <colinclark> i just wanted to be sure that you'd also considered this issue
[12:28:36 EST(-0500)] <EverettZ> colinclark: justin_o I was going to ask if alt text is part of the data that is expected to be stored for images of artifacts. I.e. understanding that the data might not be present, is there a datastore where it could be placed if available?
[12:29:09 EST(-0500)] <colinclark> EverettZ: It's a big question to answer.
[12:29:17 EST(-0500)] <colinclark> EverettZ: Gimme a couple minutes and I can answer
[12:29:22 EST(-0500)] <colinclark> justin_o: I've closed ENGAGE-424
[12:29:33 EST(-0500)] <EverettZ> colinclark: Well, I suppose I don't so much need the answer
[12:29:38 EST(-0500)] <colinclark> jameswy, justin_o, yura: Is there anything else that needs to be looked at before freeze?
[12:30:00 EST(-0500)] <EverettZ> colinclark: as much as the answer is that if it isn't part of the current data model that it needs to be added whenever it is the right time for it to be added.
[12:30:22 EST(-0500)] <justin_o> colinclark: i don't think so
[12:30:46 EST(-0500)] <colinclark> EverettZ: The thing about Engage's approach to data models is that it's very flexible--fundamentally we allow museums to choose the schema and structure of their collection information
[12:31:04 EST(-0500)] <colinclark> EverettZ: So the key challenge is how to represent alt text when it is available in the museum's data, and where to source it if it isn't
[12:31:25 EST(-0500)] <justin_o> colinclark: can we rebuild the daily now and start testing?
[12:31:40 EST(-0500)] <colinclark> EverettZ: Ultimately, it's a kind of model transformation. Where alt text is present use it. In other cases, recognize that it can be derived from some other field in the model, specific to the museum.
[12:31:43 EST(-0500)] <colinclark> justin_o: Yes, go for it.
[12:31:51 EST(-0500)] <colinclark> I declare that trunks are now officially frozen again.
[12:31:52 EST(-0500)] <EverettZ> colinclark: so, in laymans terms, you create a bridge between the museum data model and what is required for engage?
[12:32:12 EST(-0500)] <colinclark> EverettZ: Or you might think of it as map, yes.
[12:32:30 EST(-0500)] <colinclark> EverettZ: As part of using Engage, museums describe the layout of their data to us
[12:33:53 EST(-0500)] <EverettZ> colinclark: makes sense, and makes for a flexible product. I don't really see a design problem here as far as a11y. The data is either present or not and is used or not. Some engage implementations will have greater semantic a11y as a result of better data being provided by the museum.
[12:34:02 EST(-0500)] <colinclark> EverettZ: That's the goal, yes
[12:34:31 EST(-0500)] <colinclark> EverettZ: It then becomes interesting for us to devise ways to close the a11y gap where that data is missing.
[12:34:43 EST(-0500)] <yura> colinclark: justin_o it
[12:34:44 EST(-0500)] <EverettZ> colinclark: I bet
[12:34:49 EST(-0500)] <yura> s now rebuilt
[12:34:56 EST(-0500)] <EverettZ> colinclark: thanks for explaining. I'm off to work on jQuery.
[12:34:58 EST(-0500)] <colinclark> jameswy: You're ready to go
[12:35:03 EST(-0500)] <colinclark> EverettZ: Good luck. Let us know if you need any help
[12:35:16 EST(-0500)] <EverettZ> colinclark: will do
[12:35:21 EST(-0500)] <jameswy> colinclark: roger that.
[12:35:21 EST(-0500)] <colinclark> justin_o: I'm assuming you'll now help jameswy coordinate the QA testing
[12:35:41 EST(-0500)] <colinclark> yura: Can you have a chat with jamon about the performance of our fluidengage.org instance?
[12:35:46 EST(-0500)] <yura> yes
[12:35:52 EST(-0500)] <colinclark> I'm gonna head into the office now, so I'll see you all shortly
[12:35:53 EST(-0500)] <jameswy> colinclark, justin_o: already sent out the email. But it just occurred to me after I sent it that I think we're the only ones in the core community with 3GSes.
[12:35:56 EST(-0500)] <justin_o> colinclark: yep... but i think it may be sufficiently small for just a few of us to do it
[12:36:03 EST(-0500)] <jameswy> That too
[12:36:08 EST(-0500)] <colinclark> cool
[12:36:18 EST(-0500)] <colinclark> justin_o has the keys to the 3GSes, so let's rock it
[12:36:42 EST(-0500)] <justin_o> colinclark: got them out already
[12:37:52 EST(-0500)] <colinclark>
[12:58:58 EST(-0500)] * joan2 (~jgarci@159.Red-88-21-180.staticIP.rima-tde.net) has joined #fluid-work
[12:59:15 EST(-0500)] * joan2 (~jgarci@159.Red-88-21-180.staticIP.rima-tde.net) has left #fluid-work
[13:19:21 EST(-0500)] * anastasiac (~team@142.150.154.193) has joined #fluid-work
[13:21:23 EST(-0500)] * denbuzze (~anonymous@ginger.caret.cam.ac.uk) has joined #fluid-work
[13:38:35 EST(-0500)] * colinclark (~colin@142.150.154.101) has joined #fluid-work
[13:56:22 EST(-0500)] * yura1 (~yura@142.150.154.101) has joined #fluid-work
[14:09:51 EST(-0500)] * justin_o (~jmo@142.150.154.101) has joined #fluid-work
[14:20:10 EST(-0500)] <justin_o> jameswy: i have finsihed a round of testing. I didn't find anything new that would have been caused by any recent changes. Did find an issue with exhbition home page though and filed it here http://issues.fluidproject.org/browse/ENGAGE-441
[14:20:31 EST(-0500)] <justin_o> i'm going to do a quick run through of the app using voice over in french and see how that goes
[14:21:12 EST(-0500)] <jameswy> justin_o: I've similarly finished a round of the abridged VO testing and found no issues, and was able to replicate issue 441
[14:22:30 EST(-0500)] <jameswy> jessm, colinclark: justin_o and I have completed a run each of the abridge VO testing (testing against 424), and it looks good.
[14:23:00 EST(-0500)] <jameswy> abridged*
[14:26:04 EST(-0500)] <jessm> jameswy: good stuff
[14:26:30 EST(-0500)] <yura> justin_o: , janes I will test the object code entry one more time right now in both languages
[14:27:03 EST(-0500)] <justin_o> yura: thanks... i've tested it once, but i'm a bit biased
[14:32:55 EST(-0500)] <yura> jessm: justin_o, there are some issues with Hugues language encoding, should I let him now just in case before tomorrow?
[14:33:15 EST(-0500)] <jessm> yura:yes please, he's getting us a fresh feed tomorrow
[14:34:41 EST(-0500)] <yura> jessm: sure I will email him right now, is there anything else I should ask him , data related ?
[14:35:15 EST(-0500)] <jessm> yura: justin_o: you guys tell me – do we have any more language issues? what aoubt the media badge?
[14:35:31 EST(-0500)] <jessm> yura: justin_o: nevermind we're punting that
[14:35:56 EST(-0500)] <justin_o> jessm: i'm compiling a list at the moment... i'll file jiras for them so we keep track of them
[14:36:37 EST(-0500)] <yura> jessm: justin_o so just the data encoding then
[14:37:21 EST(-0500)] <justin_o> yura: i think so
[14:38:00 EST(-0500)] <colinclark> jessm: You were mentioning a few resolved, but not closed, blockers...
[14:38:13 EST(-0500)] <jessm> 310, 309, 387, 345, 364, 344, 356
[14:38:20 EST(-0500)] <jessm> colinclark: ^ those are they
[14:40:33 EST(-0500)] <colinclark> jessm: These all need to be reviewed before closing, which I think we can do immediately after QA is finished and the release is out.
[14:40:43 EST(-0500)] <jessm> colinclark: fantastic
[14:44:11 EST(-0500)] <jessm> yura: i'm not deeply into the data feed to weigh in – but justin_o should be able to confer with you on this so you can communicate with Hugues
[14:45:05 EST(-0500)] <yura> jessm: thanks. so justin_o do you want me to wait for those strings or should I email Hugues about the encoding for now?
[14:46:26 EST(-0500)] <justin_o> yura: I think you should just e-mail Hugues about the data feed.. the language issues will have to wait till after we unfreeze
[14:47:03 EST(-0500)] <yura> jessm: justin_o: ok ill compose one now then
[14:48:53 EST(-0500)] <jessm> yura: cc the list if you will
[14:49:02 EST(-0500)] <yura> jessm: will do
[14:51:52 EST(-0500)] <yura> jameswy: that issue is ENGAGE-443, jessm you might want to take a look too
[14:53:26 EST(-0500)] <jameswy> yura: thanks.
[15:09:05 EST(-0500)] <justin_o> jessm: i've filed the localization issues here http://issues.fluidproject.org/browse/ENGAGE-444
[15:16:02 EST(-0500)] <yura> jessm: justin_o I email Hugues about the encoding issues and cced the list
[15:16:30 EST(-0500)] <justin_o> yura: thanks
[15:26:27 EST(-0500)] <yura> jessm: justin_o : I just finished object code entry right now in both languages
[15:26:52 EST(-0500)] <justin_o> yura: is it working okay?
[15:27:36 EST(-0500)] <yura> justin_o: yes, both in english and french voice over
[15:29:53 EST(-0500)] <Bosmon> colinclark and all: Over the weekend I found this extremely interesting blog post by John Resig: http://ejohn.org/blog/deep-tracing-of-internet-explorer/
[15:30:20 EST(-0500)] <Bosmon> They also have upcoming support for Firefox, but all the same, to strike at the heart of the territory of dreadful performance in IE6 is extremely exciting
[15:30:32 EST(-0500)] <Bosmon> not least, that it looks to be a very well put together tool in any case
[15:34:22 EST(-0500)] <colinclark> Bosmon: Thanks for sending this along
[15:34:28 EST(-0500)] <colinclark> I had read this post on the subway one day
[15:34:33 EST(-0500)] <Bosmon> ah, cool
[15:34:41 EST(-0500)] <colinclark> but since my RSS reader doesn't pre-cache images, I didn't quite realize how good it looked
[15:34:55 EST(-0500)] <Bosmon> I guess the urgency of figuring out where IE6 spends all its time is diminishing month on month
[15:35:02 EST(-0500)] <Bosmon> But all the same...
[15:35:03 EST(-0500)] <colinclark> it would be nice to have a tool like this for WebKit, too
[15:35:08 EST(-0500)] <colinclark> I mean, we have much better tools there
[15:35:08 EST(-0500)] <Bosmon> To be sure
[15:35:14 EST(-0500)] <colinclark> But the native profiling, etc, is pretty nice
[15:35:47 EST(-0500)] <colinclark> so Bosmon, things are looking pretty good with the release
[15:35:56 EST(-0500)] <colinclark> looks like we'll have "beta 1" out in a few hours
[15:36:16 EST(-0500)] <colinclark> and then it's up to us with "beta 2"
[15:37:26 EST(-0500)] <Bosmon> That's awesome
[16:09:38 EST(-0500)] <yura> also added http://issues.fluidproject.org/browse/ENGAGE-450
[16:23:26 EST(-0500)] <yura> jessm: jameswy, colinclark it seems like in chromeless you cant open any videos for the artifact
[16:23:47 EST(-0500)] <colinclark> yura: tell us more
[16:24:25 EST(-0500)] <justin_o> so it works from the browser directly... so i wonder if the wrong item is getting focus or something
[16:24:36 EST(-0500)] <colinclark> This is definitely a regression
[16:28:47 EST(-0500)] <jessm> yura: 450 to be clear is just added to 0.3 but not to parade
[16:29:20 EST(-0500)] <jessm> justin_o: yura: i'm going to suggest that we tag all new bugs we add with the 0.3 version tag – that make sense?
[16:29:44 EST(-0500)] <jessm> ok, all hands on deck for the blocker i guess
[16:31:20 EST(-0500)] <yura> jessm: we are tying to check if it's the older iphone os version that breaks it, colinclark and justin_o seem to be able to load it
[16:32:04 EST(-0500)] <justin_o> jessm: sure.. unless we don't think it is something we will get to for 0.3
[16:32:19 EST(-0500)] * yura1 (~yura@142.150.154.101) has joined #fluid-work
[16:32:22 EST(-0500)] <jessm> justin_o: then we tag it with 0.5 i'd assume
[16:32:32 EST(-0500)] <yura> jessm: makes sense
[16:32:36 EST(-0500)] <justin_o> jessm: yep.. that seems reasonabl
[16:32:56 EST(-0500)] <jessm> yura: "seem to be able to load it" – meaning video?
[16:35:18 EST(-0500)] * colinclark (~colin@142.150.154.101) has joined #fluid-work
[16:35:26 EST(-0500)] <yura> jessm: yes
[16:35:32 EST(-0500)] <colinclark> So I have a working theory, but no way to back it up at the moment
[16:35:56 EST(-0500)] <justin_o> colinclark, jessm, yura: It's going to take about 30 minutes to update the iPhone
[16:35:59 EST(-0500)] <colinclark> a quick check with a proxy suggests that Hugues is serving his MP4 videos with a content type of text/plain.
[16:36:12 EST(-0500)] <Bosmon> "oh dear"
[16:36:15 EST(-0500)] <colinclark> It may be that the latest Safari for iPhone is smart enough to handle this error, and older version are not
[16:41:22 EST(-0500)] * anastasiac (~team@142.150.154.193) has joined #fluid-work
[16:43:10 EST(-0500)] <justin_o> colinclark, jessm, yura: I tested the issue in the iPhone simulator
[16:43:15 EST(-0500)] <justin_o> and it seems to be the OS version
[16:43:23 EST(-0500)] <justin_o> if i put the simulator down to 3.0 it doesn't work
[16:44:19 EST(-0500)] <justin_o> it seems to work as of 3.1
[16:45:17 EST(-0500)] <colinclark> ok
[16:45:26 EST(-0500)] <colinclark> I'm willing to bet it's the content type issue
[16:45:42 EST(-0500)] <colinclark> We tried on yura's droid and it failed, saying that the media type wasn't supported
[16:45:53 EST(-0500)] <colinclark> yet MPEG-4 videos do appear to be supported
[16:46:00 EST(-0500)] <colinclark> I've emailed Hugues about it
[16:46:10 EST(-0500)] <justin_o> colinclark: thanks