[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ui-dev] Startup performance / Lazy creation of editors.
|
The real problem is Editor bloat. Solve that problem first, then look at
performance. I never wanted all of those windows open to begin with, but
the weak editor management means I have to have set my "reuse threshold"
too high.
The "Number of Open Editors before closing" preference should only apply to
*clean* editors. I personally would then set this number to ONE, and I
would have VA-Java++. The exception being that if the current Editor is
dirty, I can open up another Editor along with the first.
|---------+--------------------------------->
| | Jared Burns |
| | <jared-eclipse@xxxxx.c|
| | om> |
| | Sent by: |
| | platform-ui-dev-admin@|
| | eclipse.org |
| | |
| | |
| | 04/30/2002 04:48 PM |
| | Please respond to |
| | platform-ui-dev |
| | |
|---------+--------------------------------->
>------------------------------------------------------------------------------------------------------------|
| |
| To: platform-ui-dev@xxxxxxxxxxx |
| cc: |
| Subject: 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
_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev
