Bug 115110 - DataObjectTopComponent
DataObjectTopComponent
Status: NEW
Product: platform
Classification: Unclassified
Component: -- Other --
5.x
All All
: P3 (vote)
: TBD
Assigned To: issues@platform
issues@platform
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-09-09 18:18 UTC by Tim Lebedkov
Modified: 2009-01-06 14:37 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Lebedkov 2007-09-09 18:18:08 UTC
Hi,

I have implemented a module that recognizes a file as of special type (not text) and
shows a TC when the file is opened.

I find it was too much work for such a common case (maybe I do something wrong):
- extend TC
- override getPersistenceType
- listen to changes in the DO and update Title/Tooltip
- create ExplorerManager, implement ExplorerManager.Provider, set DataObject.getDelegateNode() 
  as selected node
- associate lookup with the node
- readExternal/writeExternal to store/load the file being edited
- override canClose()

I think that the case is very common and there must be a "DataObjectTopComponent" for
easy implementation.

Are You of the same opinion?


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo