Kind of yucky--e.g. putting ContextTreeView w/ PropertySheetView will
not work, because they have different ideas of what selected vs.
context nodes should be for.
Also PropertyPanel should be supported nicely, somehow.
If you need a volunteer, I can help a bit.
Sure, if you like. I think we need a new template category in
apisupport, "Explorer API", with a panel template (incl. .form file);
and palette beans for common views and I guess also PropertyPanel,
which might need some special property editors for its stuff (not clear).
Target milestone was changed from '3.4' to TBD.
*** Issue 31660 has been marked as a duplicate of this issue. ***
*** Bug 153627 has been marked as a duplicate of this bug. ***
*** Bug 57644 has been marked as a duplicate of this bug. ***
Here are the Explorer API components I would find really useful to have on the palette:
FWIW, this would be trivial to do in an external module.
(In reply to comment #8)
> FWIW, this would be trivial to do in an external module.
Agreed. But with very little effort it could be a good addition to the IDE itself. It would improve usability and visibility of these very powerful components.
Votes + duplicates > 10. Marking as P2. :)
+1: It would be useful.
Should be easy. You could even add them manually - see http://netbeansrcp.wordpress.com/2009/04/01/adding-explorer-components-into-the-netbeans-palette/