fluid-work IRC Logs-2010-11-19

Owned by Fluid IRC Log Bot
Last updated: Nov 19, 2010Version comment
15 min read

[08:26:31 CST(-0600)] <heidi_> justin_o ill add those builder patches - anything i can help with after that?
[08:29:01 CST(-0600)] <Justin_o> heidi_: not exactly sure at this moment, I have to go through all the jiras again and make sure bug parade is up-to-date and I think we may have to do some reorganizing for the release.. hopefully not much though
[08:29:27 CST(-0600)] <heidi_> okee ping me when you find anything i can help with !
[08:30:15 CST(-0600)] <Justin_o> heidi_: thanks
[08:30:24 CST(-0600)] <heidi_> btw, do you guys have snow?
[08:30:44 CST(-0600)] <Justin_o> heidi_: I haven't seen any today... do you have much?
[08:32:05 CST(-0600)] <heidi_> drove home in a crazy snow storm last night! and yeah we have some on the ground this morning, not that much but it's sticking
[08:33:23 CST(-0600)] <yura_> hey Justin_o
[08:35:48 CST(-0600)] <Justin_o> yura_: hello
[08:35:59 CST(-0600)] <yura_> I was wondering if we can add another JIRA to bug parade
[08:36:06 CST(-0600)] <Justin_o> heidi_: wow... starting to feel like christmas
[08:36:15 CST(-0600)] <Justin_o> yura_: which one is that
[08:36:27 CST(-0600)] <yura_> http://issues.fluidproject.org/browse/FLUID-3857
[08:36:44 CST(-0600)] <yura_> it has a patch and tests and bosmon looked at it last night
[08:38:46 CST(-0600)] <Justin_o> yura_: what makes this jira important
[08:40:25 CST(-0600)] <yura_> Justin_o: well the implementation of remove_if precedes the existence of such utilities as isArrayable, fluid.each and so on. So it is limited only to operating on arrays and not both arrays and objects. Currently cspace has a bug because of the assumption that it can handle both arrays and objects.
[08:45:41 CST(-0600)] <Justin_o> i guess i'm not sure it's a blocker... what could go wrong by adding it in?
[08:45:56 CST(-0600)] <Justin_o> what is the risk?
[08:46:00 CST(-0600)] <Justin_o> yura_: ^
[08:48:01 CST(-0600)] <yura_> well Justin_o, the only 2 places the function is used in the framework are withing the reorderer: in GeometricManager :439 and ModuleLayout: 203
[08:48:19 CST(-0600)] <yura_> it doesnt change the functionality of operating over arrays
[08:48:23 CST(-0600)] <yura_> just adds one for objects
[08:49:40 CST(-0600)] <Justin_o> yura_: I think you said there is a patch, did you run the reorderer unit tests against it?
[08:50:04 CST(-0600)] <yura_> Justin_o: give me one second ill do it
[08:50:12 CST(-0600)] <Justin_o> okay
[08:53:26 CST(-0600)] <yura_> Justin_o: all reorderer tests are passing
[08:55:02 CST(-0600)] <Justin_o> yura_: okay... i guess we can add it on then... is bosmon going to review and commit?
[08:56:10 CST(-0600)] <yura_> yes, I will ask him to do that. Thanks , Justin_o
[08:56:21 CST(-0600)] <Justin_o> yura_: no problem.. thanks for the patch
[09:20:17 CST(-0600)] <heidi_> justin_o i was thinking i'd go through fss jiras and also add the issues unicon brought up - would that be a good thing to do today?
[09:21:09 CST(-0600)] <Justin_o> heidi_: you mean file jiras for the unicon ones?
[09:21:16 CST(-0600)] <heidi_> ya
[09:21:19 CST(-0600)] <Justin_o> okay...
[09:21:39 CST(-0600)] <heidi_> unless there's better stuff to be doing - let me know (smile)
[09:21:45 CST(-0600)] <Justin_o> heidi_: i'll try to get some more clarity on where we're at in the bug parade and release issues soon... so i may have some other stuff for you later
[09:21:51 CST(-0600)] <heidi_> okay cool
[09:23:12 CST(-0600)] <heidi_> jhung are you working from home? can you connect to http://source.fluidproject.org/svn/ ?
[09:23:42 CST(-0600)] <jhung> Heidi_: Yep. No probs here.
[09:23:51 CST(-0600)] <heidi_> weird...
[09:26:56 CST(-0600)] <Justin_o> heidi_: can you connect to any of our websites?
[09:27:35 CST(-0600)] <heidi_> justin_o no... waiting for jamon. i wonder if i'm blocked for some reason
[09:28:04 CST(-0600)] <Justin_o> heidi_: i think jamon is preparing for his defense later today... not sure if he will be around much
[09:28:18 CST(-0600)] <heidi_> oh right... errgh
[09:28:36 CST(-0600)] <heidi_> oh there he is
[09:30:33 CST(-0600)] <heidi_> okay i'm good now. thanks jamon!
[09:31:30 CST(-0600)] <jamon> Justin_o, heidi_, armin will be in today if something comes up
[09:31:40 CST(-0600)] <heidi_> cool
[09:32:58 CST(-0600)] <mlam> Justin_o: here are the JIRAs that colin, harris, and i covered for the uploader: FLUID-3843, FLUID-3722 (still work-in-progress), FLUID-3846, FLUID-3852, FLUID-3727, FLUID-3726, FLUID-3725, FLUID-3724, FLUID-3777, FLUID-3856
[09:33:27 CST(-0600)] <mlam> FLUID-3854 still needs to be done, but not for the demo .
[09:33:31 CST(-0600)] <Justin_o> mlam: that's a lot.. thanks
[09:33:36 CST(-0600)] <mlam> np
[09:36:11 CST(-0600)] <harriswong> Justin_o: layout reorderer jira: http://issues.fluidproject.org/browse/FLUID-3858
[09:36:34 CST(-0600)] <Justin_o> harriswong: thanks... i'll add that one onto the parade
[09:37:50 CST(-0600)] <Justin_o> harriswong: so you can still move to the empty column with the mouse?
[09:39:36 CST(-0600)] <harriswong> Justin_o: yes, just confirmed again on FF3.6
[09:39:55 CST(-0600)] <Justin_o> harriswong: okay... thanks
[09:40:34 CST(-0600)] <harriswong> Justin_o: np!
[10:14:25 CST(-0600)] <harriswong> jessm: I manually tested the grid/image/layout/list reorderer, all seems fine except for the layoutReorderer @ http://issues.fluidproject.org/browse/FLUID-3858. Tested with ff3, ff3.6, ie7, ie8.
[10:20:24 CST(-0600)] <jessm> harriswong: thanks so much for testing!
[10:21:46 CST(-0600)] <jessm> harriswong: nice jira! it's really clear what's going on. and it looks like Justin_o has added this to 1.3 bug parade
[10:21:52 CST(-0600)] <jessm> good and good!
[10:26:52 CST(-0600)] <harriswong> jessm: n[!
[10:26:58 CST(-0600)] <harriswong> jessm: *np!
[11:46:30 CST(-0600)] <colinclark> Hey jameswy, Processing.js 1.0 was released yesterday with full feature parity to regular Processing http://processingjs.org/
[12:04:30 CST(-0600)] <jessm> heidi_: how goes it?
[12:04:35 CST(-0600)] <jessm> what you working on?
[12:05:04 CST(-0600)] <heidi_> jessm just finishing a patch for builder. there's a weird IE thing i'm trying to fix
[12:05:16 CST(-0600)] <heidi_> ill send an email to list soon w/ links
[12:05:26 CST(-0600)] <heidi_> jessm is there something i can help with?
[12:06:20 CST(-0600)] <jessm> heidi_: just wanna make sure there's clarity for next steps, i know you had a pretty big list before all this sprint
[12:07:07 CST(-0600)] <heidi_> jessm i guess i'm focusing on helping w bug parade before going back to opencaps/matterhorn and then UI options
[12:08:12 CST(-0600)] <jessm> ok, good, that sounds reasonable – i don't have secret clarity on this, just want to make connections – jameswy does what heidi says make sense from your work trajectory? ^
[12:08:57 CST(-0600)] <heidi_> cool. i'm also going to switch my in-office day to wednesday so i can start playing soccer at lunch and also meeting up with jen for ui options work, when she's in
[12:09:08 CST(-0600)] <heidi_> (smile)
[12:10:48 CST(-0600)] <jameswy> jessm, heidi_: Yep, that works for me. How long do you think opencaps will tie you up for?
[12:11:26 CST(-0600)] <jessm> colinclark: does this make sense to you as well? i know we need to do more planning, but as a way forward? ^
[12:11:36 CST(-0600)] <heidi_> jameswy i only want to spend like a day just setting up MH, figuring out what the issues are and suggesting to matterhorn list... not actual fixing
[12:11:39 CST(-0600)] <jessm> heidi_: wed. is a popular day (smile)
[12:12:18 CST(-0600)] <colinclark> just catching up
[12:13:09 CST(-0600)] <colinclark> heidi_: Have you don e any work on triaging OpenCaps with Matterhorn so far?
[12:13:31 CST(-0600)] <heidi_> colin spent a little time trying to get the latest MH installed and running but that's it
[12:14:01 CST(-0600)] <colinclark> ok
[12:14:08 CST(-0600)] <colinclark> So they're still waiting to hear back from us about the issue?
[12:15:38 CST(-0600)] <colinclark> heidi_: ^
[12:15:45 CST(-0600)] <heidi_> yep
[12:15:50 CST(-0600)] <colinclark> Ok
[12:15:50 CST(-0600)] <heidi_> i talked to some in the chat tho
[12:15:56 CST(-0600)] <heidi_> but didn't reply to list yet
[12:15:57 CST(-0600)] <colinclark> Where's the chat?
[12:16:02 CST(-0600)] <heidi_> #opencast
[12:16:09 CST(-0600)] <colinclark> I don't think I even knew they had an IRC channel--cool!
[12:16:13 CST(-0600)] <heidi_> yep!
[12:16:30 CST(-0600)] <heidi_> i also replied to clemens saying i was going to look into it
[12:17:04 CST(-0600)] <colinclark> Okay, so you've got the Builder issue--anything else on your bug parade list so far?
[12:17:55 CST(-0600)] <heidi_> helping join w/ layout reorderer demo
[12:18:01 CST(-0600)] <heidi_> *jon
[12:18:10 CST(-0600)] <colinclark> ok, cool
[12:18:10 CST(-0600)] <heidi_> then justin_o was going to give me more
[12:18:19 CST(-0600)] <jessm> jhung: you're pecking away at bud parade issues then?
[12:18:37 CST(-0600)] <colinclark> So, maybe let's aim to do that triage of OpenCaps by end of next week, along with a response to the mailing list?
[12:18:46 CST(-0600)] <heidi_> colin that sounds good
[12:18:48 CST(-0600)] <colinclark> I'd like to help with that if I could
[12:18:51 CST(-0600)] <heidi_> cool
[12:19:10 CST(-0600)] <jessm> mlam: you're continuing to wrestle with uploader, right?
[12:19:12 CST(-0600)] <jhung> jessm: yes. Trying to wrap code cleanup on layout reorderer so it can be code reviewed.
[12:19:21 CST(-0600)] <mlam> jessm: yes, i am
[12:19:23 CST(-0600)] <heidi_> it def seems like matterhorn work is continuing full-force so good to keep tabs on that
[12:19:36 CST(-0600)] <colinclark> mlam: What part of Uploader are you working on at the moment?
[12:19:41 CST(-0600)] <jhung> jessm: I mean markup cleanup, not the javascript.
[12:19:53 CST(-0600)] <mlam> i'm trying to get the image gallery to run the html5 uploader
[12:20:06 CST(-0600)] <jessm> and jhung and jameswy your'e going to catch up with each other on moving the pager demo forward, right? tools?
[12:21:04 CST(-0600)] <colinclark> mlam: tell me more
[12:21:27 CST(-0600)] <mlam> by default, the image gallery is expecting the SWFUPloader to run
[12:21:41 CST(-0600)] <jameswy> jessm: jhung and I already met a couple of days ago about the pager demo--he's got some great next steps for evolving it
[12:21:48 CST(-0600)] <jessm> awesome
[12:22:02 CST(-0600)] <mlam> in the image-gallery.js file , i'm trying to force the gallery to run the html5 uploader instead for testing purposes
[12:22:49 CST(-0600)] <colinclark> mlam: Should be pretty straightforward. How is it going so far?
[12:23:07 CST(-0600)] <jessm> harriswong: you're working on the reorderer bug you filed, right?
[12:23:14 CST(-0600)] <Justin_o> fluid-everyone: sent out a big bug parade upadate
[12:23:41 CST(-0600)] <mlam> colinclark: it's looking at the html5 code, but looking into why the browse button isn't opening the file dialog
[12:24:09 CST(-0600)] <mlam> there's an error telling me that the html5 strategy can't be found
[12:24:19 CST(-0600)] <colinclark> mlam: So I had this working my own working copy... should be two things
[12:24:35 CST(-0600)] <colinclark> 1. Update the AddImages.html file with the correct JS dependencies
[12:24:44 CST(-0600)] <colinclark> (which is why the HTML 5 strategy can't be found)
[12:24:55 CST(-0600)] <mlam> ahhh
[12:25:01 CST(-0600)] <colinclark> 2. Just override the options to the Uploader, replacing SWFUpload with the HTML 5 strategy
[12:26:28 CST(-0600)] <mlam> ok, got it, thanks!
[12:26:43 CST(-0600)] <colinclark> Update 42, Justin_o!
[12:26:56 CST(-0600)] <michelled> up Yonge street we go
[12:27:06 CST(-0600)] <Justin_o> (smile)
[12:27:11 CST(-0600)] <colinclark> We must be, at least, in North York by now
[12:31:10 CST(-0600)] <Justin_o> fluid-everyone: did you want to talk about what's left on the bug parade, some other issues that came up, and generally i guess what we want to make sure gets in to the 1.3 release
[12:31:10 CST(-0600)] <mlam> justin_o have those screen reader issues for inline edit been addressed yet?
[12:31:27 CST(-0600)] <Justin_o> mlam: which one was that, the autocomplete one?
[12:31:38 CST(-0600)] <colinclark> Justin_o: sure
[12:32:05 CST(-0600)] <mlam> there are a bunch of them....FLUID3811 .. to FLUID-3815
[12:33:18 CST(-0600)] <Justin_o> oh those ones that jonathan had mentioned before?
[12:33:25 CST(-0600)] <mlam> yeah
[12:33:37 CST(-0600)] <Justin_o> i'm not sure those are issues since no one seemed to bring them up yesterday, but we should confirm for sure
[12:33:45 CST(-0600)] <Justin_o> jhung: can we drop close those ones off?
[12:34:55 CST(-0600)] <jhung> justin_o: give me a sec...
[12:36:37 CST(-0600)] <Justin_o> fluid-everyone: anyone else interested in talking about the bug parade and issues for the 1.3 release... probably easier to do it face-to-face or over skype
[12:36:56 CST(-0600)] <colinclark> i'm cool either way
[12:37:08 CST(-0600)] <colinclark> we can do face to face and skype in anyone who isn't here in the office at the moment
[12:37:47 CST(-0600)] <Justin_o> sure, sounds good
[12:41:00 CST(-0600)] <jhung> justin_o: They should still be issues. FLUID-3814 and FLUID-3815 will require user testing / feedback from users.
[12:41:08 CST(-0600)] <jhung> mlam^
[12:41:30 CST(-0600)] <jhung> justin_o mlam, FLUID-3811 to 3813 are still issues.
[12:42:27 CST(-0600)] <harriswong> jessm: yep, i am working on that jira bug i filled.
[12:44:06 CST(-0600)] <jhung> justin_o, mlam: actually there may be new bugs as well (i.e. none of the tooltip text is being read by NVDA in IE8, undo/redo buttons are just being read as links etc.).
[12:44:10 CST(-0600)] <colinclark> jhung and Justin_o: I'm puzzled about FLUID-3814 and FLUID-3815 in terms of the bug parade...
[12:44:23 CST(-0600)] <colinclark> What's the deliverable? How do we know we've done these tasks and checked them off for the bug parade?
[12:44:45 CST(-0600)] <jhung> colinclark: justin_o was asking if they can be closed. I say no.
[12:45:15 CST(-0600)] <colinclark> I'm fine with that, but the question is "what needs to be done to fix them?"
[12:45:33 CST(-0600)] <colinclark> In themselves, I think they're too vague to be on the bug parade
[12:46:05 CST(-0600)] <colinclark> What are the actual tasks we'd do to fix them?
[12:46:50 CST(-0600)] <jhung> colinclark: It needs more investigation for certain. Definitely not a concrete task at this point.
[12:47:12 CST(-0600)] <jhung> colinclark: can be dropped from bug parade.
[12:47:32 CST(-0600)] <colinclark> I didn't want to drop them from bug parade
[12:47:43 CST(-0600)] <colinclark> I wanted to know what to do to start fixing them
[12:49:38 CST(-0600)] <jhung> colinclark: someone needs to use the demo and find out if the feedback being given in both JAWS and NVDA is acceptable. Then from there we can determine what needs to be focused on. Right now it feels like the feedback is a bit convoluted (esp. in NVDA), but it may actually be acceptable to users.
[12:49:50 CST(-0600)] <colinclark> yeah
[12:49:55 CST(-0600)] <colinclark> So we need to do a user test, perhaps?
[12:50:34 CST(-0600)] <colinclark> maybe we should file a subissue for that
[12:50:36 CST(-0600)] <colinclark> brb
[12:50:50 CST(-0600)] <jhung> colinclark: yes. We've added a lot in terms of a11y to the component. It's time we did some testing to refine things.
[13:24:22 CST(-0600)] <swei> hi
[13:28:08 CST(-0600)] <jessm> greetings swei
[13:28:16 CST(-0600)] <swei> Hi jessm
[13:28:31 CST(-0600)] <swei> I'm new to the fluidproject and sakai
[13:28:50 CST(-0600)] <jessm> swei: well, welcome! who are you working with in sakai?
[13:28:54 CST(-0600)] <swei> I've a question regarding the image gallery component
[13:29:26 CST(-0600)] <swei> I'm working for UC Davis
[13:30:11 CST(-0600)] <jessm> swei: we're all in a mtg. right now, but you should definitely ask your question and stick around for an answer
[13:31:53 CST(-0600)] <swei> great. thank you. a little background here: I followed the integration guide specified here http://wiki.fluidproject.org/display/fluid/Walkthrough+-+Building+and+using+the+Image+Reorderer+in+Sakai#Walkthrough-BuildingandusingtheImageReordererinSakai-5.CheckouttheImageReordererenabledImageGallerytool
[13:33:53 CST(-0600)] <swei> In the pom.xml of image-gallery, I changed the fluid-components version to 0.6.
[13:36:52 CST(-0600)] <swei> the image-gallery component compiled and deployed. but the problem is that sometimes the thumbnails are aligned vertically instead of horizontally
[13:37:32 CST(-0600)] <swei> and keyboard shortcuts don't seem to work when that happens.
[13:39:04 CST(-0600)] <michelled_> swei: are you getting a javascript error?
[13:41:27 CST(-0600)] <swei> yes, one. in firefox. it says that "fluid.lightbox is not a function"
[13:45:16 CST(-0600)] <colinclark> swei: Unfortunately the Image Gallery isn't something that is supported anymore. It was written by developers at UC Berkeley back in 2007, and since then they've stopped developing it.
[13:45:25 CST(-0600)] <colinclark> I imagine with changes to Sakai since then, it probably doesn't work very well
[13:46:52 CST(-0600)] <swei> ok. just curious, do you have any theories on why does it behave inconsistently?
[13:47:40 CST(-0600)] <colinclark> swei: From the errors you're seeing, it looks to me like that version of the Image Gallery is running an ancient version of Infusion
[13:47:50 CST(-0600)] <swei> right.
[13:48:23 CST(-0600)] <colinclark> I imagine it would need some refactoring to update it to a recent version of the Image Reorderer
[13:48:36 CST(-0600)] <colinclark> If you did that you might be able to get it working
[13:48:49 CST(-0600)] <colinclark> The difficult part is that the Image Gallery was never feature-complete before Berkeley stopped supporting it
[13:49:12 CST(-0600)] <colinclark> So it's one of those things that, if you wanted to use it, you'd have to put some fairly substantial development cycles into finishing it
[13:49:38 CST(-0600)] <swei> I see.
[13:54:08 CST(-0600)] <heidi_> colinclark jessm am starting FLUID-3842
[13:55:11 CST(-0600)] <colinclark> swei: What were you hoping to do with the Image Gallery?
[13:56:08 CST(-0600)] <swei> trying to find a replacement for the presentation tool which is deprecated in the newer version of sakai
[13:57:55 CST(-0600)] <swei> it's basically providing the image-viewer capability into the image files specified in the Resource tool.
[13:59:30 CST(-0600)] <swei> besides that glitch, image-gallery seems to deliver the view feature quite well...
[14:09:23 CST(-0600)] <jhung> heidi_: Just a reminder to put flc- classes before any fl- or demo- classes in the HTML markup. I forgot, so I thought I'd remind you as well. (big grin)
[14:09:35 CST(-0600)] <heidi_> cool will do
[14:09:52 CST(-0600)] <heidi_> jhung again, why does it matter if flc doesn't have any styles
[14:10:02 CST(-0600)] <heidi_> just for cleanness?
[14:10:32 CST(-0600)] <jhung> heidi_: Yes ease of readbility. Often we're looking for a single FLC and if it's at the end of the list, it's hard to spot.
[14:10:44 CST(-0600)] <jhung> at most we have only 1 flc class anyway.
[14:11:16 CST(-0600)] <heidi_> cool
[14:21:24 CST(-0600)] <heidi_> armin on irc?
[14:21:55 CST(-0600)] <heidi_> i think the server has blocked me again...
[14:30:56 CST(-0600)] <jhung> jameswy: do you have a sec to chat about http://issues.fluidproject.org/browse/FLUID-3839?
[14:31:11 CST(-0600)] <jameswy> jhung: Sure
[14:31:35 CST(-0600)] <jhung> jameswy let's try chatting in the channel for now. (smile)
[14:32:16 CST(-0600)] <jhung> jameswy: my question is: do you think it is confusing that a warning message appears even though there is a valid drop marker indicated?
[14:32:47 CST(-0600)] <jameswy> jhung: Yes. And, it doesn't sound like a warning message at all. Sounds more like an error.
[14:33:54 CST(-0600)] <jhung> jameswy: so... 1. Do you think presenting no message at all, and just showing the drop marker is understood by the user?
[14:33:54 CST(-0600)] <jhung> 2. Do you think a message should be displayed in this case, if so, what should it say?
[14:35:43 CST(-0600)] <jameswy> jhung: Let me make sure I understand the problem correctly. Is this the case where the user drags and drops a moveable element into a fully locked region?
[14:36:40 CST(-0600)] <jhung> jameswy: yes. And by default the nearest valid drop marker will be displayed in addition to the warning text.
[14:38:05 CST(-0600)] <jameswy> jhung: In that case, I think that we have one of two sensible options: 1) have neither drop marker nor a warning message, and do not move the element, or 2) show the nearest drop marker, show no warning message, and drop the element at said nearest drop marker
[14:41:03 CST(-0600)] <jhung> jameswy: hmmm. I think option 2 is best since it's possible the user may intend the move to around the locked region, but just isn't precise with their mouse movement.
[14:43:14 CST(-0600)] <jameswy> jhung: That sounds very sensible to me.
[14:44:28 CST(-0600)] <jhung> jameswy: thanks.
[14:48:19 CST(-0600)] <jhung> jessm: I'd like your thoughts on this: http://issues.fluidproject.org/browse/FLUID-3839 (be sure to read the comments too).
[14:54:09 CST(-0600)] <jessm> jhung: i'll take a look in a minute – in a mtg.
[14:54:28 CST(-0600)] <jhung> thanks!
[14:55:02 CST(-0600)] * jhung going to move forward on new pager designs.
[15:00:36 CST(-0600)] <jessm> jhung: i'm interested to hear what you're thinking re: 3839
[15:01:35 CST(-0600)] <jhung> jessm: my concern is that we're removing functionality from the demo to fix a usability issue in the demo.
[15:02:42 CST(-0600)] <jhung> jessm: If we want to keep the warning message in as a feature, I'm going to need to think more about how it can be incorporated.
[15:03:40 CST(-0600)] <jessm> well, jhung inneresting
[15:03:47 CST(-0600)] <jessm> i'm thinking, there might be a middle ground
[15:04:01 CST(-0600)] <jessm> are we really losing functionality? what if we display the "error" differently?
[15:05:22 CST(-0600)] <jhung> jessm: yes. That thought crossed my mind too, but having a valid drop marker already displayed is pretty succinct. Not sure what else we can say that will make things clear or informative.
[15:05:44 CST(-0600)] <jessm> what about a non-drop marker? instead of a message?
[15:07:31 CST(-0600)] <anastasiac> jhung, jessm, can I join in here? Justin_o, michelled, colinclark and I discussed this issue in the bug parade review
[15:07:47 CST(-0600)] <jessm> yes, please, of course!
[15:08:05 CST(-0600)] <anastasiac> one of the things we noted was that it's not actually invalid to show both the warning and the drop target at the same time
[15:08:22 CST(-0600)] <anastasiac> the drop target is still valid: If you should happen to 'drop' at that moment, that's where it will end up
[15:08:33 CST(-0600)] <anastasiac> and the warning is valid: you can't drop it where you're trying to drop it
[15:08:57 CST(-0600)] <anastasiac> it's a challenge, but it's not really appropriate to, for example, remove the drop indicator
[15:09:01 CST(-0600)] <anastasiac> doe sthis make any sense?
[15:09:55 CST(-0600)] <anastasiac> I think our general impression is "this is how it's supposed to work"
[15:10:15 CST(-0600)] <anastasiac> i.e. not a bug, but maybe something worthy of user testing, to see if users find it confusing?
[15:10:24 CST(-0600)] <jessm> anastasiac: i wondered that – i'm not thoroughly convinced it's a really bad interaction
[15:10:33 CST(-0600)] <jessm> +1 user testing
[15:11:14 CST(-0600)] <jhung> jessm, anastasiac: I'm all for more user testing. +1
[15:11:41 CST(-0600)] <jhung> So I think the wording of the warning should be massaged a little to be a little more clear. Then test it with some users.
[15:11:54 CST(-0600)] <anastasiac> cool. our thoughts when we discussed it was "let's not make any changes for this issue now"
[15:12:09 CST(-0600)] <anastasiac> jhung, what would you change the wording to?
[15:13:04 CST(-0600)] <jhung> anastasiac: not sure at the moment, but something a little less severe. Currently it just references the fact you can't drop onto a locked area, but makes no reference to the fact it will be dropped elsewhere.
[15:14:02 CST(-0600)] <anastasiac> well, the drop indicator is still there, so that does tell you where it will go... of course, that's probably not read out loud, is it? (smile)
[15:14:05 CST(-0600)] <jhung> anastasiac: the text should at least mention what will happen when the user releases the mouse. Otherwise they may think bad things are going to happen. (big grin)
[15:15:18 CST(-0600)] <anastasiac> jhung, maybe put this suggestion on the JIRA, and Justin_o can give thought to whether or not it's bug-parade worthy. The parade is pretty long, so I'm guessing it might not make it this round
[15:15:32 CST(-0600)] * anastasiac is trying to remember if the Santa Claus Parade is this weeken...
[15:15:56 CST(-0600)] <anastasiac> yep: sunday: http://www.thesantaclausparade.ca/
[15:16:28 CST(-0600)] <jhung> anastasiac: will do.
[15:16:34 CST(-0600)] <jessm> i think that Justin_o is likely to refocus us away from this bug to something bigger and more immediate
[15:16:59 CST(-0600)] <anastasiac> 106 years that parade has been going... wow...
[15:17:06 CST(-0600)] <jhung> jessm: yes. Seems like some user testing post 1.3
[15:20:35 CST(-0600)] <justin_o_> jhung: is your patch on FLUID-3855 ready to go through review... or is there still more work to do?
[15:21:29 CST(-0600)] <jhung> justin_o: it should be ready to go.
[15:21:46 CST(-0600)] <justin_o_> jhung: okay thanks.. we're adding that one to bug parade.. i'll mark it for review
[15:31:47 CST(-0600)] <justin_o> harriswong: this page might be helpful to you http://wiki.fluidproject.org/display/fluid/The+Geometric+Manager
[15:32:11 CST(-0600)] <harriswong> justin_o: thanks!
[15:32:28 CST(-0600)] <justin_o> np