Re: EOF replacement
Re: EOF replacement
- Subject: Re: EOF replacement
- From: Marco Scheurer <email@hidden>
- Date: Thu, 21 Feb 2002 15:39:45 +0100
On Wednesday, February 20, 2002, at 09:02 pm, Georg Tuparev wrote:
Some facts:
- It seams that Apple will not keep their promise to support
Objective-C version of EOF
- In our company we have tones of ObjC EOF based sources that we
depend on in order to finish our products on time.
- We are not going to use Java EOF or even a bridge.
- We are using FrontBase only.
- We need object persistency framework for almost every serious
application or project.
In order to finish the products we are working on, we see the following
options:
1. Try to hack into Apple's CVS and get the EOF sources;
2. Write our own replacement;
3. Buy a replacement from someone else;
4. Develop completely new version of EOF that fixes all long standing
issues and adds some essential goodies.
5. Apple (or third party) announces new equivalent product (within 4
months)
The first four options might have some legal consequences. But after
Apple decided not to keep their promise and left us behind with huge
(at least for us) worthless investments, I do not feel very bad about
it.
After months long discussions with my partners & friends we think that
option #4 is probably the best. But before jumping on it, I would
appreciate your comments about this matter.
1. If you're going to do something as illegal as steal the source, it
might be easier (but also illegal) to reverse engineer EOF Java: there
are some good Java decompilers.
2. Is it different from #4?
3. I haven't seen any good replacement, not even for Java, and certainly
not in Objective C.
4. I think that would be a lot of work, but maybe something simpler
would be enough? Sometimes, I have a feeling that EOF has become too
large and complicated.
5. I remember someone, on this list or over at email@hidden,
saying that EOF / Cocoa / Objective C would be resurrected by Apple, but
I wouldn't bet on this.
Since you posted on cocoa-dev, I assume that you need EOF for Cocoa
development. If that is the case, you do not need to rewrite the entire
EOF to get started: the EO frameworks are still there
(System/Library/PrivateFrameworks). If you are ready to bet that #4 or
#5 are possible, then as a first step, you only have to rewrite what is
now broken (EOInterface, EOF IB palette), or missing (an up-to-date
Frontbase adaptor).
marco
Marco Scheurer
Sen:te, Lausanne, Switzerland
http://www.sente.ch
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.