On Fri, 22 Jan 2010 17:15:00 -0800
>> "Conal" == "Conal Elliott" wrote:
Hello Conal,
Conal> I've worked with both wxhaskell and gtk2hs. I prefer wxhaskell
Conal> for elegant design. And I like that it gives me a native Mac OS
Conal> X look. There is a partially working native Gtk for Mac,
Hi Conal,
I recently switched my app from Haskell to Smalltalk because I was
unable to code interdependent widgets with wxHaskell, ie. a bunch of
dropdowns where changing the value of one needs to change the set of
elements available in others.
Well I was unable to code this in Haskell without
Hi Gour,
I've worked with both wxhaskell and gtk2hs. I prefer wxhaskell for elegant
design. And I like that it gives me a native Mac OS X look. There is a
partially working native Gtk for Mac, but I don't think it works with 3D,
which was a requirement for me. The X11 mode is painful & ugly, a
Hi, me again... I'm using the current darcs version of wxhaskell (darcs get
--partial --set-scripts-executable http://code.haskell.org/wxhaskell/) and
seems like this patch is not applied and the code in eljfindrepldlg.cpp is
wrong again.
Can someone check it out, please?
Thanks.
Marie von
Ebner
On Thu, 21 Jan 2010 11:59:01 +
>> "Jeremy" == "Jeremy O'Donoghue" wrote:
Jeremy> Documentation and its layout are not always as clear as they
Jeremy> could be for wxHaskell. Despite the fact that it is not the
Jeremy> most 'interesting' or 'fun' thing for me to work on, I plan to
Jeremy> d
Hi Günther,
I suppose that at the end of the day, both toolkits will provide a
very similar interface: You create some sort of raw widget
(DrawingArea for Gtk2Hs) and then react to expose events. Gtk2Hs also
has some other widgets that allow you to have widgets within your
custom widget (L
