• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: *****SPAM*****How to convince company I should switch to Cocoa
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: *****SPAM*****How to convince company I should switch to Cocoa


  • Subject: Re: *****SPAM*****How to convince company I should switch to Cocoa
  • From: Izidor Jerebic <email@hidden>
  • Date: Mon, 19 Jan 2004 10:26:22 +0100

On Jan 17, 2004, at 6:48 AM, Larry Gerndt wrote:

MY boss is asking me to to justify my desire to rewrite our
Carbon/PowerPlant app in Cocoa. I've seen enough of Cocoa to know that this
is probably the best move I can make. Right now I'm stuck with PowerPlant
(the original), and it's now dead. So either I should port to PowerPlant X
(which is a huge port because PowerPlant X is radically different from the
original), or I spend that time delving into Cocoa. I believe the Cocoa API
is richer by far than PowerPlant X could hope to be, though PowerPlant X
does look excellent for anyone who wants to stay in the Carbon API.

It would sure help to know what is it that your application does. But I guess that for almost all cases the following holds - just do it in Cocoa! Your application automatically gets all the nice stuff - unicode support, printing, document & text handling, services, and lots of other goodies that come for free when using Cocoa. You can always wrap your custom logic in ObjC ( or C++ - not recommended, but possible if necessary) and use it as model in ModelViewController scheme. This redesign will benefit your application even if you do not implement it in Cocoa - better OO design always improves application (less bugs, better maintainability, ...). Cocoa implementation will also benefit you because you will sub-consciencely absorb a lot of best-practice that is contained in Cocoa, simply by using Cocoa and allowing it to guide your implementation.

In short - your application's quality and maintainability (it will become much easier and faster to improve it in the future) will greatly improve as a side effect of moving to Cocoa. This alone will probably make it worthwhile....

izidor
_______________________________________________
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.

References: 
 >*****SPAM*****How to convince company I should switch to Cocoa (From: "Larry Gerndt" <email@hidden>)

  • Prev by Date: Re: [ANN] Graphviz 1.10 (v2) for Mac OS X, beta test
  • Next by Date: Re: encoding structs (NSCoder / NSArchiver issue)
  • Previous by thread: Re: *****SPAM*****How to convince company I should switch to Cocoa
  • Next by thread: Re: *****SPAM*****How to convince company I should switch to Cocoa
  • Index(es):
    • Date
    • Thread