• 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: Apple's Tools Strategy
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple's Tools Strategy


  • Subject: Re: Apple's Tools Strategy
  • From: Laurence Harris <email@hidden>
  • Date: Sun, 29 Oct 2006 02:02:10 -0500


On Oct 28, 2006, at 4:19 PM, Turtle Creek Software wrote:

Yes, there is an improved version -- it's called Cocoa! It is an
extremely rich framework that allows you to focus on your features
within your niche.

I'm sure Cocoa is very cool, and if we were starting development on a new product now, we'd use it.

Likewise, I'm aware that many people like XCode the way it is, and
that's fine.  I don't want to take XCode away from anyone!

The problem is, we have shipping software with code developed in CW and
PowerPlant, and we also have limited resources-- time spent switching
frameworks or switching compilers means less time writing accounting
features, and keeping users happy.


80% of our sales are on Windows, and all our competitors are in a
platform that hasn't forced any major code changes in 9 years (and
won't with Vista, either). Meanwhile, in that same time period, we've
faced five big changes-- Think C to CW, 68K to PPC, 9 to X, CW to XCode
and PPC to Intel.

Macintosh, the transition platform. ;-)

I must say that Apple and MW did a great job of easing the moves to PPC
and OSX. We only spent a week or two for the PPC version, and a couple
months to get to OSX. The Intel swap will also be relatively painless,
since we're already byte-swapping for our Windows version.


What we need is an easier transition from CW to XCode, too.  If that
change is indeed necessary.

Absolutely necessary since you can't use CW to build an Intel-native binary and CW is now defunct and no longer supported as a product.


We simply can't spend .5 to 1
programmer-year on something that just gets us back to where to we
started.

It's nowhere near that bad, especially if you have access to someone who is familiar with the process. When Apple first announced the transition to Intel, a number of people were able to convert their CW projects to Xcode while they were at WWDC. The key is to be efficient with your time. If you get stuck, ask for help asap instead of struggling with it for a long time.


Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Re: Apple's Tools Strategy (From: Turtle Creek Software <email@hidden>)

  • Prev by Date: Re: Apple's Tools Strategy
  • Next by Date: Re: Apple's Tools Strategy
  • Previous by thread: Re: Apple's Tools Strategy
  • Next by thread: Re: Apple's Tools Strategy
  • Index(es):
    • Date
    • Thread