This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 32901 - Usability issue related to nonrefreshing folders
Summary: Usability issue related to nonrefreshing folders
Status: VERIFIED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: jrojcek
URL:
Keywords:
: 33602 (view as bug list)
Depends on:
Blocks: 35485
  Show dependency tree
 
Reported: 2003-04-15 12:25 UTC by Jan Becicka
Modified: 2008-12-22 18:25 UTC (History)
5 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Becicka 2003-04-15 12:25:44 UTC
I wanted to create a new java application from
existing sources. I started the wizard and wanted
to add a java source root. I already had the
source files, but - unfortunately - they were
archived in the zip file. I went to system console
to unzip the sources and then back to IDE. But I
couldn't see the folder with my sources, even if I
restarted the wizard. I think this is serious problem.
Comment 1 Vitezslav Stejskal 2003-04-15 13:02:02 UTC
OK, this is neveredning story, the filesystems aren't refreshed
automaticaly which causes problems on various places including the UI
problems similar to that you've described. Unfortunately we aren't
able to do anything in projects to improve this situation.

The situation is even worse because the Refresh All Filesystems action
was removed from main menu for Netbeans 4.0 (CCing jmzourek).

The only workaround I am aware of is to go to the folder where you
created files and use the Refresh action, your files should then
become visible to Netbeans.
Comment 2 rmatous 2003-04-15 15:14:03 UTC
I understand that this issue may be problem for you. But be sure, that
I definitely don't think this is worth of P1 priority. 

Vita described the cause of this problem. I see 
3 possible solutions:
1/ periodical refresh - rejected because of performance
2/ native support - not widely accepted idea because of JNI need
3/ user action - see Vita's comment (depends on UI design)

From my point of view - WONTFIX for filesystems at the moment as DEFECT.
Comment 3 Jan Becicka 2003-04-15 15:24:16 UTC
Hey, you must be joking! I described very common use case, right?
AFAIK Filesystems tab will removed, right? So there is no workaround.
Comment 4 Jiri Mzourek 2003-04-24 15:04:44 UTC
I agree that this is a valid issue. What we saw in the usability study
this week -- participants had a problems with it (when they touched
the files by external tools). We should address this problem somehow
for release after NB3.5.
Comment 5 Jan Becicka 2003-05-21 10:18:32 UTC
*** Issue 33602 has been marked as a duplicate of this issue. ***
Comment 6 _ pkuzel 2003-10-21 17:10:44 UTC
I see another possible solution:

4/ instrument several FileObject methods so they will as side effect
perform a part of the refresh. It'll also perfectly emulate the
nondeterministics behaviour of asynchronous refresh thread.
Comment 7 _ pkuzel 2003-10-21 17:17:06 UTC
Some competitive IDEs use yet another technique:

5/ synchronize state on IDE window activation. Unfortunatelly it
obstructs user as it's commonly done in synchronous manner showing a
progress dialog.
Comment 8 Marian Mirilovic 2003-12-22 13:41:43 UTC
As described in
http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss
the
current work on projects prototype has been stopped.

This issue should be closed or tracked as non Projects issues.

removed PROJECTS keyword.
Comment 9 jrojcek 2004-01-17 15:14:46 UTC
The current dev build provides multiple ways how to manually refresh filesystem: 

- File|Refresh All Filesystems main menu action
- Refresh All contextual menu action on Filesystems node
- Refresh menu action on individual filesystem nodes and folders

The automatic refresh of filesystems was turned off due to performance reasons. I 
agree that it would be great to do it automatically, but perfomance penalty is 
unacceptable (AFAIK). Marking as won't fix.
Comment 10 pzajac 2004-02-25 14:52:29 UTC
verified wontfix