Bug 194075 - Combine Empty Folders In File Listing Views
Summary: Combine Empty Folders In File Listing Views
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2.2   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Boris Bokowski CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-22 19:06 EDT by Nick T CLA
Modified: 2019-09-06 16:12 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick T CLA 2007-06-22 19:06:28 EDT
Combine empty folders in search and navigator (and any other view that lists files) like empty packages are in the JDT Package Explorer.  Instead of using dots use slashes.

e.g.
Instead of this:
- a
  - b
    - c
      |- file1.java
      |- file2.java

Do this:
- a\b\c
  |- file1.java
  |- file2.java
Comment 1 Kevin McGuire CLA 2007-06-25 15:07:50 EDT
The suggestion does have the benefit of compacting the trees for cases where there is a deep tree with files just at the edges.  However, this doesn't work as well if there are files through different levels of the tree: since each level requires its own path entry, the "treeness" is lost, eg:

- a
  |- file1.txt
- a\b
  |- file2.txt
- a\b\c
  |- file3.txt
  |- file4.txt

I'm not sure that's applicable for all types of trees.
Comment 2 Nick T CLA 2007-06-28 13:52:19 EDT
(In reply to comment #1)

I apologize; I wasn't clear with what I meant.

The idea would be to collapse the tree as far as possible, wherever possible, while not duplicating information (tree paths); it should mimic the way packages are handled in the JDT Package Explorer.

- a
  - b1\c1
    |- file2
    |- file3

  - b2\c2\d2\e2 (empty)

  - b3
    - c3\d3
      - e3
      |- file5
    - c31
    |- file4

 |- file1
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:12:19 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.