[erlang-questions] cocoa bridge

[Jon Watte]

How about this? I've used this for other systems I've needed to wrap in some
GUI:

1) Create cocoa application with a proper "main" that runs in a main thread.
2) create new thread
3) open erl as a dynamic library
4) call the entry point of that dynamic library from the new thread

Sincerely,

jw


--
Americans might object: there is no way we would sacrifice our living
standards for the benefit of people in the rest of the world. Nevertheless,
whether we get there willingly or not, we shall soon have lower consumption
rates, because our present rates are unsustainable.



On Mon, Oct 17, 2011 at 6:57 AM, Joel Reymont <joelr1@REDACTED> wrote:

>
> On Oct 17, 2011, at 2:18 PM, David Goehrig wrote:
>
> > Is there any reason you can't swap order, have the Cocoa app spawn erlang
> in a new thread and treat the original process as a port?
>
>
> I was hoping to avoid marshaling function calls over TCP.
>
> --------------------------------------------------------------------------
> - for hire: mac osx device driver ninja, kernel extensions and usb drivers
> ---------------------+------------+---------------------------------------
> http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
> ---------------------+------------+---------------------------------------
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20111021/ffcb2862/attachment.htm>