It's not really clear what Apple is telling me to do vis a vis
WebObjects. They say:
Apple's strategy is to make WebObjects the best server-side runtime
environment we can by:
- Improving performance, manageability, and standards compliance
- Making WO work well with ANT and the most popular IDEs, including
Xcode and Eclipse
- Opening and making public all standards and formats that WO depends
upon
I don't see "You should stop using Xcode and use Eclipse and WOLips
instead." Maybe they can't say that explicitly but I think the lack
of clarity is what makes this conversation recycle over and over.
That said, if anyone needs help working on an Objective-C replacement
for EOModeler or WOBuilder (especially EOModeler), I would be happy
to help out!
On Jan 22, 2007, at 3:21 PM, Calven Eggert wrote:
If tons of people on this list are recommending it, take the hint.
(Maybe
that's why Apple is telling you too.)
Calven
--
Mike Nowak
Work: http://chcr.umich.edu/
Personal: http://snackdog.org/
"Beer: All the carbs I need."
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
