• 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: CoverFlow
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoverFlow


  • Subject: Re: CoverFlow
  • From: "Mark Munz" <email@hidden>
  • Date: Wed, 21 Nov 2007 11:19:10 -0800

I was addressing the more generic comment that Scott made:
> Well, you certainly should not use undocumented API.  Ever.

And trying to give a few examples where you can't get functionality
without diving into some undocumented territory. Mail APIs, MenuExtras
are a couple examples.

The Coverflow control may be possible to duplicate, but the developer
will likely need to spend a lot of time duplicating all the behaviors
of the control. From the user's perspective, they just want Coverflow
functionality.

Using a private framework may be a shortcut. I agree that it's very
dangerous and shouldn't be done without serious contemplation of the
consequences.

Unfortunately, pretty pictures has taken over these days but that's a
whole other discussion. Apple has given a lot of focus to pretty
pictures scrolling by since they put it into Finder, iTunes and their
iPods.

I would love to see Apple provide a way to use some of the
functionality it finds important enough to use in its own apps without
having to wait another 2+ years to do so.


On 11/21/07, Jaime Magiera <email@hidden> wrote:
>
> On Nov 21, 2007, at 1:48 PM, Mark Munz wrote:
> >
> > *Sometimes*, private APIs are the only option. As I said, you have to
> > have your guard up. I try to avoid private APIs when I can.. but
> > sometimes you aren't given a choice.
>
> Mark,
>
> I guess I'm missing the "only option" connotation. Only option to do
> what? Something that is not supported? Something that your app is not
> dependent on (pretty pictures)?
>
> In other words, where does *necessity* for the feature, particularly
> considering the private API status, come in?
>
> Jaime
>
>
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>


--
Mark Munz
unmarked software
http://www.unmarked.com/
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >CoverFlow (From: Alexander Cohen <email@hidden>)
 >Re: CoverFlow (From: Scott Anguish <email@hidden>)
 >Re: CoverFlow (From: "Mark Munz" <email@hidden>)
 >Re: CoverFlow (From: Jaime Magiera <email@hidden>)
 >Re: CoverFlow (From: "Mark Munz" <email@hidden>)
 >Re: CoverFlow (From: Jaime Magiera <email@hidden>)

  • Prev by Date: Re: NSDate appears to leak
  • Next by Date: Re: CoverFlow
  • Previous by thread: Re: CoverFlow
  • Next by thread: Re: CoverFlow
  • Index(es):
    • Date
    • Thread