• 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
[Moderator] Re: [Moderator] Re: MacBook Air multitouch trackpad API
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Moderator] Re: [Moderator] Re: MacBook Air multitouch trackpad API


  • Subject: [Moderator] Re: [Moderator] Re: MacBook Air multitouch trackpad API
  • From: Scott Anguish <email@hidden>
  • Date: Sun, 3 Feb 2008 12:48:43 -0800

Guys.

Please, don't debate this here.

Just drop the thread.


On Feb 3, 2008, at 12:21 PM, Steve Christensen wrote:

On Feb 2, 2008, at 7:22 PM, Nicko van Someren wrote:
On 2 Feb 2008, at 21:31, Scott Anguish wrote:
On Feb 2, 2008, at 1:17 PM, Wesley Smith wrote:
On Feb 2, 2008 1:15 PM, Scott Anguish <email@hidden> wrote:

Do not post links to reverse engineered APIs here.

why not?


First, the Mac OS X Software License Agreement says you may not disassembly or reverse-engineer (This is list not the place to debate whether or not this would fall under fair use or not)


Humph... OS X sends me an event on a post card (OK, in an NSEvent), one it sends to everyone else who has a MacBook Air, and I'm not allowed to tell people what it says? I agree that this isn't the place to debate what is and isn't reverse engineering, but the simple fact is that this isn't.


From Wikipedia: "Reverse engineering is the process of discovering the technological principles of a device, object or system through analysis of its structure, function and operation." In order to determine that support for the MacBook Air trackpad exists, the OP had to dig through undocumented private frameworks (or private class methods in public frameworks) to find what he was looking for.

I'm not qualified to discuss fair use in this case, but it does sound like reverse engineering.

Another point about discussing private APIs is that some people then have a tendency to want to use them, rather than waiting for a public solution or relying on another way of doing something. And some of -them- don't code defensively so that when Apple removes that API, or changes how it behaves, their software becomes unstable.

My two cents...

steve

_______________________________________________

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

_______________________________________________

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: 
 >MacBook Air multitouch trackpad API (From: ∞ <email@hidden>)
 >[Moderator] Re: MacBook Air multitouch trackpad API (From: Scott Anguish <email@hidden>)
 >Re: [Moderator] Re: MacBook Air multitouch trackpad API (From: "Wesley Smith" <email@hidden>)
 >Re: [Moderator] Re: MacBook Air multitouch trackpad API (From: Scott Anguish <email@hidden>)
 >Re: [Moderator] Re: MacBook Air multitouch trackpad API (From: Nicko van Someren <email@hidden>)
 >Re: [Moderator] Re: MacBook Air multitouch trackpad API (From: Steve Christensen <email@hidden>)

  • Prev by Date: Re: [Moderator] Re: MacBook Air multitouch trackpad API
  • Next by Date: receiving a file on app startup
  • Previous by thread: Re: [Moderator] Re: MacBook Air multitouch trackpad API
  • Next by thread: copyCGLContextForPixelFormat
  • Index(es):
    • Date
    • Thread