| Accelerating Eclipse VE [message #34180] |
Fri, 30 April 2004 17:54  |
Eclipse User |
|
|
|
Originally posted by: list.eclipse.newgenesys.com
When building a swing GUI, VE opens 2 more windows. I noticed that
SWT-designer is opening one also. Why is that? How can I prevent that? Is
that slowing down the designer?
Right now building a swing GUI is too slow on my machine (Celeron 1.7GHz
with 1GB RAM, Linux 2.4.26, KE 3.1). How can I fasten the process?
Thanks in advance
Pascal
|
|
|
| Re: Accelerating Eclipse VE [message #34383 is a reply to message #34180] |
Mon, 03 May 2004 09:38  |
| Eclipse User |
|
|
|
Originally posted by: mendelgili.netscape.net
Pascal Demilly wrote:
> When building a swing GUI, VE opens 2 more windows. I noticed that
> SWT-designer is opening one also. Why is that? How can I prevent that? Is
> that slowing down the designer?
When you drop a top level window (e.g., JFrame) the editor will
instantiate the window so that it could be screen scraped, and in order
to introspect it. On the windows platform that will be noted as a
"Window" ... even though VE draws it off screen.
Since VE is running on a target VM and screen scrapes the image (it does
not drop the windows inside the IDE)... we were thinking of making the
window "visual" only when we need to screen scrape ... which will cause
the windows on the task bar to "flicker" when scrapping is required. In
this case, the windows would not apear on your task bar. The extra
window that VE has, is the target VM's main top level window.
>
> Right now building a swing GUI is too slow on my machine (Celeron 1.7GHz
> with 1GB RAM, Linux 2.4.26, KE 3.1). How can I fasten the process?
>
Can be helpful if you be more specific... is it when dropping
components, changing layouts, writing in the source viewer
> Thanks in advance
>
> Pascal
|
|
|
| Re: Accelerating Eclipse VE [message #34485 is a reply to message #34383] |
Mon, 03 May 2004 09:55 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
One thing you can try is when you start your Eclipse to use
-vmargs -Xmx256M
This is the standard way to increase the java heap size. The default
java heap size is too small for most Eclipse work. It doesn't matter how
big your machine is, Java will use whatever size heap is given to it,
even if there is more memory available.
--
Thanks, Rich Kulp
|
|
|
| Re: Accelerating Eclipse VE [message #587671 is a reply to message #34180] |
Mon, 03 May 2004 09:38 |
| Eclipse User |
|
|
|
Pascal Demilly wrote:
> When building a swing GUI, VE opens 2 more windows. I noticed that
> SWT-designer is opening one also. Why is that? How can I prevent that? Is
> that slowing down the designer?
When you drop a top level window (e.g., JFrame) the editor will
instantiate the window so that it could be screen scraped, and in order
to introspect it. On the windows platform that will be noted as a
"Window" ... even though VE draws it off screen.
Since VE is running on a target VM and screen scrapes the image (it does
not drop the windows inside the IDE)... we were thinking of making the
window "visual" only when we need to screen scrape ... which will cause
the windows on the task bar to "flicker" when scrapping is required. In
this case, the windows would not apear on your task bar. The extra
window that VE has, is the target VM's main top level window.
>
> Right now building a swing GUI is too slow on my machine (Celeron 1.7GHz
> with 1GB RAM, Linux 2.4.26, KE 3.1). How can I fasten the process?
>
Can be helpful if you be more specific... is it when dropping
components, changing layouts, writing in the source viewer
> Thanks in advance
>
> Pascal
|
|
|
| Re: Accelerating Eclipse VE [message #587705 is a reply to message #34383] |
Mon, 03 May 2004 09:55 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
One thing you can try is when you start your Eclipse to use
-vmargs -Xmx256M
This is the standard way to increase the java heap size. The default
java heap size is too small for most Eclipse work. It doesn't matter how
big your machine is, Java will use whatever size heap is given to it,
even if there is more memory available.
--
Thanks, Rich Kulp
|
|
|
Powered by
FUDForum. Page generated in 0.03099 seconds
Home