You’re really not going to have an easy time doing that. You’re asking to break the encapsulation of what modules are expected to be able to do. Within the designer, it would theoretically be possible - from the
DesignerContext, you can
getProjectBrowserRoot. You’ll then have to (recursively) walk its children, find which node(s) represent resources (ie, inherit from AbstractResourceNavTreeNode) and then extend their popup menu. Because your custom menu item(s) won’t be registered, they won’t be populated with the contextual information I mentioned, so figuring out the resource information might be tricky.