Thanks for fleshing this out!
Your characterisation of wxc/wxdirect sounds better. Can't claim to be new at
this myself, but it's been a while.
In the absence of a response from the devs, I would suggest not waiting for a
blessing and going ahead and modifying wxdirect if working from the json
Hello!
First, do you know about the work on wxOcaml?
http://www.ocamlpro.com/blog/2013/04/02/wxocaml-reloaded.html
Thought it would be good if wxHaskell, wxOcaml, and wxRust made a
deliberate point of working together on a single wxC project. (and
before anyone suggests autogenerating wxc from wx
Hi,
I'm working on rust bindings to wx, based on the (wonderful!) wxc
layer exposed by wxhaskell. When starting on the wxdirect equivalent,
it struck me that it was wasteful for everyone to be parsing the .h
files - instead, wxc could consist of both the header files and some
sort of serialised da
