|
From: Thelmo L. <the...@em...> - 2003-12-04 18:24:08
|
On Thu, 2003-12-04 at 17:19, Robert Fletcher wrote: > The thing is that JavaCore doesn't store the information itself. It provides > a framework to link any provider of the information with any consumer of the > information. Okay, it does provide a default provider implementation, but > it's pretty basic & most people would probably rather use a more > project-centric implementation. I can take your point here > But it's a question of usage. You don't need all the source for the various > libs. Classpath & sourcepath basically provide you with a sort of extended > reflection framework, answering questions like "does class x exist?", "what > are the classes in package y?", "what are the methods of class z?". That's > the kind of thing needed by code completion, import checking, skeleton code > generation, etc. In those scenarios the only source code you really need is > your own & you only need that for classes you haven't compiled yet or that > have changed since the last compile. Docs would, presumably, be used for > interactive help, etc. and unlike classpath/sourcepath are unlikely to be > physically located in a project-centric way (other than the very specific > docs for the project classes). Providing docpath info is easy & logical for > something like the default service in JavaCore where nothing is > project-centric anyway. It's more difficult for something like AntHelper > that has no business knowing anything about where the docs for commons-* > live, for example. Here my approach is slightly different since from my point of view a good code completion should carry hint from the javadoc of the current selected method or from the source it's providing completion (like CodeAid does). This feature could be done by providing javadocs or (better) source code. And i would like this feature also for the libs i'm working with, have you came across libs with the same method name/signature !? Maybe i'm too lazy, but by habit is to work with a lot of libs on different projects and that's turn to be very useful addon. I'm totally with you when you say 'docpath is not so project-centric', this is the reason why i suggest to make JavaCore become a self producer for docpath, and provide to others docpath in a standard manner (like classpath or sourcepath). So maybe default service implementation in JavaCore could do this work, or better a class that extend the default implentation. -- Thelmo |