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

Re: CoverFlow on 10.4


  • Subject: Re: CoverFlow on 10.4
  • From: Oliver Quas <email@hidden>
  • Date: Sat, 18 Aug 2007 18:51:16 +0200

hm, i wonder if it is patented.

the omni group has an app called omnidazzle that has a view almost equal to coverflow. see the screenshot at

http://www.omnigroup.com/applications/omnidazzle/

do they pay apple for using it?

best regards,
oliver



Doesn't Apple have a patent on Cover Flow?

They probably do, and I imagine that if you tried to incorporate a cover flow view into a windows application that their lawyers would come knock on your door.


However, Apple has traditionally been rather forgiving over the use of their intellectual property on the platform so long as the original intent of the element is maintained. So, if you need a button that takes the user to their home directory you can use the home image from the finder on your button. However, don't use that button to take your user to the beginning of their document as that changes the meaning of the icon.

_______________________________________________

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


  • Follow-Ups:
    • Re: CoverFlow on 10.4
      • From: Alastair Houghton <email@hidden>
  • Prev by Date: Re: Insert at cursor position NSTokenField
  • Next by Date: Re: Another Core Data + table view question
  • Previous by thread: Re: CoverFlow on 10.4
  • Next by thread: Re: CoverFlow on 10.4
  • Index(es):
    • Date
    • Thread