Description libing wang 2012-05-30 09:10:33 EDT

In replace page, we still have check box now.
I planned to remove the check box and replace them by selection model.
I talked to several people and they gave suggestions from user's point of view:

McQ suggested:
1.Remove the check box and use selection model the similar way we use for navigator.
2.Have select all action on the header.
3.When selecting/deselecting a container(e.g. file), all the children(e.g. matches) are selected/deselected automatically.  
4.The default action on a row highlights the matching diff in the compare widget.

Simon said if we will use selection model, he will feel inconvenient when selecting matches.

Susan suggested:
1.We should use check box till we have a good design regarding what containment level selection means.
2.In replace page, user's focus is on a set of selection. If user works hard on selecting a set and click some where else by mistake it will just deselect every thing. Basically we need a toggle mode and do not surprise user with a good UI gesture.

Given we are in RC1 now, I think for 0.5 we will use check box.
McQ's suggestion makes sense post 0.5. We need refinements on top of that.
Post 0.5, we need to add options like toggle mode and container level selection policy. We also need good UI gesture without surprising user that the selection behaves differently.