Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Visual Editor (VE) » VE development problem
VE development problem [message #103974] Fri, 26 August 2005 23:01 Go to next message
hanys is currently offline hanysFriend
Messages: 188
Registered: July 2009
Senior Member
Hi all,

I'm using VE 1.1.0.
Here are simple list of problems which I found:

1. At Runtime-Workbench I must close all editors and clean all projects to
REFRESH BEAN INFOs. Sometimes I have to change the JAVA file before I may
do the project cleaning. The beaninfo cache may be old, even if the
CLASSPATH CONTAINER JAR FILE CONTAINS NEW BEANINFO VERSION.

2. When I'm developing new palette with components the palette will not
show immediately when is CLASPATH CONTAINER INSERTED INTO THE TARGET
PROJECT!!!
The palette will show for next random period of TIME!!!! From that point
the palete is shown all the time.

3. The development is somethink hard when there are more VMs. This is only
the tip for development improvement.

John Cage

Report message to a moderator

Re: VE development problem [message #104113 is a reply to message #103974] Mon, 29 August 2005 13:26 Go to previous message
Gili Mendel is currently offline Gili MendelFriend
Messages: 338
Registered: July 2009
Senior Member
John Cage wrote:
> Hi all,
>
> I'm using VE 1.1.0.
> Here are simple list of problems which I found:
>
> 1. At Runtime-Workbench I must close all editors and clean all projects
> to REFRESH BEAN INFOs. Sometimes I have to change the JAVA file before I
> may do the project cleaning. The beaninfo cache may be old, even if the
> CLASSPATH CONTAINER JAR FILE CONTAINS NEW BEANINFO VERSION.
>

Changed BeanInfo is not a typical scenario; VE does not expect this to be changed
at this time... so you will have to "clean" to clear the cache.

> 2. When I'm developing new palette with components the palette will not
> show immediately when is CLASPATH CONTAINER INSERTED INTO THE TARGET
> PROJECT!!!
> The palette will show for next random period of TIME!!!! From that point
> the palete is shown all the time.
>

VE creates a "spare" VM when it opens an editor and keeps it around for 5min or so (in the case that no VE editors are
up). This VM will speed up the opening of an editor the next go around. ... the problem is that this VM will have the
classpath that was set on its creation time. If the class path was changed, VE should recycle All VMs (for open
editors, including the spare). .. if it does not it is a bug.

> 3. The development is somethink hard when there are more VMs. This is
> only the tip for development improvement.
>

Yes... debugging the target VM is a bit indirect (have to connect another debugger to the target); target VM has many
draw backs, but also many merits at the same time. Something we continuesly struggle with.

> John Cage
>
>

Report message to a moderator

Re: VE development problem [message #610426 is a reply to message #103974] Mon, 29 August 2005 13:26 Go to previous message
Gili Mendel is currently offline Gili MendelFriend
Messages: 338
Registered: July 2009
Senior Member
John Cage wrote:
> Hi all,
>
> I'm using VE 1.1.0.
> Here are simple list of problems which I found:
>
> 1. At Runtime-Workbench I must close all editors and clean all projects
> to REFRESH BEAN INFOs. Sometimes I have to change the JAVA file before I
> may do the project cleaning. The beaninfo cache may be old, even if the
> CLASSPATH CONTAINER JAR FILE CONTAINS NEW BEANINFO VERSION.
>

Changed BeanInfo is not a typical scenario; VE does not expect this to be changed
at this time... so you will have to "clean" to clear the cache.

> 2. When I'm developing new palette with components the palette will not
> show immediately when is CLASPATH CONTAINER INSERTED INTO THE TARGET
> PROJECT!!!
> The palette will show for next random period of TIME!!!! From that point
> the palete is shown all the time.
>

VE creates a "spare" VM when it opens an editor and keeps it around for 5min or so (in the case that no VE editors are
up). This VM will speed up the opening of an editor the next go around. ... the problem is that this VM will have the
classpath that was set on its creation time. If the class path was changed, VE should recycle All VMs (for open
editors, including the spare). .. if it does not it is a bug.

> 3. The development is somethink hard when there are more VMs. This is
> only the tip for development improvement.
>

Yes... debugging the target VM is a bit indirect (have to connect another debugger to the target); target VM has many
draw backs, but also many merits at the same time. Something we continuesly struggle with.

> John Cage
>
>

Report message to a moderator

Previous Topic:View in VE is wrong after upgrade to 1.1
Next Topic:problem to debug VE into eclipse 3.1.0 ?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Wed Apr 24 17:58:50 GMT 2024

Powered by FUDForum. Page generated in 0.03796 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top

Sign up to our Newsletter

A fresh new issue delivered monthly