Re: [tasklist] compiler module feedback
Tor Norbye <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.tasklist.devel |
|---|---|
| Organization | Sun Microsystems, Inc |
| Message-ID | <1049173146.5910.112.camel@proto> |
I realized I overlooked this message a while ago: On Thu, 2003-03-13 at 06:28, Tim Lebedkov wrote: > From: "Tor Norbye" <[email protected]> > > On Tue, 2003-03-11 at 02:03, Tim Lebedkov wrote: > > > What about the TL API enhancements? > > > > I'm sorry -- what are you referring to here? > > We need a public API for OutputTab replacement. > > the API could be very simple: > > public class ProcessMessage { > CompileTask currently has following attributes: > -severity > -line > -column > -FileObject > -priority??? (or maybe is severity enough?) > -type > -summary > -details > -suggestions??? (or maybe SystemAction[] getActions()) > Annotation createAnnotation(); > } > > public class ProcessMessageView { > public static ProcessMessageView create(String name); > public void add(ProcessMessage msg); > public void clear(); > public void setVisible(boolean v); > } > > Two things are not clear to me now: > - whether the attributes of ProcessMessage would satisfy all future needs. > - would anybody use this API if it depends on TL/core? I'm still a little lost. Who is the provider and who is the client of this API? Is the intent to provide a "general" API that the NetBeans output engine should use, such that one could plug something like the buildmsg module in as a replacement without having to duplicate the code and use layer masking etc.? Or, are you referring to fact that there is no way to use the tasklist API (tasklist-api.jar, not tasklist-core.jar) to create a new Tasklist Tab? I've thought of that (since there are potential other uses too, e.g. as an output device for PMD, as an output device for ant, etc.) I think that API should have nothing compiler-specific in it. I was thinking that the new "request" parameter which I added to the SuggestionManager API (for other reasons, probably documented in the javadoc or the code) might do the trick. Using some (to be added) method like "createView", which returns a handle, the handle can then be used by SuggestionManager.register to direct task registrations to the correct view. I guess both of my remarks might be off since I don't quite fully understand which problem you're addressing here. -- Tor