I personally picked up both wxHaskell and reactive-banana at the same time
and it was fine. In practice the two are almost orthogonal—reactive-banana
completely supplants parts of wx and doesn't touch the rest at all, for the
most part. (I recall some wx-specific quirks that leak out into
reactive-banana code, but nothing too bad.)
For me, the examples included with reactive-banana-wx were probably the
most useful learning aide. Once you figure out how the examples work, you
can modify them and see the changes right away, which is enough of a
stepping stone to figure the rest out from the API docs.
As far as superimposing text on an image, that should only take
wxHaskell-specific code. You'll probably have to mess around with the
layout, but the two widgets (text and image) should still be the same and
so act the same from the perspective of reactive-banana.
On Tue, Jan 6, 2015 at 5:06 PM, Jeffrey Brown
Hi!
I want to write a mindmapping app, like Freeplane, which involves drawing rectangles containing text and arrows connecting them. For that purpose, today I installed reactive-banana, wxWidgets, wxHaskell and reactive-banana-wx. (It's the first complex install for which I didn't have to write the list for help!)
Am I correct that the question of whether graphics can be superimposed over text depends only on wxHaskell, and not reactive-banana? Would you recommend first writing code that uses only wxHaskell, to become familiar with the library, or jumping right in by using reactive-banana at the same time?
Regards, Jeff
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe