Tasklist SPIs
Petr Kuzel <[email protected]> Sat, 08 Nov 2003 22:59:16 +0100
| Newsgroups | gmane.comp.java.netbeans.modules.tasklist.devel |
|---|---|
| Organization | Sun Microsystems |
| Message-ID | <[email protected]> |
Hello,
I'd like to do incompatible API change.
DocumentSuggestionProvider has several abstract
methods taking DataObject and Document arguments.
Looking around code most providers need String
of FileObject. If no objections I'll replace
these by one wrapper object:
/**
* @deprecated Experimental SPI
*/
public final class SuggestionContext {
// package private constructor accessible by framework
/** Returns in-memory representation */
public CharSequence getCharSequence();
/** Return fs level representation */
public FileObject getFileObject();
}
Moreover I need to figure out actual API stability level.
I wish friend stability level answer :-). Then I plan to
mark all APIs as @deprecated with experimental note.
Another issue, I'm confused about API packaging. It's
in ....tasklist.api package but it should be in
...taslist.spi package (framework calls to it).
I'm willing to commit above changes if nobody objects.
Cc.