Page Comparison

[13:55:08 EST(-0500)] * JASIGLogBot (i=jasigch@jasigch.Princeton.EDU) has joined #fluid-work
[13:55:19 EST(-0500)] <EricDalquist> all fixed
[14:01:59 EST(-0500)] <jhung> Excellent! Thanks Eric!
[14:02:44 EST(-0500)] <EricDalquist> no problem ... sorry I didn't notice earlier
[14:38:42 EST(-0500)] <clown> everyone: In case you didn't see the email on the fluid-work mailing list, fluid's svn repository is going offline today at 2:45pm est ((= 1:45pm central, 11:45am PST, and 7:45pm in London England)
[14:39:22 EST(-0500)] <clown> if you are about to commit, do it soon, or squirrel those changes safely away.
[14:40:19 EST(-0500)] <jhung> done and done.
[15:12:56 EST(-0500)] <michelled> EricDalquist: we all thought the log bot went on vacation with you
[15:13:21 EST(-0500)] <EricDalquist> that would be weird ... not sure I want my vacation logged
[15:13:32 EST(-0500)] <michelled> lol!
[15:21:52 EST(-0500)] <michelled> clown: I originally thought that Fluid 187 was just going to be a quick fix which involved adding columns as drop targets however when I tried it it became clear that the issue involves a lot of styling problems as well.
[15:22:49 EST(-0500)] <clown> so you've tried to simply add the columns to the drop target list as created by createFindItems()?
[15:23:13 EST(-0500)] <michelled> Yes but didn't commit it because of the bizarre user experience.
[15:24:16 EST(-0500)] <clown> i doubt it would work now that the code checks to see if a drop target really is a drop target (by consulting the permissions), although that could be modified methinks.
[15:24:21 EST(-0500)] <michelled> We may require the ability to style drop targets in two different ways.
[15:25:02 EST(-0500)] <michelled> Well, we still do need to check the permissions. One issue we have is that we are overloading the word drop target.
[15:25:30 EST(-0500)] <michelled> The 'permissions' drop targets refer to the gaps between portlets.
[15:25:57 EST(-0500)] <michelled> The drop targets that we use in the DnD code and that we style refer to what the mouse is hovered over when a drop occurs.
[15:26:48 EST(-0500)] <michelled> So, when a column gets drop, we'll need to see where the mouse is and then check the permissions. It's not trivial.
[15:28:13 EST(-0500)] <clown> not sure... there is the green bar that we draw, and refer to as a dropTarget in the code, and there is the, well for now, portlet that we are hovering over. when you said we style the drop target, I assume you mean the green bar, not the portlet.
[15:29:19 EST(-0500)] <clown> pardon me, "dropMarker".
[15:32:18 EST(-0500)] <clown> a thought: when a column is empty, the layout data thingy reflects that with an empty array for the column. I wonder if that can be leveraged.
[15:33:19 EST(-0500)] <michelled> The issue is bigger then empty portlets. It is also when hovering over whitespace between portlets. That was the specific case that came up in the user testing.
[15:33:32 EST(-0500)] <EricDalquist> A thought from reading the latest user testing ... perhaps when you try to drag a locked portlet have the cursor change to a lock icon or a crossed out circle icon or an X icon or some such
[15:33:45 EST(-0500)] <clown> oh.
[15:34:40 EST(-0500)] <clown> My intuition says that hovering over whitespace between portlets and detecting that is a whole new ball game. One we have avoided until now.
[15:36:01 EST(-0500)] * shawhan (n=Sakai2@142.150.154.166) has joined #fluid-work
[15:36:40 EST(-0500)] <michelled> hey shawhan, EricDalquist had a good suggestion for dealing with communicating that a portlet is locked.
[15:36:49 EST(-0500)] <michelled> "A thought from reading the latest user testing ... perhaps when you try to drag a locked portlet have the cursor change to a lock icon or a crossed out circle icon or an X icon or some such"
[15:38:21 EST(-0500)] <shawhan> that's a great idea, we will try that!
[15:38:22 EST(-0500)] <michelled> clown: yes you're right. That's why the estimate skyrocketed from 1.5 days to 4 days
[15:38:47 EST(-0500)] <clown> only 4??? ;-P
[15:39:29 EST(-0500)] <EricDalquist> thanks
[15:39:32 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[16:23:54 EST(-0500)] * michelled (n=team@142.150.154.199) has left #fluid-work
[16:41:02 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[16:58:12 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[17:16:13 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[17:30:11 EST(-0500)] * clown (n=clown@user383.megabit.utoronto.ca) has left #fluid-work
[17:30:15 EST(-0500)] * clown (n=clown@user383.megabit.utoronto.ca) has joined #fluid-work
[17:35:15 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[17:55:18 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[18:08:42 EST(-0500)] * shawhan (n=Sakai2@142.150.154.166) has left #fluid-work
[18:13:40 EST(-0500)] * slightlyoff (n=alex@204.14.154.209) has joined #fluid-work
[18:24:33 EST(-0500)] * colinclark (n=colin@142.150.154.101) has joined #fluid-work
[18:42:02 EST(-0500)] * RayDavis (n=chatzill@dhcp-169-229-212-40.LIPS.Berkeley.EDU) has joined #fluid-work