When submissions are put in, there is a way for mentors to talk to students to ask for more details. Those don't show up in the published abstract you can see at the end.

The discussion shifted towards focusing on getting things to a point where Haskell can meaningfully use SWIG rather than on Qt per se but it is good to keep such a concrete goal in mind when working on something as abstract as SWIG.

I agree that Qt has a somewhat horrible API. =)

-Edward

On Wed, May 29, 2013 at 12:34 PM, harry <voldermort@hotmail.com> wrote:

Edward Kmett <ekmett <at> gmail.com> writes:

> There should be a link from the google-melange website, but one slight
shift in focus is on either getting SWIG bindings or possibly even using
Ian-Woo Kim's C++FFI tools. Carter may be able to go into more detail.

There's almost no information in the google project abstract. My concern is
that the problem isn't generating the bindings (as I've said, that's been
done twice before). It's that Qt's slots-and-signals are horrible to use
from the Haskell side. If the student hasn't already got a good idea of how
to solve this, I fear that this project will be just generate another
unusable set of bindings.

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe