[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Startup performance / Lazy creation of editors.
|
It sounds like this will completely break my editor management view. The view
displays the currently open editors as returned by
IWorkbenchPage.getEditors(). I don't see how I can find out which editors are
open if the getEditors() API is removed.
It strikes me as a fundamentally bad idea for the Eclipse platform to not
provide access to the open editors. Maybe I'm missing something here, but it
seems like we have a performance problem that we're just trying to avoid by
removing functionality. The correct solution here should be to improve the
implementation of EditorPart and the code that restores the editors on
startup.
Why is it so expensive to restore a workbench with 50 editors open? Are we
opening them serially and processing each editor creation to the fullest?
Things like block operations and lazy initialization should solve this
problem - without having to eliminate API.
- Jared
