What is the methodology of creating GUI toolkits bindings with functional languages ?
Hello,
I think I generally understand how one can create GUI toolkits bindings with procedural languages, and for this discussion I consider OO languages to be procedural. Regarding the similarity between OO and procedural languages - my point is that both are state-friendly. I.e. it's not a problem to create an instance of the toolkit widget, and that widget instance keeps state. If we look at pure functional languages, we do not have state (though we kinda have them through monads, don't we ?). Anyway, I am interested to learn about the methodology of creating GUI toolkits bindings with/for functional languages and, specifically, about resolving the issue of instances/states. Any pointers ? I can, of course, start digging into, say, Haskell for which, AFAIR, gtk+ has bindings, but I would like to first read something more abstract. Thanks in advance. |
Hi,
I don't know if I can help here. I've waited with an answer to your question for some days because I did not want to kick it from the zero reply list ;) Well, I'm no expert for functional programming and no professional programmer at all. To your question: I'm using the Xmonad windowmanager which is written in Haskell. One of the dependencies for Xmonad is haskell-X11 http://www.haskell.org/haskellwiki/X...ing_in_Haskell. You may also take a look at the Xmonad documentation http://xmonad.org/xmonad-docs/xmonad...t:ScreenDetail where the concepts are explained on a "programmer level". Hope this helps. Markus |
Quote:
So, now I have quite a lot of stuff to comprehend. |
All times are GMT -5. The time now is 08:52 AM. |