Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Converting nibs (Re: [ANN] Nano 1.4)

I do realize that any company has to make business decisions, sometimes very tough ones, to stay in business. But just within the last couple of days, a couple of things, in combination, kind of woke me up.

First, a discussion on NPR about how Apple's stock value has risen 40% since the beginning of the year because of the announcement of the iPhone. How much is the release of Leopard likely to increase Apple stock prices? No wonder "management" feels a need to send a signal Carbon developers. Perhaps we should just be grateful they're working on Leopard at all.

Second, I'm trying to play by Apple's newest rules and switch from using QuickTime Music Architecture to CoreMidi since they're now telling us not to use QTMA for Mac any more (now that it's FINALLY stable after years and years of my having to work around its bugs, but at least I can still use it on Windows). But other than the info in the header files, there seems to be no documentation for the part of CoreMidi I probably need to use to replace QTMA. So I submitted a list of related questions to Developer Tech Support, using one of my precious "incidents." The DTS response to my question about documentation was: "Unfortunately there is not much documentation for CoreMIDI at the moment. Header files and Google are your best bet." Well, I'd studied the one bit of sample code that looked relevant, memorized the header files, searched all the developer documentation available (yes, including the CoreAudio list), already Googled too, and not found the info I needed. Even the DTS person has to go ask an Apple engineer if it's possible to do one thing I want to do since HE doesn't have documentation either. Not incidentally, one immensely useful feature of QTMA is just plain not in CoreMidi. I could try to re-create that feature myself and/or file an enhancement request (the two suggestions from DTS). However, it seems--as with other examples mentioned on this list--like it shouldn't be necessary to have to keep telling Apple that we still need to be able to do the same basic things, even if we have to do them in some brand new way and can add lovely new things we couldn't do before. But then, there's no getting around the fact that Apple stock has gone up 40% since the beginning of the year because of the iPhone, not because of Cocoa's capabilities or the promise of Leopard or 64-bit whatever.

I'm not slamming the DTS folks. They've been extremely helpful over the years, as well as patient when I've asked what were probably dumb questions, and even this time, my most important question was answered. But having a DTS person tell me to Google for info about how to do what Apple is telling me I have to do because the new way isn't documented? Just too much for me yesterday. In short, if some of us seem to lose our temper a bit now and then, maybe we really do have our reasons.

Ann

On Jun 19, 2007, at 10:00 AM, Laurence Harris wrote:
Sure. I need the e-mail address of someone who will convert my Carbon

nibs to Cocoa nibs and rewrite all the code that needs to be
rewritten but won't result in anything any user will be able to detect.



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.