Home » Newcomers » Newcomers » Cannot Load Visual Editor
| Cannot Load Visual Editor [message #189252] |
Mon, 22 January 2007 03:16  |
Eclipse User |
|
|
|
Originally posted by: hal.thresholddigital.com
I've asked this on the eclipse.tools.ve group, but in my experience, answers
there are very slow, and I *have* to get the VE up and running ASAP. I am
blocked in all my work until it's back online, so I need a solution quickly
or I have to find another IDE. I'm not threatening, it's just gotten to
where I have to get it working ASAP or switch to something with a VE that I
can get working. Any help is appreciated!
I'm using Ubuntu Linux, Edgy upgraded from Dapper. I've installed Eclipse
3.2.1 from eclipse.org instead of using apt. I'm using Java 1.4.2 from
Sun, not any 3rd party version.
I had been using Eclipse 3.2 and I started running in to this problem, so I
created a clean install of 3.2.1, updated it, added the VE, made sure that
was updated as well, and I still have the same problem.
I've also tried installing Eclipse with apt-get. It's in a different
directory, so I have two different versions (and I've deleted /~/.eclipse
between tests). It doesn't do any good and I cannot install needed updates
because my window manager won't let me log in as root, I can't run Eclipse
from the console in X, as root, and have it open a window when X is run
under my own username. In other words, I get this problem with completely
different install and even with the newer Java 6 that I just installed.
Whenever I open an existing class or create a new one to edit in the VE, I
get a requestor telling me that it can't open the file in the VE and I
always get a Null Pointer Exception. There's no stack trace, just one
window telling me it couldn't open the file in the VE and that it's a NPE.
I've had a bit of trouble Googling for this. Any ideas what it is? I would
think it's related to something in my system, since it used to work fine in
3.2, then started having problems (with no changes to Eclipse), then also
had the same problem in 3.2.1.
Any ideas?
Thanks!
|
|
|
| Re: Cannot Load Visual Editor [message #189400 is a reply to message #189252] |
Mon, 22 January 2007 16:36  |
 Paul A. Rubin
Messages: 188
Registered: July 2009 |
Senior Member |
|
|
Hal Vaughan wrote:
> I've asked this on the eclipse.tools.ve group, but in my experience, answers
> there are very slow, and I *have* to get the VE up and running ASAP. I am
> blocked in all my work until it's back online, so I need a solution quickly
> or I have to find another IDE. I'm not threatening, it's just gotten to
> where I have to get it working ASAP or switch to something with a VE that I
> can get working. Any help is appreciated!
>
> I'm using Ubuntu Linux, Edgy upgraded from Dapper. I've installed Eclipse
> 3.2.1 from eclipse.org instead of using apt. I'm using Java 1.4.2 from
> Sun, not any 3rd party version.
>
> I had been using Eclipse 3.2 and I started running in to this problem, so I
> created a clean install of 3.2.1, updated it, added the VE, made sure that
> was updated as well, and I still have the same problem.
>
> I've also tried installing Eclipse with apt-get. It's in a different
> directory, so I have two different versions (and I've deleted /~/.eclipse
> between tests). It doesn't do any good and I cannot install needed updates
> because my window manager won't let me log in as root, I can't run Eclipse
> from the console in X, as root, and have it open a window when X is run
> under my own username. In other words, I get this problem with completely
> different install and even with the newer Java 6 that I just installed.
>
> Whenever I open an existing class or create a new one to edit in the VE, I
> get a requestor telling me that it can't open the file in the VE and I
> always get a Null Pointer Exception. There's no stack trace, just one
> window telling me it couldn't open the file in the VE and that it's a NPE.
>
> I've had a bit of trouble Googling for this. Any ideas what it is? I would
> think it's related to something in my system, since it used to work fine in
> 3.2, then started having problems (with no changes to Eclipse), then also
> had the same problem in 3.2.1.
>
> Any ideas?
>
> Thanks!
>
Are you installing other plugins besides VE and its dependencies? If
so, you might try a clean install with just VE and dependencies and see
if that helps. Seems to me I've seen occasional allegations of
conflicts between plugins, though I don't recall if VE was ever involved.
/Paul
|
|
|
| Re: Cannot Load Visual Editor [message #189467 is a reply to message #189400] |
Mon, 22 January 2007 20:50 |
| Eclipse User |
|
|
|
Originally posted by: hal.thresholddigital.com
Paul Rubin wrote:
> Hal Vaughan wrote:
>> I've asked this on the eclipse.tools.ve group, but in my experience,
>> answers
>> there are very slow, and I have to get the VE up and running ASAP. I
>> am blocked in all my work until it's back online, so I need a solution
>> quickly
>> or I have to find another IDE. I'm not threatening, it's just gotten to
>> where I have to get it working ASAP or switch to something with a VE that
>> I
>> can get working. Any help is appreciated!
>>
>> I'm using Ubuntu Linux, Edgy upgraded from Dapper. I've installed
>> Eclipse
>> 3.2.1 from eclipse.org instead of using apt. I'm using Java 1.4.2 from
>> Sun, not any 3rd party version.
>>
>> I had been using Eclipse 3.2 and I started running in to this problem, so
>> I created a clean install of 3.2.1, updated it, added the VE, made sure
>> that was updated as well, and I still have the same problem.
>>
>> I've also tried installing Eclipse with apt-get. It's in a different
>> directory, so I have two different versions (and I've deleted /~/.eclipse
>> between tests). It doesn't do any good and I cannot install needed
>> updates because my window manager won't let me log in as root, I can't
>> run Eclipse from the console in X, as root, and have it open a window
>> when X is run
>> under my own username. In other words, I get this problem with
>> completely different install and even with the newer Java 6 that I just
>> installed.
>>
>> Whenever I open an existing class or create a new one to edit in the VE,
>> I get a requestor telling me that it can't open the file in the VE and I
>> always get a Null Pointer Exception. There's no stack trace, just one
>> window telling me it couldn't open the file in the VE and that it's a
>> NPE.
>>
>> I've had a bit of trouble Googling for this. Any ideas what it is? I
>> would think it's related to something in my system, since it used to work
>> fine in 3.2, then started having problems (with no changes to Eclipse),
>> then also had the same problem in 3.2.1.
>>
>> Any ideas?
>>
>> Thanks!
>>
>
> Are you installing other plugins besides VE and its dependencies? If
> so, you might try a clean install with just VE and dependencies and see
> if that helps. Seems to me I've seen occasional allegations of
> conflicts between plugins, though I don't recall if VE was ever involved.
>
> /Paul
I tried reinstalling a number of ways. I wiped the directory and
re-installed, then installed the VE through Eclipse. I tried installing it
through the package manager (apt), I tried wiping the directory and
reinstalling from scratch, including installing the VE at the same time. I
even made sure I wiped /~/.eclipse and it made no difference. I finally
wiped out ~/workspace/.metadata and that did it. I don't know what was
there that made the difference. It did mean re-creating my projects, but
since I'm still learning and haven't added a ton of settings, and the
projects were all in different directories (and none in ~/workspace), it
was acceptable.
To me, the obvious conclusion was that there was something wrong with a
setting. Before I wiped the .metadata directory, I noticed if I tried to
change prefs on the VE, they wouldn't stay. If I tried to change the
default layout from the original to a null layout, the box would not stay
checked. I don't know which setting or config file caused the problem, but
I didn't have time to search for it.
Thanks for the suggestion, but since it went across all new installs, I
finally decided it had to be what wasn't changing with new installs. First
to look at was ~/.eclipse, then ~/workspace/.metadata.
Hal
|
|
| |
| Re: Cannot Load Visual Editor [message #189587 is a reply to message #189479] |
Tue, 23 January 2007 19:06 |
| Eclipse User |
|
|
|
Originally posted by: hal.thresholddigital.com
Paul Rubin wrote:
> Hal Vaughan wrote:
>> I finally
>> wiped out ~/workspace/.metadata and that did it. I don't know what was
>> there that made the difference. It did mean re-creating my projects, but
>> since I'm still learning and haven't added a ton of settings, and the
>> projects were all in different directories (and none in ~/workspace), it
>> was acceptable.
>>
>
> Didn't think of that, but other people have reported other breakdowns
> that were cured by wiping .metadata, so maybe Eclipse occasionally mungs
> something there (?).
>
> Glad you're back up and running.
Thanks. It's in my "bag of tricks" now. In the future, if it comes up
again, I'll search .metadata first and see if I can figure out what could
be the problem.
Hal
|
|
|
| Re: Cannot Load Visual Editor [message #189817 is a reply to message #189587] |
Wed, 24 January 2007 18:25 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Hal Vaughan wrote:
> Paul Rubin wrote:
>
>> Hal Vaughan wrote:
>>> I finally
>>> wiped out ~/workspace/.metadata and that did it. I don't know what was
>>> there that made the difference. It did mean re-creating my projects, but
>>> since I'm still learning and haven't added a ton of settings, and the
>>> projects were all in different directories (and none in ~/workspace), it
>>> was acceptable.
>>>
>> Didn't think of that, but other people have reported other breakdowns
>> that were cured by wiping .metadata, so maybe Eclipse occasionally mungs
>> something there (?).
>>
>> Glad you're back up and running.
>
> Thanks. It's in my "bag of tricks" now. In the future, if it comes up
> again, I'll search .metadata first and see if I can figure out what could
> be the problem.
Whenever Eclipse has internal errors, the details are logged in
<workspace>/.metadata/.log - that usually has enough information to
narrow down the problem, and it certainly can help Googling and posting
to the newsgroups.
Hope this helps,
Eric
|
|
|
| Re: Cannot Load Visual Editor [message #190243 is a reply to message #189817] |
Fri, 26 January 2007 17:21 |
| Eclipse User |
|
|
|
Originally posted by: hal.thresholddigital.com
Eric Rizzo wrote:
> Hal Vaughan wrote:
>> Paul Rubin wrote:
>>
>>> Hal Vaughan wrote:
>>>> I finally
>>>> wiped out ~/workspace/.metadata and that did it. I don't know what was
>>>> there that made the difference. It did mean re-creating my projects,
>>>> but since I'm still learning and haven't added a ton of settings, and
>>>> the projects were all in different directories (and none in
>>>> ~/workspace), it was acceptable.
>>>>
>>> Didn't think of that, but other people have reported other breakdowns
>>> that were cured by wiping .metadata, so maybe Eclipse occasionally mungs
>>> something there (?).
>>>
>>> Glad you're back up and running.
>>
>> Thanks. It's in my "bag of tricks" now. In the future, if it comes up
>> again, I'll search .metadata first and see if I can figure out what could
>> be the problem.
>
> Whenever Eclipse has internal errors, the details are logged in
> <workspace>/.metadata/.log - that usually has enough information to
> narrow down the problem, and it certainly can help Googling and posting
> to the newsgroups.
>
> Hope this helps,
> Eric
That does help.
Any idea why the error message dialog box only says, "NullPointerError" and
doesn't give a stacktrace?
Hal
|
|
|
| Re: Cannot Load Visual Editor [message #190272 is a reply to message #190243] |
Fri, 26 January 2007 18:54 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Hal Vaughan wrote:
> Any idea why the error message dialog box only says, "NullPointerError" and
> doesn't give a stacktrace?
I can't say with authority about Eclipse's design, but it is generally
considered poor UI design to show details like a stack trace in a error
notification dialog. These kinds of error usually mean that "something
went horribly wrong" and a GUI element isnt' the proper debugging mechanism.
Eric
|
|
|
| Re: Cannot Load Visual Editor [message #190361 is a reply to message #190272] |
Sat, 27 January 2007 03:22 |
| Eclipse User |
|
|
|
Originally posted by: hal.thresholddigital.com
Eric Rizzo wrote:
> Hal Vaughan wrote:
>> Any idea why the error message dialog box only says, "NullPointerError"
>> and doesn't give a stacktrace?
>
> I can't say with authority about Eclipse's design, but it is generally
> considered poor UI design to show details like a stack trace in a error
> notification dialog. These kinds of error usually mean that "something
> went horribly wrong" and a GUI element isnt' the proper debugging
> mechanism.
>
> Eric
I could see that in most programs, but it would seem that in an IDE the user
is expected to have a certain level of sophistication. In this case, the
program is written in Java for those who are, for the most part, also
writing in Java. It's one of the few cases where more error details would
seem to be more beneficial. At least a button on the error window that
would reveal more details might help.
I'm not directing this at you, Eric. I'm just voicing a thought that any
Eclipse developers reading this might find worth considering.
Hal
|
|
|
| Re: Cannot Load Visual Editor [message #190466 is a reply to message #190361] |
Sun, 28 January 2007 23:23 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Hal Vaughan wrote:
> Eric Rizzo wrote:
>
>> Hal Vaughan wrote:
>>> Any idea why the error message dialog box only says, "NullPointerError"
>>> and doesn't give a stacktrace?
>> I can't say with authority about Eclipse's design, but it is generally
>> considered poor UI design to show details like a stack trace in a error
>> notification dialog. These kinds of error usually mean that "something
>> went horribly wrong" and a GUI element isnt' the proper debugging
>> mechanism.
>>
>> Eric
>
> I could see that in most programs, but it would seem that in an IDE the user
> is expected to have a certain level of sophistication. In this case, the
> program is written in Java for those who are, for the most part, also
> writing in Java. It's one of the few cases where more error details would
> seem to be more beneficial. At least a button on the error window that
> would reveal more details might help.
>
> I'm not directing this at you, Eric. I'm just voicing a thought that any
> Eclipse developers reading this might find worth considering.
You can always file a Bugzilla enhancement request (please search to see
if something similar already exists) at http://bugs.eclipse.org
Keep in mind that Eclipse is not a Java IDE per se, it is a general
application platform and the decision to not show stack traces might be
rooted in that generality.
Eric
|
|
|
Goto Forum:
Current Time: Thu Apr 25 01:56:45 GMT 2024
Powered by FUDForum. Page generated in 0.08784 seconds |
] 
Search
Help
Register
Login
Home
