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 35586 - Temporary editor
Summary: Temporary editor
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Roman Ondruska
: 15772 (view as bug list)
Depends on: 90395 94607
Blocks: 89617
  Show dependency tree
Reported: 2003-08-21 10:51 UTC by mvinar
Modified: 2010-04-29 09:14 UTC (History)
3 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description mvinar 2003-08-21 10:51:49 UTC
User problem:
The user typically navigates through a lot of
classes during the debugging, which are only "on
the way" to the target, but they remain open after
the debugging session finishes and need to be
explicitly closed

User need:
The user wants to look at certain sources only
temporarily, and the IDE can be smart enough to
figure out what to close automatically.

Product requirement:
Implement temporary editor (editor which is reused
for traversing of opene
d files during debugging and navigation (Goto
Class?)), alternatively implement AutoClose of
documents opened during debugging when the
debugger session finishes.
Comment 1 Jan Jancura 2004-09-02 09:19:53 UTC
I agree with this RFE and I plan to implement it for the next release.
Comment 2 Roman Ondruska 2005-05-12 16:05:52 UTC
In NB-plan #1028
Comment 3 _ lcincura 2005-05-12 18:05:55 UTC
*** Issue 15772 has been marked as a duplicate of this issue. ***
Comment 4 clever 2006-03-21 15:03:46 UTC
I think this is a good idea.. However, I think the request can be expanded into
something even bigger. The 'temporary editor' seems like a neat idea, but
perhaps we can identify the underlying requirement.. see how it applies to the
entire IDE, and gracefully implement a good solution starting with the editor
and debugging..

I'd like to see this approached from a usability perspective. This is a stab:
- Recognize that the user has differnt levels of 'interest' in a file or object
- Recognize that a user has different "modes" (ala 'perspectives') by which they
are using the IDE. For example, {editing, running, and debugging}. Each
operating mode would allow for a different IDE "behavior model".
- Formalize a 'behavior model' to allow views and windows to auto-close in a
customizable and intelligent fashion

And, it seems that the solution proposed here makes the assumption that a
'temporary editor' is the best way to manage the introspection and viewing of
source code for the 'current context'. Is this up for debate? Perhaps something
like a "Source Explorer".. or "Context Explorer":)

I think this (and other related RFE's) are going to give the NBDev team an
opportunity to run circles around the other IDE's... if the cards are played
right.  Just for fun, I'd like to mention that I appreciate the "Perspective"
feature of Eclipse.. however, it's far from user friendly and feels 'kludgy'.
Comment 5 Marian Petras 2006-03-21 15:22:56 UTC
There is a pretty intensive discussion about this topic on the NB UI mailing
list - for introduction, see the first e-mail sent by David Strupl
Comment 6 _ tboudreau 2006-06-16 17:27:12 UTC
A minor suggestion:  Probably any files the user *edits* while debugging should remain open after the 
debugger session stops.
Comment 7 Martin Entlicher 2007-03-15 10:44:14 UTC
The editor panes are reused, when opening files from debugger.
It's fixed in trunk:

new revision: 1.11; previous revision: 1.10
Comment 8 Quality Engineering 2010-04-29 09:14:39 UTC
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.