Bug 3813 - Build path wizard - existing source folders should always be available (1GEUN2J) [build path]
Summary: Build path wizard - existing source folders should always be available (1GEUN...
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows NT
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Martin Aeschlimann CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate
Depends on:
Blocks:
 
Reported: 2001-10-10 23:01 EDT by Philipe Mulet CLA
Modified: 2003-01-10 03:20 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2001-10-10 23:01:18 EDT
The UI for choosing/adding a source folder on the build path is not consistent with the one for selecting a project on the classpath; and I prefer the latter which does always
present to me the available items for free.

When adding source folders onto a project classpath, I have to explicitly select "Add Existing Folders" in order to pick any from them, where I would like this to be the default.

NOTES:
EG (6/5/2001 3:24:45 AM)
	valid observation, but can't fix for June.
	moving to inactive
Comment 1 Martin Aeschlimann CLA 2001-10-16 11:13:09 EDT
moved to 'active'
Comment 2 DJ Houghton CLA 2001-10-24 07:21:22 EDT
PRODUCT VERSION:
SDK 119

Comment 3 Erich Gamma CLA 2001-11-10 19:28:44 EST
defer
Comment 4 Dirk Baeumer CLA 2002-07-25 12:35:36 EDT
A good suggestion. We should use a check box table for the source folder tab as 
well
Comment 5 Martin Aeschlimann CLA 2002-10-09 08:56:31 EDT
I'm not really convinced of this suggestion.
The difference between the project selection and the source folder selection is 
that the set of projects is fixed, where as for folders you can add new entries.

The second difference is that also subfolders can be added. So when presented 
in a list, the list would contain a flatted list of all possible paths
folders
folders/src1
folders/src2
doc
doc/api
doc/api/topic1

So it seems a tree could help. Checkbox trees are problematic in general: You 
have to expand a tree to see all entries, the check state of a parent has to 
reflect the check state of its children. 

How would you do it?

Comment 6 Philipe Mulet CLA 2002-10-09 12:20:40 EDT
Or maybe present it to me in the same way as the export wizard which also has 
some checkboxes. Though here I would not want the parent to be selected as soon 
as I pick its child.
Comment 7 Martin Aeschlimann CLA 2003-01-10 03:20:24 EST
new build path uses node children for attributes