make simple edit-alternative to double click



Solving this would let us remove the add/edit link under Pointers, offer a nice alterative to double-click-to-edit, and depending on the solution give access to other tabs when not in open/closed view.


We ended up with refactor card menus - the menu that pops up from the little gear/cog to the right of any card name in open/closed view (and it can be added to most(?) other views with "show:menu"), vaguely similar to #2 below.




Two Earlier possibilities:




Cards in any view (that has card slot info) other than open or closed can be triggered to show the title bar - but translucent - over the top of the card's content.


The trigger could be hovering over the card for a second or so, or clicking on the card content (hrm, that wouldn't work for cards with content that already have a behavior when clicked, e.g. collections with item:link or any text type with only a link as content). Could offer both...


In any case, if the user clicks on the faint title bar, the card's view changes to open - the content slides down, the title bar becomes opaque, and the footer appears at the bottom. If they click on a control in the faint title bar, the click could be processed directly. If we do this, could also have a faint footer appear - this would make for one-click card watching.


If they click View, it goes back to its original view.


Note that this only happens if the card's "+*edit controls" points to "hover" (or "click" depending on how this is triggered). *all+*edit controls defaults to this method being on, and "double click" being off. See Ability to disable double-click-to-edit.





A small interface like this:

inclusion popup interface mockup

...that can pop up whenever you hover over an inclusion not in open/closed view, perhaps just offering an edit link for now, but to which we could later add the "More..." menu, which can offer View, Changes, Options/Settings, Related, and from card footers: "Cards" (maybe "Parts" is a better term for this?) with a submenu showing those links, "Last Editor: |name|", and the "watch" link.



The proposed solution here drew in part from What's up with date? I think i got everything from there, but wanted to link just in case...

I like where this is heading.


When I first saw that button, I wondered "what does 'edit more' mean?". We'll probably need to make it visually obvious that they're 2 different things. Probably want something greyscale so it looks good with lots of wagns, and we'll probably want the two.

  --Ethan McCutchen.....Mon May 03 12:37:26 -0700 2010

An additional possibility (we want a visible interface in any case) is key commands for save and edit as a non-double-click way to edit cards. For this to be useful, the key command for edit would have to bring up an interface to choose whether to edit the main card of the page, or one of the included cards. This interface would have to be pretty speedy to be useful.


(said John Abbe, a while back, on improve interface around content view inclusions

  --Ethan McCutchen.....Tue May 04 15:08:31 -0700 2010

Would handle part 1 of implement watch links as a card

  --John Abbe.....Thu Feb 17 11:57:27 -0800 2011

I would actually say that we basically have a very viable alternative now -- the gear menu. The only real need is to make it available in the content view, which should be very straightforward.

  --Ethan McCutchen.....2013-03-04 18:33:23 +0000


  --John Abbe.....2013-03-04 19:02:54 +0000

So, tag Wagn 1.11? And when we release it, scan this and pull anything left out to a new ticket?

  --John Abbe.....2013-03-14 05:00:18 +0000

sounds good.

  --Ethan McCutchen.....2013-03-14 05:28:35 +0000

though I don't really want to advertise the mechanism for turning off clicks yet.

  --Ethan McCutchen.....2013-03-14 05:29:08 +0000

I like 2 much better, although I suppose it could be a Wagneer choice.


What I like the best about 2 is that it should be 'skinnable', so we could even put an image widget with the controls we want on it, and then we can design the UX with several icons, one for each key function. Clicking it might anchor it tempararily on the page, or even expand it to a larger view or one with labels too, etc.

  --Gerry Gleason.....2013-03-14 10:53:35 +0000

I hadn't been thinking about making that the menu; I'd been expecting we'd focus on these as two separate issues:


1. make the menu Wagneerable 

2. creating different patterns for making the menu appear.


In general I wouldn't want to create core support for lots of navigation subsystems, because on the face of it that sounds like more for users to learn. But of course we really need to make the system we build flexible and responsive.

  --Ethan McCutchen.....2013-03-14 16:41:12 +0000


upgrade the menu

  --John Abbe.....2013-03-21 22:46:48 +0000