Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 342618

Summary:	Hover affordances for remove from context/mark as landmark
Product:	z_Archived	Reporter:	Sam Davis <sam.davis>
Component:	Mylyn	Assignee:	Mylyn Inbox <mylyn-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	shawn.minto
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Sam Davis

2011-04-12 13:59:24 EDT

Now that there's a hover affordance for show filtered children, I sort of want affordances for remove from context and mark as landmark (MS Office style I guess). I don't know if it's really a good idea, but I've always felt like those actions are useful to have, but too hard to get to for the value they provide, i.e. it's usually not worth the trouble of right clicking and finding them in the enormous context menu. Having affordances would also mean you wouldn't have to select the item (which switches editors) to perform those actions, and that we could eventually remove those options from the menu.

Comment 1 Shawn Minto

2011-04-12 15:12:26 EDT

I think that this could be a really good idea as well.  The question is how would this look with 3 icons per hover instead of 1.  Maybe will mock something up and see how usable/cluttered it would be.

Comment 2 Sam Davis

2011-04-12 15:27:25 EDT

We should also consider that there are some problems with the exisiting affordance. I'm thinking of how it sometimes is clipped, that it doesn't always draw over the Windows tree tooltip, and bug 341589.

Comment 3 Steffen Pingel

2011-04-12 15:46:17 EDT

I am a bit worried that adding additional affordances would add significant complexity and make it difficult to pick the right button. Sam, how frequently do you use mark as landmark and remove from context? 

Generally, the context framework should manage the context through monitoring interactions and there should rarely be a need to manually change interest on elements. Just curious if this isn't working as expected and if there is something else that could be done to optimize the context mangement.

Comment 4 Sam Davis

2011-04-12 16:14:01 EDT

I would say I use them once in a while.

I think the main use for remove from context is after some exploration where I realise the code I was exploring is not relevant (or if I started briefly working on something else without switching context, because I forgot or had files with unsaved changes). I don't think there is any way for this to be automatically detected, although I could imagine having some way of explicitly partitioning the interaction history, like a sub-context switch...

I mainly use mark as landmark when I find something that I know is important and I may not be interacting much with the important element right away, but I don't want to lose it.

I'm not sure we want to encourage people to use these actions a lot though, or to create the perception that they are often needed... Perhaps it could be an advanced/experimental option you have to turn on if you want it.

Comment 5 Shawn Minto

2011-05-02 14:00:59 EDT

I think that I am with Steffen on this now and that it would cause too much clutter for the little that they are used. Should we mark this as wontfix?

Comment 6 Sam Davis

2011-05-02 14:21:42 EDT

I think I agree. It would sort of be nice if I could hold down a key and click to perform those actions, but I can't see what keys could be used for that.

Comment 7 Shawn Minto

2011-05-04 21:15:50 EDT

Sounds good.  Will mark as WONTFIX for now.