Community
Participate
Working Groups
CompilationUnitEditor is marked as Internal api so its mostly undocumented and I'm not allowed to instantiate it directly. However, if a plugin writer has the need/desire to put the Java editor inside a MultiPageEditor (for example in a Java code documentation plugin), it is necessary to create an instance of CompilationUnitEditor as a page of the MultiPageEditor. I think either of the following would resolve the issue (there may be other resolutions I haven't thought of): 1) CompilationUnitEditor to be minimally documented--enough so it can be instantiated in another plugin. 2) A JavaMultiPageEditor component that isn't internal API but that uses CompilationUnitEditor could be published. Then I could use non-internal API and get what I want while CompilationUnitEditor could remain internal.
There will be improvements as part of the code moves to Platform Text, but the rest is rather unlikely to happen.
>>There will be improvements as part of the code moves to Platform Text, but the rest is rather unlikely to happen.<< I'm not sure I understand this. Are you saying that enough of the API will be moved to Platform Text that I will be able to do what I need to do? Thanks, Dave
