So, if you don't mind, I'm going to stop trying to fit cubes into round holes and gonna use reactive and fieldtrip[4] to do things.
Yes exactly, these projects are an attempt to make reactive programming (and GUI programming is one of these) much more composable. However it is still unclear to me if these frameworks can fix the typical space leaks that have been addressed in AFRP (e.g. Yampa) and also mentioned in the Fruit paper. A nice discussion between Yampa and Reactive took place in this list a while ago (see http://www.nabble.com/Yampa-vs.-Reactive-td21045891.html)http://www.nabble.com/Yampa-vs.-Reactive-td21045891.html So AFRP also tries to make reactive programming more composable, and already succeeded somehow by showing working games and prototype guis, but the arrows syntax takes away much of the elegance of Haskell (we're really drawing boxes and links in Haskell here ;-) and research is still being done to make it more scalable (push versus pull, see e.g. http://www.cs.yale.edu/homes/hl293/download/NEPLS-talk.pdf)http://www.cs.yale.edu/homes/hl293/download/NEPLS-talk.pdf To me, none of these approaches mean anything as long as we can't produce real complex GUIs with it :-) I do hope that Haskell community will combine efforts to make a practical reactive (and GUI) framework!
[1]http://softbase.org/hqk/qoo/qoo.pdf [2] http://haskell.org/gtk2hs/docs/devel/System-Glib-GObject.html#v%3AmakeNewGOb... [3]Somewhat disregarding using OS widgets, but that's unimportant since native look+feel is vastly overrated. I've got enough asbestos to defend that against alt.politics. [4]Gotta get rid of glut, though.
-- (c) this sig last receiving data processing entity. Inspect headers for copyright history. All rights reserved. Copying, hiring, renting, performance and/or quoting of this signature prohibited.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe