I suggest to add access to editor of EditableContent. E.g. add
something like this:

java.awt.Component getEditor ();

into EditableContent.EditorNode

another option would be to use getNode().getCustomizer() if it returns
the right editor (if so can this be documented?)

What about changing EditableContent.createNode to 

java.awt.Component createEditor() ?

It was originally like that, but then it seemed too coupled to me. But
now I see that creating just the node is useless (nobody would ever
implement other editor reusing the node) and coupled as well.

So I think it would be simple and functional to return directly the
panel you could put into your property editor or whereever you wish.

What do you think?

ok, I did not understand that the node retured from getNode in
EditorNode is the root node in editor. If it is so then I agree with
your solution -- getNode() should not be needed.

BTW: should not the content editor be used in customizer of build
target? What about poutting it into a separate tab called "Content".

Its finished.

RE "..customizer...": yes, of course. It's just not done yet.

Re: RE "..customizer...": 

when you try this you will find that it is not sufficient to return
java.awt.Component from createEditor(). To add a customizer panel you
need to implement a TemplateWizard.Iterator. You should apply changes
in instantiate() method, not immediately from the UI (see the
documentation in projects/ide about "Build Target Wizard and Customizer").
I suggest to change the createEditor method to createCustomizer:

public TemplateWizard.Iterator createCustomizer (Configuration c) {..}

As Ondrej pointed to me offline the recomended way is to clone the
ProjectContent, use it in customizer and set it back in instantiate().
How simple.

verified - it works

closing all my verified issues