I don't think FLTK requires X11; at least it doesn't need an X server to
run. What I noticed is that it really helps to have a resource fork for
csound; with it the FLTK windows can be moved about etc.; without
it they're frozen, although you seem to be able to access the widgets.
Now, this is all with csound 5; I have not looked at cs4.23 (gbs).

Victor





>Here's a crazy thing that I found a couple of days ago:  an old MacOS 9 port
>of FLTK (version 1.0.10) !  Which version of FLTK does Csound require?
>(Also, I might be wrong about OS X FLTK requiring X11 ...)
>
>
>
>Anthony

Victor Lazzarini
Music Technology Laboratory
Music Department
National University of Ireland, Maynooth  

On 1/7/05 10:03 AM, Victor Lazzarini  etched in
stone:

> I don't think FLTK requires X11; at least it doesn't need an X server to
> run. What I noticed is that it really helps to have a resource fork for
> csound; with it the FLTK windows can be moved about etc.; without
> it they're frozen, although you seem to be able to access the widgets.
> Now, this is all with csound 5; I have not looked at cs4.23 (gbs).

Well, I am really glad to hear this from you, Victor.  I think that I must
have assumed or somehow come to the conclusion a long time ago that FLTK was
based on X.  And over time, it must have become "fact" in my mind.

I want to really apologize for spreading incorrect information on this
issue, and for making a big stink on the list over FLTK and OS X.  Maybe I
will even get it to work soon on my OS X machine and post a binary for
everyone ...

And I think you are very right about the resource fork bit.  I found this
message on a mailing list about a month ago:

--------------------------------------
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.

--------------------------------------

Thanks :)

Anthony Kozar
anthony.kozar@utoledo.edu
http://akozar.spymac.net/