Re: Java Project API/SPI
Svatopluk Dedic <[email protected]> Thu, 24 Jul 2003 07:43:17 +0200
| Newsgroups | gmane.comp.java.netbeans.modules.projects.devel |
|---|---|
| Message-ID | <[email protected]> |
Jan Pokorsky wrote: > If you look at the natures owerview > http://www.netbeans.org/download/prj40_prototype/javadoc/ProjectsCoreAPIs/org/netbeans/api/projects/doc-files/natures.html#Natures > you can find following definitions: > > * natures provide a mechanism for registering extensions to a project in > a declarative form > * a project nature is a XML file > * it has a unique name and a version > * ... > > I do not think the JavaProject accomplishes them. Sorry, that I am not > constructive but I am not able to bring up any better name. > <IMHO> A "nature" is more like "flavour"; the term is quite generic and broad as it may include registration, services, templates, wizards, actions, ... Some natures may even go without some JavaProject analogy, I think. JavaProject is just one component of Java nature - it is (or was creates as) a organization model of project contents suited to java processing. </IMHO> Another name could be JavaProjectPart so the name suggest it is just a part of a larger entity, Then we would have Project and then *ProjectPart - models of nature-specific organizations (c.f. Eclipse: Workbench vs. WorkbenchPart). -Svata