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 19871 - need API for hiding JEditorPane of file being edited externally
Summary: need API for hiding JEditorPane of file being edited externally
Status: RESOLVED INVALID
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 3.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: mslama
URL: http://openide.netbeans.org/source/br...
Keywords: API
Depends on: 41291
Blocks:
  Show dependency tree
 
Reported: 2002-01-29 00:13 UTC by David Weatherford
Modified: 2009-02-27 17:16 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Weatherford 2002-01-29 00:13:50 UTC
The externaleditor module requires the ability to hide the JEditorPane
associated with a file which is being edited externally.  This would
provide better coexistence with the built-in Source Editor (see issue
17398).

Suggested implementation:  Add a property to the DataObject that controls
the visibility of its editor pane.  The ExtEdKit could set this property
at install() time, and the Source Editor would check the property before
showing the pane for the file.  If the ExtEdKit is uninstalled for the
MIME type of the file, it would reset the property so that subsequent
Opens would show the pane as expected.

Requested for NB 3.4.
Comment 1 Miloslav Metelka 2002-01-30 08:53:13 UTC
I cannot handle this in the editor module. This is rather for openide
or core. Reassigning to openide.
Comment 2 _ ttran 2002-01-30 09:33:58 UTC
No chance to do it for 3.3.x series.  This is an RFE, not a bug.  It
requires API changes, I marked this issue with API keyword to indicate
this fact.

Will put high prio on this issue for 3.4
Comment 3 Jaroslav Tulach 2002-01-30 12:57:15 UTC
Adding property to DataObject is not good solution - DO should be
separate from editor.

We should improve CloneableEditorSupport to find out that the Document
is standalone (NbDocument.CustomEditor returning something special)
and not open any CloneableEditors...

Comment 4 Jesse Glick 2002-01-30 13:17:36 UTC
I did start work on such an API in the past. It is old but the basic
ideas could be revisited to see if they are still useful.

The API involves an optional interface in NbDocument permitting
documents from an editor kit to mark themselves as invisible or
somehow special. In that case a CloneableEditor (or equiv.) is still
created, for API compatibility purposes, but never made visible.
Comment 5 Marek Grummich 2002-07-22 11:22:45 UTC
Set target milestone to TBD
Comment 6 Marek Grummich 2002-07-22 11:24:53 UTC
Set target milestone to TBD
Comment 7 Jaroslav Tulach 2004-01-28 13:49:37 UTC
I am not sure, but I think that this might be duplicate or very
similar to issue 20910. As that issue is fixed for long time, I am
curious whether this issues is not fixed as well. Closing as
duplicate, if still necessary, reopen.

*** This issue has been marked as a duplicate of 20910 ***
Comment 8 _ gordonp 2004-01-28 14:35:25 UTC
This is a very different issue than 20910. That issue was in regards
to vetoing an open in the IDE of a file which was already open in
the external editor.

This issue deals with removing the redundancy of having a tab in the
otherwise empty source editor as well as having the file opened in
the external editor.

Right now, if I'm editing with gvim (or xemacs) and have 5 source
files open, I've got 5 tabs in the NB editor. This issue deals with
being able to suppress those, not with vetoing any opens.
Comment 9 Jaroslav Tulach 2004-04-07 12:07:38 UTC
Seems to me that the patch in issue 41291:
http://www.netbeans.org/issues/showattachment.cgi?attach_id=14259
if modified to support null component, might solve this issue as well.
Comment 10 Antonin Nebuzelsky 2008-04-17 15:16:03 UTC
Reassigning to new module owner mslama.
Comment 11 _ gordonp 2009-02-27 17:16:14 UTC
The externaleditor module has been unsupported since the NetBeans 3.5 release. So the original reason
this issue was opened is no longer a requirement. Unless someone has another reason unrelated to the
original reason, this issue should be closed.