Re: *****SPAM*****How to convince company I should switch to Cocoa
Re: *****SPAM*****How to convince company I should switch to Cocoa
- Subject: Re: *****SPAM*****How to convince company I should switch to Cocoa
- From: Stéphane Sudre <email@hidden>
- Date: Tue, 20 Jan 2004 23:32:55 +0100
On mardi, janvier 20, 2004, at 08:48 PM, Paul Lalonde wrote:
I personally would be very reluctant to move development over to
Cocoa, though admittedly the choice depends on a number of factors.
Here are some issues to ponder, in no particular order:
- Where is the application in its lifecycle? Is it being actively
developed, or is it more in a maintenance situation? Are new
application features likely to require features of Mac OS X not
already supported by PowerPlant? The cost of tweaking your source (or
PowerPlant itself) may be smaller than a rewrite, depending on your
application's needs. On the other hand, perhaps there are features in
the planning stages that could benefit greatly from Cocoa.
True and wrong. It depends on every application. If you have a lot of
dirty code written and fixed over the years, it might be a good idea to
start from a fresh version. From experience, I know that the move
should be almost mandatory if you have a lot of table views in your
application or if you want to handle multiple localizations (easily).
- Switching to Cocoa means re-implementing the application. The cost
of doing so can easily approach that of the initial implementation.
You will get a completely new set of bugs. And while the rewrite is
happening, you won't be improving the app from a user's perspective.
Note that the same is true for a port to PPx.
You forget that instead of thinking he's using a Java application, the
user will think that he's using a Mac OS X native application.
_______________________________________________
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.