Here is something that I stumbled upon last month while searching for
information on using FLTK with OS X.  I don't know if this is relevant to us
or not:


To: pari-dev@list.cr.yp.to
Subject: Re: Mac OS X + PARI + FLTK
From: matthiasm 
Date: Sat, 19 Jun 2004 00:09:55 -0700

I am not sure if you guys still follow the thread, but I stumbled
across the mail. I am the developer who ported FLTK to OS X. The
solution is very simple: OS X requires that your program has a resource
fork. FLTK provides a default resource fork in FL/mac.r . Simply attach
the resource via

/Developer/Tools/Rez -t APPL -o myappname FL/mac.r

This should make your window responsive and top-level. If threading is
a problem (FLTK prefers to be the main thread, and only one FLTK thread
can run per application, unless you dive into the depth of Fl::lock()
and Fl::unlock()), you can simply use FLTK in the main thread to run
PARI as the second thread. Some communication to open windows, etc. is
probably required.

For more help, feel free to drop by on the FLTK mailing list.

Anthony Kozar  writes:

> Here is something that I stumbled upon last month while searching
> for information on using FLTK with OS X.  I don't know if this is
> relevant to us or not:

This message confirms that our current implementation is not thread
safe.  It also suggests to me that by following the rules in the FLTK
manual for multithreaded applications, we can be sure our FLTK widgets
will work on OS X.

John

To: pari-dev@list.cr.yp.to
Subject: Re: Mac OS X + PARI + FLTK
From: matthiasm 
Date: Sat, 19 Jun 2004 00:09:55 -0700

I am not sure if you guys still follow the thread, but I stumbled
across the mail. I am the developer who ported FLTK to OS X. The
solution is very simple: OS X requires that your program has a resource
fork. FLTK provides a default resource fork in FL/mac.r . Simply attach
the resource via

/Developer/Tools/Rez -t APPL -o myappname FL/mac.r

This should make your window responsive and top-level. If threading is
a problem (FLTK prefers to be the main thread, and only one FLTK thread
can run per application, unless you dive into the depth of Fl::lock()
and Fl::unlock()), you can simply use FLTK in the main thread to run
PARI as the second thread. Some communication to open windows, etc. is
probably required.

For more help, feel free to drop by on the FLTK mailing list.