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.
| Summary: |
Create Lookup.Provider interface |
| Product: |
platform
|
Reporter: |
Jaroslav Tulach <jtulach> |
| Component: |
Lookup | Assignee: |
David Strupl <dstrupl> |
| Status: |
RESOLVED
FIXED
|
|
|
| Severity: |
blocker
|
CC: |
dsimonek, jglick, jpokorsky
|
| Priority: |
P2
|
Keywords: |
API |
| Version: |
3.x | |
|
| Hardware: |
PC | |
|
| OS: |
Linux | |
|
|
Issue Type:
|
ENHANCEMENT
|
Exception Reporter:
|
|
|---|
| Bug Depends on: |
|
|
|
| Bug Blocks: |
26076, 26617
|
|
|
In various situations there seems to a need to find out whether an object is Lookupable or not. This is not needed for our own classes where we can always add getLookup method, but for example if we want to check if a component is Lookupable, then a interface interface Lookup.Provider { public Lookup getLookup (); } could be very handy. I suggest to create such interface. It should be needed by actions redesign done by Dafe and possibly by settings enhancements being worked on by Honza. There already was a discussion about this on nbdev: http://www.netbeans.org/servlets/ReadMsg?msgId=329118&listName=nbdev