| VisualEditor very slow, etc. [message #74769] |
Tue, 14 December 2004 04:01  |
Eclipse User |
|
|
|
Originally posted by: mik.c-l-a-s-s-x.it
We're working with the VisualEditor since a month after migrating all our
soruce code base from VisualAge for Java. We develop Swing based desktop
applications so the visual gui building is an important phase of our
development cycle.
I find the VisualEditor very slow even on a high-end machines and I think
the main problem of VE is the slowness of the gui rebuilding, which is a
real pain, even when working with a limited number of components.
Also the gui rebuilding itself is done very frequently due to property
changes (visual) or source code changes.
Some ideas:
1 - why don't you separate the source code update from the gui editing ? We
could, for example, build and modify a gui at full speed and ask for a code
regeneration at the end of the gui editing. User code would be kept intact
in case of further gui editing.
2 - Leave things unchanged but speedup the gui rebuilding as much as you can
by avoiding the source code parsing phase (making use of metadata i.e. for
the classes directly generated inside VE).
3 - Leave things unchanged but speedup the gui rebuilding as much as you can
by pre-parsing the source code (making use of metadata) and then displaying
the gui (this avoids a huge lot of unneded repaints).
Mik
p.s.
there's a little annoying bug in the VE: changing a property of a component
unselects it.
--
============================================================ ================
> ClassX Development Italy Via Francesca, 368/I I-56030 S.M. a Monte (PI) <
> Tel.(+39)-0587-705153 Fax.(+39)-0587-705153 WEB: http://www.classx.it <
============================================================ ================
|
|
|
|
|
|
|
|
| Re: VisualEditor very slow, etc. [message #603877 is a reply to message #74769] |
Tue, 14 December 2004 05:26  |
| Eclipse User |
|
|
|
One temporary solution you may or may not have already noticed: when
editing the sourcecode by hand, you can pause GUI repainting ('pause'
button on the toolbar) until you're ready to see it again. (I think this
was more noticeable in 2.x.) This allows you to handwrite sourcecode
without being burdened by constant repainting, but doesn't allow you to
see your changes or make changes through the VE itself.
Michele Puccini wrote:
> We're working with the VisualEditor since a month after migrating all our
> soruce code base from VisualAge for Java. We develop Swing based desktop
> applications so the visual gui building is an important phase of our
> development cycle.
>
> I find the VisualEditor very slow even on a high-end machines and I think
> the main problem of VE is the slowness of the gui rebuilding, which is a
> real pain, even when working with a limited number of components.
> Also the gui rebuilding itself is done very frequently due to property
> changes (visual) or source code changes.
>
> Some ideas:
>
> 1 - why don't you separate the source code update from the gui editing ? We
> could, for example, build and modify a gui at full speed and ask for a code
> regeneration at the end of the gui editing. User code would be kept intact
> in case of further gui editing.
>
> 2 - Leave things unchanged but speedup the gui rebuilding as much as you can
> by avoiding the source code parsing phase (making use of metadata i.e. for
> the classes directly generated inside VE).
>
> 3 - Leave things unchanged but speedup the gui rebuilding as much as you can
> by pre-parsing the source code (making use of metadata) and then displaying
> the gui (this avoids a huge lot of unneded repaints).
>
> Mik
>
> p.s.
> there's a little annoying bug in the VE: changing a property of a component
> unselects it.
>
--
Liam Morley
Computer Science Undergraduate
Worcester Polytechnic Institute
|
|
|
| Re: VisualEditor very slow, etc. [message #603902 is a reply to message #74786] |
Tue, 14 December 2004 12:01 |
| Eclipse User |
|
|
|
Well said, it's just a temporary solution.
I would like to hear the position of the VEP developers.
Mik
--
============================================================ ================
> ClassX Development Italy Via Francesca, 368/I I-56030 S.M. a Monte (PI) <
> Tel.(+39)-0587-705153 Fax.(+39)-0587-705153 WEB: http://www.classx.it <
============================================================ ================
"Liam Morley" <lmorley@wpi.edu> ha scritto nel messaggio
news:cpmf4d$of1$1@www.eclipse.org...
> One temporary solution you may or may not have already noticed: when
> editing the sourcecode by hand, you can pause GUI repainting ('pause'
> button on the toolbar) until you're ready to see it again. (I think this
> was more noticeable in 2.x.) This allows you to handwrite sourcecode
> without being burdened by constant repainting, but doesn't allow you to
> see your changes or make changes through the VE itself.
|
|
|
|
| Re: VisualEditor very slow, etc. [message #603920 is a reply to message #75023] |
Wed, 15 December 2004 03:12 |
| Eclipse User |
|
|
|
Which direction are you taking in order to speedup VE ?
Mik
--
============================================================ ================
> ClassX Development Italy Via Francesca, 368/I I-56030 S.M. a Monte (PI) <
> Tel.(+39)-0587-705153 Fax.(+39)-0587-705153 WEB: http://www.classx.it <
============================================================ ================
"Rich Kulp" <richkulp@us.NO_SPAM.ibm.com> ha scritto nel messaggio
news:cpn7ev$ars$1@www.eclipse.org...
> WE are working on performance. That is the number one thing for the next
> release.
>
> --
> Thanks,
> Rich Kulp
|
|
|
|
Powered by
FUDForum. Page generated in 0.04548 seconds
Home