Re: Time out!
Re: Time out!
- Subject: Re: Time out!
- From: Karl <email@hidden>
- Date: Sat, 12 Aug 2006 16:30:00 -0700
Deepak,
You don't need to worry about WOBuilder or EOModeller or Xcode or Rule
Editor or WOALauncher going away right now. The tools are
deprecated. They will not go away any time soon.
When Apple deprecates something, they are simply telling us that they
are no longer investing in the tool, product, API or whatever. Take
the Quicktime C API. For years now it has been deprecated and Apple
have been telling us not to use it. It still works just fine. Apple
won't make it a 64-bit API because they are not investing in that
technology and it has long since been replaced by QTKit.
Take Classic as an example. Its the compatibility mode introduced in
2000/2001 with the beta and first releases of Mac OS X. It is
deprecated but still works on PowerPC-based Macs. It was not ported
to Macs running on Intel (although Apple clearly could have done this
if they felt there was a need).
Apple has not said that they are going to stop shipping the deprecated
tools with Xcode. They are still shipped with Xcode 2.4, which has
just been released and I have no reason to suspect that Apple will
stop shipping them in their deprecated state for some years to come.
They won't improve them nor will they fix the bugs. And if they need
to make another big transition some time in the future - say to
another processor or something equally radical - and these products
won't work, then they may stop shipping them. But when will that be?
Already, WOLips and Mike's Entity Modeler do a better job than
EOModeler and the Xcode build system. The community will rapidly
evolve these tools and others, such as Rule Modeler and other yet-to-
be-invented products and make the old Apple tools irrelevant.
So if you are comfortable with Xcode and the various classic WO tools,
go ahead and use them. I expect them to be around for some years but
do not expect to be using them myself for much longer.
Its been nice knowing you Xcode / EOModeler / WOBuilder but I think
that our time together is rapidly coming to an end.
Karl
On Aug 12, 2006, at 4:18 PM, Deepak Nulu wrote:
On Aug 12, 2006, at 2:00 PM, Anjo Krank wrote:
Am 12.08.2006 um 22:45 schrieb Deepak Nulu:
I am not a fan of manually editing the wod files. I was impressed
when I first saw drag-and-drop bindings in WOBuilder (even though
I am used to it since Nextstep days with InterfaceBuilder; I just
did not expect it for a web-based UI builder :-). So I stick with
WOBuilder and EOModeller (you just need to have XCode up and
running in the background) and do everything else in WOLipse/
Eclipse.
Well good luck...
Currently I am only dabbling in WO and am not writing any serious or
production level stuff. The luck I am hoping for is that there will
be WOBuilder and EOModeller replacements before I start doing any
serious or production level stuff :-).
I would like to contribute to the replacement effort (coding), but
can't do so right now. I spent a lot of my spare time learning WO,
and I really don't feel like learning yet another framework
(Eclipse) now :-). That, and my spare time is disappearing fast.
I'll try to contribute ideas, and in the future, code as well.
--deepak
_______________________________________________
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
_______________________________________________
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