Skip to main content



      Home
Home » Archived » Visual Editor (VE) » Parsing problems on Eclipse 3.2
Parsing problems on Eclipse 3.2 [message #131884] Fri, 06 October 2006 05:39 Go to next message
Eclipse UserFriend
Originally posted by: FunkyHippy.gmail.com

Hi

I use eclipse 3.1.2 along with Visual Editor 1.1.0.1 to produce the many
swing apps my company uses internally. I've recently tried to move to
eclipse 3.2 with VE 1.2.v20060530.RC2; however every project that
display fine in ve 1.1.0.1 will not display in 1.2 I get parse errors
for everything.

I am not along in this as a couple of colleagues have exactly the same
issue. Is there any incompatibilities moving between these versions?

As far as I can see its all just standard sing (the free version of
Cloudscapes Jigloo display them perfectly in 3.2).

I would attached any errors logs but I can't find any it just gives a
IWAV0181E Parse Error on screen.

Has anyone got any ideas?

tia
Re: Parsing problems on Eclipse 3.2 [message #131938 is a reply to message #131884] Fri, 06 October 2006 09:46 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Can you attach a simple class as an example that fails? OR can you send
it directly to me?

Jason Price wrote:
> Hi
>
> I use eclipse 3.1.2 along with Visual Editor 1.1.0.1 to produce the many
> swing apps my company uses internally. I've recently tried to move to
> eclipse 3.2 with VE 1.2.v20060530.RC2; however every project that
> display fine in ve 1.1.0.1 will not display in 1.2 I get parse errors
> for everything.
>
> I am not along in this as a couple of colleagues have exactly the same
> issue. Is there any incompatibilities moving between these versions?
>
> As far as I can see its all just standard sing (the free version of
> Cloudscapes Jigloo display them perfectly in 3.2).
>
> I would attached any errors logs but I can't find any it just gives a
> IWAV0181E Parse Error on screen.
>
> Has anyone got any ideas?
>
> tia

--
Thanks,
Rich Kulp
Re: Parsing problems on Eclipse 3.2 [message #132573 is a reply to message #131884] Fri, 27 October 2006 06:11 Go to previous messageGo to next message
Eclipse UserFriend
This question remaining unanswered I continue the thread. I get the error code IWAV0181E with a very simple class in VE:

package client.view.kehitysaikaiset;

import org.eclipse.swt.layout.GridLayout;
import org.eclipse.swt.graphics.Point;
import org.eclipse.swt.widgets.Composite;

public class Avaus extends Composite {
public Avaus(Composite parent, int style) {
super(parent, style);
initialize();
}

private void initialize() {
setSize(new Point(300, 200));
setLayout(new GridLayout());
}
}

But then, I'm convinced that this error code has nothing to do with my java source code -- the problem is that some Eclipse VE configuration file has become corrupt. But which?

Certainly EclipseVE functions normally if I reinstall it, but that's so awkward.

So the question is: How to straighten or reset Eclipse VE in a situation like this?
Re: Parsing problems on Eclipse 3.2 [message #132585 is a reply to message #131884] Fri, 27 October 2006 06:25 Go to previous message
Eclipse UserFriend
The answer to the question in my previous mail was here:

http://dev.eclipse.org/newslists/news.eclipse.tools.ve/msg05 163.html

I did 'Project - Clean all' and restarted Eclipse and now VE seems to be OK.
Re: Parsing problems on Eclipse 3.2 [message #614692 is a reply to message #131884] Fri, 06 October 2006 09:46 Go to previous message
Eclipse UserFriend
Originally posted by: richkulp.us.NO_SPAM.ibm.com

Can you attach a simple class as an example that fails? OR can you send
it directly to me?

Jason Price wrote:
> Hi
>
> I use eclipse 3.1.2 along with Visual Editor 1.1.0.1 to produce the many
> swing apps my company uses internally. I've recently tried to move to
> eclipse 3.2 with VE 1.2.v20060530.RC2; however every project that
> display fine in ve 1.1.0.1 will not display in 1.2 I get parse errors
> for everything.
>
> I am not along in this as a couple of colleagues have exactly the same
> issue. Is there any incompatibilities moving between these versions?
>
> As far as I can see its all just standard sing (the free version of
> Cloudscapes Jigloo display them perfectly in 3.2).
>
> I would attached any errors logs but I can't find any it just gives a
> IWAV0181E Parse Error on screen.
>
> Has anyone got any ideas?
>
> tia

--
Thanks,
Rich Kulp
Re: Parsing problems on Eclipse 3.2 [message #614737 is a reply to message #131884] Fri, 27 October 2006 06:11 Go to previous message
Eclipse UserFriend
This question remaining unanswered I continue the thread. I get the error code IWAV0181E with a very simple class in VE:

package client.view.kehitysaikaiset;

import org.eclipse.swt.layout.GridLayout;
import org.eclipse.swt.graphics.Point;
import org.eclipse.swt.widgets.Composite;

public class Avaus extends Composite {
public Avaus(Composite parent, int style) {
super(parent, style);
initialize();
}

private void initialize() {
setSize(new Point(300, 200));
setLayout(new GridLayout());
}
}

But then, I'm convinced that this error code has nothing to do with my java source code -- the problem is that some Eclipse VE configuration file has become corrupt. But which?

Certainly EclipseVE functions normally if I reinstall it, but that's so awkward.

So the question is: How to straighten or reset Eclipse VE in a situation like this?
Re: Parsing problems on Eclipse 3.2 [message #614738 is a reply to message #131884] Fri, 27 October 2006 06:25 Go to previous message
Eclipse UserFriend
The answer to the question in my previous mail was here:

http://dev.eclipse.org/newslists/news.eclipse.tools.ve/msg05 163.html

I did 'Project - Clean all' and restarted Eclipse and now VE seems to be OK.
Previous Topic:Cannot view subclassed form
Next Topic:Broken link in downloads page
Goto Forum:
  


Current Time: Sat Jun 21 07:08:23 EDT 2025

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

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

Back to the top