Hello I am pleased to announce a Haskell binding to the FLTK (http://www.fltk.org) GUI toolkit available from http://www.cs.helsinki.fi/u/ekarttun/hs-fltk/ Hs-fltk is focused on creating a simple API for building GUIs in Haskell and manages to keep the binary size down. Currently it is tested on Linux, but FLTK is available on Win32 too... - Einar Karttunen
Einar Karttunen wrote:
I am pleased to announce a Haskell binding to the FLTK (http://www.fltk.org) GUI toolkit available from http://www.cs.helsinki.fi/u/ekarttun/hs-fltk/ [...]
Hmmm, it doesn't work with the GHC from HEAD: -------------------------------------------------------------------------- panne@jeanluc:~/hs-fltk-0.2.5> make examples make -C example build make[1]: Entering directory `/home/panne/hs-fltk-0.2.5/example' ghc -package FLTK -o test test.hs test.hs:3:39: Failed to load interface for `FLTK.Widget': Could not import `FLTK.Widget': it is hidden (in package FLTK-0.2.5) make[1]: *** [test] Fehler 1 make[1]: Leaving directory `/home/panne/hs-fltk-0.2.5/example' make: *** [examples] Fehler 2 -------------------------------------------------------------------------- I've changed the Makefile a bit to use ./setup configure --prefix=/tmp/fltk and ./setup install --user This avoids being root at install time and should probably be available more conveniently. Cheers, S.
Sven Panne
Hmmm, it doesn't work with the GHC from HEAD:
This seems to be due to revision 1.20 of http://cvs.haskell.org/cgi-bin/cvsweb.cgi/fptools/ghc/compiler/iface/LoadIfa..., and my cvs ghc was older than that. This changed things so that one cannot export the contents of a hidden module, e.g. module Exposed (module Private) where import Private If this is the intended behavior things can be made to work by changing the all the modules to be exposed in Setup.description.in. - Einar Karttunen
Einar Karttunen wrote:
[...] This changed things so that one cannot export the contents of a hidden module, e.g.
module Exposed (module Private) where import Private
If this is the intended behavior things can be made to work by changing the all the modules to be exposed in Setup.description.in.
Hmmm, I am not sure that this is really intended: "Exposed" explicitly says that it wants to export "Private", hidden or not. It seems like a perfectly normal use case. Perhaps SimonM could comment on this... Cheers, S.
participants (2)
-
Einar Karttunen -
Sven Panne