Bug 26621

Summary:	Filter in Sync view
Product:	[Eclipse Project] Platform	Reporter:	DJ Houghton <dj.houghton>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	axel.carl.mueller, daniel_megert
Version:	2.1	Keywords:	usability
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description DJ Houghton

2002-11-18 18:13:47 EST

build 2002-11-15b, win2k, j9

This is a usability issue.

When there are multiple changes between my workspace and the server, it would 
be good if I could apply a filter to the resources that are shown in the sync 
view.

Consider the following use case: 
- I have a project which contains thousands of resources of types html and java 
- I want to synchronize and automatically release all my html file changes
- in order to do this I might ctrl-click each one since they are found through-
out my source folders in my project

I would like to be able to apply a filter which would should be only *.html 
from which I could release the changes and then I could turn off the filter and 
then it would show me my remaining Java file changes.

Comment 1 Andrew Low

2002-11-18 18:23:22 EST

This is made worse when you have a .c, .cpp, .asm, .h world.  You are 
frequently mixing and matching file types.

Please also consider that some projects will use prefixes vs. suffixes to 
distinguish program areas.  Being able to filter on any part of the filename 
would be useful.

Comment 2 Michael Valenta

2005-05-06 16:16:43 EDT

This bug has not been touched in 2 years. Closing as WONTFIX. If you feel this 
bug is important, feel free to reopen it.

Comment 3 DJ Houghton

2005-05-06 16:30:11 EDT

I think it would be a good enhancement. Especially in (for instance) the CDT
world where developers deal with multiple file extensions.

Comment 4 Michael Valenta

2005-05-06 16:36:27 EDT

Moving to LATER

Comment 5 Denis Roy

2009-08-30 02:23:19 EDT

As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.

Comment 6 Axel Mueller

2010-01-22 04:22:53 EST

(In reply to comment #5)
> Please reopen this bug if it is still valid for you.
I think this bug is still valid. The scenario described in comment #0 and #1 sounds very familiar to me. I was looking to get around this by any other means but did not succeed. So if anyone could please reopen this bug (otherwise I have to open a new bug because I have no rights for this bug entry).