Re: Strange WOLips importing error
Re: Strange WOLips importing error
- Subject: Re: Strange WOLips importing error
- From: Georg Tuparev <email@hidden>
- Date: Sun, 25 Nov 2007 16:19:32 +0200
On Nov 25, 2007, at 2:53 PM, Mike Schrag wrote:
Everything looks normal, but I'd like to know what happened. I have
seen this in the past, and later discovered few files were missing.
You'd have to look in the Error Log view (not Problems View, but the
Error Log view -- if you Window=>Open View=>Error Log you can get to
it) and find the corresponding entry probably to get the actual
stack trace to have any chance of figuring out what exactly this NPE
was.
Thanks, nice to know this. The error is already gone (I had to restart
Eclipse) but next time it happens I will check for the stack trace.
Did I mention how much in love I am with Eclipse? Look what a
meaningful error, and look at the scroller of the text view... one
could scroll half a mile to the right to discover ... well,
nothing :)
Come on, Georg -- I KNOW you're not implying that WOB, EOModeler,
and Xcode were bug free, right? Because that would be silly, as I
don't even USE these apps and can think of several bugs in them.
And when Eclipse has a bug, there's almost always a proper stack
trace available somewhere in the logs vs when WOB fails and you get
a one line Obj-C error message and the entire application crashes
down around you. I'm not defending this particular error --
obviously it provides no context and is basically worthless. But
you know what? We'll fix that bug within the next few days and
you'll STILL be waiting for a bugfix for some 4 year old bug filed
against WOB.
My comment was about esthetics and not about existence of bugs. One
needs to have very low esthetic desires not to be intimidated by the
look of Eclipse. I started using PB (now Xcode in 1991). Since that
time my collection of its UI disasters is significantly shorter
compared to the one I have for Eclipse.
But when you start the questions about bugs. You are absolutely
correct that there are many very old Xcode & friends related bugs (my
oldest reported and still opened is from 2003), and this is indeed
very frustrating. Nevertheless I moved a significant body of very old
C/Obj-C code (started 14 years ago) to Xcode 3 / Leo within 30 min.
And I was abled to move it to GC/Properties within 2 days. I am trying
to move from Tiger to Leo (using practically the same version of
Eclips/WOLips) for the last 2 weeks, and still cannot produce a
working (deployable) version. The same procedure when we moved to
Tiger took me calling a script and a coffee while waiting to finish
the compilation....
Here another one. I use the same version as you, and I use
<cmd><shift>-t/r constantly. Never crashed! For you it crashes 50% of
the time. Probably because around you is a bit colder, or I type
slower? In our team we observe such discrepancies daily. This does not
encourage my trust in the tool. These are factors we need to discuss
here and at bugreport.apple.com, and I am really tired of the standard
remarks, that we have to move on. I never will suggest that you or any
of the Eclipse advocates move to something else, but I would also
expect that you start also respecting what others have to say. Our
team develops one of the largest WO projects around, and I do not feel
I have no rights to have my opinion and also to communicate it. OK?
ms
-- georg --
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden