• 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: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging


  • Subject: Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
  • From: Marco Scheurer <email@hidden>
  • Date: Thu, 4 Dec 2003 14:29:22 +0100

On Thursday, December 4, 2003, at 07:16 AM, Scott Anguish wrote:

On Dec 3, 2003, at 4:21 PM, Stuart Halloway wrote:
I've been looking into wrapping the SearchKit in a more usable, Cocoa-style API. A couple of questions:

1. Are others feeling the same need? I'd be more than happy not to reinvent this wheel.

2. Wouldn't it be cool if SearchKit had wrapper classes that were toll-free bridged, like NSString/CFString etc.? I have looked into this and here are my results so far:
[...]

A SearchKit API in Obj-C would rock.. but I don't think attempting to implement tollfree bridging is the best way for you to accomplish it.

I agree: a SearchKit API in Obj-C is a must, and I wouldn't care for tollfree bridging...

And this leads to this question: why should developers like us get into this work of providing proper object-oriented APIs to some of Apple's Carbon or Core Foundation stuff?

I understand that with limited resources priorities have to be set, so this is not a criticism, but there are several things begging for Objective C APIs: Sockets, the SearchKit, Quicktime...

Now if Stuart or someone else start making a wrapper for the SearchKit, there are currently no guarantees that this work will not be obsoleted in a week or a month if Apple does it. And if nobody does it, there are no guarantees that it will not be missing for years.

Depending on the copyright and license of such products (for instance Free BSD vs GPL) Apple could silently reuse some of this effort, but wouldn't it make sense for Apple to "officialize" these contributions? Maybe ask for them, and maybe acknowledge them? Maybe even promote and distribute an open sourced "Cocoa Contributions" umbrella framework?

Marco Scheurer
Sen:te, Lausanne, Switzerland http://www.sente.ch
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
      • From: Jim Rankin <email@hidden>
    • Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
      • From: Stuart Halloway <email@hidden>
References: 
 >Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging (From: Scott Anguish <email@hidden>)

  • Prev by Date: RTF Style names
  • Next by Date: Apple Consultants Network question
  • Previous by thread: Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
  • Next by thread: Re: Toll Free Bridging, wrapping the SearchKit, and One-Way Bridging
  • Index(es):
    • Date
    • Thread