Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa
Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa
- Subject: Re: Cocoa/EOF for non-enterprise apps Re: proof of cocoa
- From: Nat! <email@hidden>
- Date: Mon, 18 Jun 2001 16:47:31 +0200
[This is just concerning the EOPalette, nothing else]
Am Donnerstag, 14. Juni 2001 um 00:10 schrieb Bill Bumgarner:
Finally, it is very likely the case that Apple hasn't made a
conscious effort to remove or destroy support for things like the
EOPalette.
Could very well be, yes.
It is far more likely that the sweeping changes required to support
Aqua in IB broke the EOPalette in a fashion that would require a fairly
monumental effort to fix.
Fairly monumental effort to fix ???
Come on. One competent engineer could fix the palette in a few days,
probably less. It's far more likely that Apple either plain doesn't want
to or has no staff capable of doing so anymore (yes then of course it
would be a monumental effort, so you must mean the second choice).
It is far more likely that the sweeping changes required to support
Aqua in IB broke the EOPalette in a fashion that would require a fairly
monumental effort to fix.
[What's the deal with the adaptors concerning the palette ? One has
nothing to do with the other.]
basic resource issue even if it IS possible], what is the real return
on investment for devoting a bunch of resources at fixing the
EOPalette? Likely, not nearly as much ROI as devoting those same
resources to pushing the Java Client / JavaEO / IB technologies
forward-- i.e. not as much as supporting the needs of what very likely
is the majority of the developers out there.
The return of investment of providing a functioning EOPalette ? If you
buy an amp and the volume dial ain't working, what's the return of
investment for your dealer to get it fixed ? Exactly the same
(present=none, future=plenty). What's your attitude towards your
dealer, when he refuses to fix the amp ? What will you do, when you're
on stage, and noone hears anything ?
Nat!