• 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: Need replacement of Component Manager::OpenDefaultComponent
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Need replacement of Component Manager::OpenDefaultComponent


  • Subject: Re: Need replacement of Component Manager::OpenDefaultComponent
  • From: email@hidden
  • Date: Sun, 26 Feb 2017 11:35:48 +0900

Yeah but even with OSAKit, to implement a language you need to link to Carbon and use deprecated Carbon calls.

Sent from my iPhone

> On Feb 26, 2017, at 7:18, じょいすじょん <email@hidden> wrote:
>
> Are you implementing scriptability for a Cocoa application? If so, you probably don't need all of this.
>
> Or are you implementing an OSA language? If so, you cannot escape this, but you might consider looking at the scripting bridge instead.
>
>> On Feb 26, 2017, at 6:02, sumit bansal <email@hidden> wrote:
>>
>> I am using it to implement scripting in my project.
>>
>> I have used the API in following way:
>>
>>
>> *ComponentInstance & compInstance =
>> OpenDefalutConmponent(kOSAComponentType,
>> kOSAGenericScriptingComponentSubtype);*
>> *OSASetSendProc( compInstance, someParam1, someParam2); //function in
>> Carbon/Frameworks/OpenScripting/OSA.h*
>>
>>
>> I am using OpenScripting Architecture(OSA) APIs to implement the scripting
>> functionality. To use APIs of OSA, we need to pass ComponentInstance.I
>> don't know any other way of creating the object of ComponentInstance, the
>> only way I know has been depreciated.
>>
>>
>> I am new in MAC programming. Please forgive me if I am asking/replying
>> something foolish.
>>
>>> On 25 February 2017 at 02:42, Jens Alfke <email@hidden> wrote:
>>>
>>>
>>> On Feb 24, 2017, at 9:11 AM, sumit bansal <email@hidden>
>>> wrote:
>>>
>>> Can anyone please help me to find out the replacement of
>>> Function =>  Component Manager::OpenDefaultComponent.
>>>
>>>
>>> That’s very generic; the Component Manager is/was just an ancient
>>> DLL-loading mechanism. IIRC it was mostly used by QuickTime. What are you
>>> using the Component Manager for?
>>>
>>> ―Jens
>>>
>> _______________________________________________
>>
>> 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


  • Follow-Ups:
    • Re: Need replacement of Component Manager::OpenDefaultComponent
      • From: Shane Stanley <email@hidden>
References: 
 >Need replacement of Component Manager::OpenDefaultComponent (From: sumit bansal <email@hidden>)
 >Re: Need replacement of Component Manager::OpenDefaultComponent (From: Jens Alfke <email@hidden>)
 >Re: Need replacement of Component Manager::OpenDefaultComponent (From: sumit bansal <email@hidden>)

  • Prev by Date: Re: I think I screwed up Core Data multi-threading rules.
  • Next by Date: KVC Validation w/ custom Formatter not working
  • Previous by thread: Re: Need replacement of Component Manager::OpenDefaultComponent
  • Next by thread: Re: Need replacement of Component Manager::OpenDefaultComponent
  • Index(es):
    • Date
    • Thread