Re: XCode 2.1 WO Development - Anyone else interested in filing a lawsuit?
Re: XCode 2.1 WO Development - Anyone else interested in filing a lawsuit?
- Subject: Re: XCode 2.1 WO Development - Anyone else interested in filing a lawsuit?
- From: James Cicenia <email@hidden>
- Date: Tue, 16 Aug 2005 12:18:45 -0500
Well,
I don't know about a lawsuit, but I must say I am very displeased
with the quality of this release. However, I have to assume, that at
the last moment they decided to welcome WebObjects home again. Maybe
they can issue a nice release that addresses everything you have
said. I too am suffering severe productivity drains from having to
gingerly open and close files.
The EOModeler is a nightmare now. Used to be quaint with its bugs,
but now it is a monster chewing up models at will.
WOBuilder seems like a decent first showing, however I miss the
pallet on top.
WOModeler... wo are we... do not touch it.
The eclipse with xcode method of development is now a complete hack
in the most negative of terms.
Come on Apple
-James Cicenia
On Aug 16, 2005, at 12:07 PM, Jürgen Lorenz Simon wrote:
Dear Members,
I'm experiencing the severest problems trying to work with XCode
2.1 and the WebObjects install
that came with it on our current WebObjects projects. The list of
problems with this release has grown
so long, that I'm seriously getting into trouble with my customers.
The XCode 2.1 release was by no means termed 'experimental' or
beta. Its in fact the only way to
do WebObjects Development on 10.4 (bar using Eclipse) and I'm sorry
to say this, but its NOT WORKING.
WOModeller
The new version of the WOModeller not only doesnt work. It also
tends to trash and destroy
components. In fact I have not once successfully edited a
WOComponent using it without it in
some form trashing it. Apart from that the inspector bar isn't
working.
EOModeler
The EOModeler tool developed serious problems in dealing with both
inheritance and prototypes.
Using either has cost us numerous hours walking through a largish
model replacing messed up
column definitions. And then (by magic) they got messed up again.
Contantly the EOModeller forgets
relationship definitions. We grew excessively tired of this.
XCode 2.1 hangs a lot
The inter-process communication of XCode2.1 and WOModeller,
EOMOdeller or Rule Editor caused
XCode to hang multiple times in an hour. Sometimes it would hang if
you closed the auxilliary apps
when XCode was still open. On other occasions XCode hung when
trying to open project files that
had been fine minutes ago.
The whole list of problems and their sheer extend can only lead us
to the belief that Apple has not
properly tested these tools before release. And it seems that we
are paying the price for this. I don't
think that's entirely fair. And I'm seriously considering filing a
lawsuit. If anyone else thinks likewise,
I would love to hear from you.
J.L.Simon
--
:tecc
Simon,Jackson GbR
Dipl. Met. Jürgen Simon
Tel: +49 160 7255991
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden