make simple edit-alternative to double click+discussion
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
nice!
--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:
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
--John Abbe.....2013-03-21 22:46:48 +0000