Re: Re: project conversion questions

 > Does your code's execution start with a knowledge of a Node ? If so,
 > then you could use Node.getLookup().lookup(ProjectMember).

No, not always, but maybe I need to change this. There are various
ways in which I am bound to the Java object I'm annotating

- the editor context menu

- the node actions

- the node filter factory (now obsolete, need to convert to looks)

The module I have is built on the Java module -- it has no data
objects of its own. It has to access the source element to manipulate
the class, it needs access to the project member to launch the source
editor, it needs access to the fileobject to locate the source
directory to generate any side files that might be needed, and it
needs access to the Java node to add different look nodes. So the set
{SourceElement, FileObject, ProjectMember, Node} constitute a logical
object that I need to navigate easily and efficiently, hopefully
without having to know details of the implementation. In the past I
didn't have to think too carefully about where things got started
since I could always get from each object to each other object. I had
figured out how to do these navigations in the 3.5 world, but lots of
things have now changed.

Peter