• 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: Writing application without Interface Builder
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Writing application without Interface Builder


  • Subject: Re: Writing application without Interface Builder
  • From: Patrick Hartling <email@hidden>
  • Date: Tue, 18 Jul 2006 07:01:55 -0500

Murat Konar wrote:
>
> On Jul 17, 2006, at 7:52 PM, Patrick Hartling wrote:
>
>> [C++ based library makes it difficult to write Cocoa using Interface
>> builder]
>
> I tracked down an earlier post of yours which sheds a bit more light on
> what you're doing
>
> <http://www.cocoabuilder.com/archive/message/cocoa/2006/2/6/156127>
>
> and in which you note that
>
>> (The application object derives from a base C++ class, the interface
>> methods of which are invoked by the microkernel in a spawned thread.)
>
> and
>
>> Then, I would see what it would take
>> to get that to work in a spawned NSThread with no event processing
>> happening
>> in the primordial thread.
>
> If I'm reading this right, you're hoping to run UI code (including
> receiving events) in threads other than the main thread. You should know
> that this unfortunately isn't supported.

At the moment, I actually have things working the way that I need to with
regard to the multi-threading. I am not sure that it is stable since I am
only working with a simple test case that (more or less) acts like the full
framework. So far, I have created one window from a spawned thread and
successfully processed keyboard and mouse events in it, but there is still a
lot more that I have to do before I will know for sure that things are going
to work for me.

> It sounds like your microkernal wants to be in charge, and that what
> you're trying to do is plug Cocoa into an already existing app
> framework, yes? I wonder if splitting this up so that you have your C++
> based "app" (with no visible manifestation) running in one process,
> communicating with a Cocoa part that runs in another process is worth
> investigating?

That is a very interesting idea. I had not thought of that at all, and I
will definitely ponder it some more. Thanks for the feedback.

 -Patrick


--
Patrick L. Hartling                    | VP Engineering, Infiscape Corp.
PGP: http://tinyurl.com/2oum9          | http://www.infiscape.com/

Attachment: signature.asc
Description: OpenPGP digital signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: Writing application without Interface Builder
      • From: Patrick Hartling <email@hidden>
    • Re: Writing application without Interface Builder
      • From: CoLo0LoGo <email@hidden>
References: 
 >Writing application without Interface Builder (From: Patrick Hartling <email@hidden>)
 >Re: Writing application without Interface Builder (From: Murat Konar <email@hidden>)
 >Re: Writing application without Interface Builder (From: Patrick Hartling <email@hidden>)
 >Re: Writing application without Interface Builder (From: Murat Konar <email@hidden>)

  • Prev by Date: Re: Writing application without Interface Builder
  • Next by Date: Re: KVO and the observeValueForKeyPath bottleneck
  • Previous by thread: Re: Writing application without Interface Builder
  • Next by thread: Re: Writing application without Interface Builder
  • Index(es):
    • Date
    • Thread