On Mon, 28 Nov 2011 21:01:38 +0100 Anders F Björklund <a...@algonet.se> wrote:
> Of course, you don't *have* to wrap all the classes or methods ? > One could start with the ones that are likely to be used from D. Well, it is still big project and not so easy to say what needed. In any case, substantial part has to be bound in order to get into writing multi-platform desktop app. > Automation is surely the way to go, the only question is whether it > should be a custom script or if a (patched?) SWIG would be better. That's hard for me to say. > If it helps, there's a Doxygen parser (for the XML output) in the > docs/doxygen/scripts directory that could be used to start it off: > > cd docs/doxygen > ./regen.sh xml > python scripts/make_bindings.py --swig --output_dir=bindings \ > out/xml/classwx_app.xml > > The generated SWIG bindings are for wxPython, but I suppose you > could adopt the swig_tools.SWIGBuilder to generate some D SWIG ? I'll take a look to see if it makes sense to me. :) > Just that I won't have much time to actually maintain it, myself. I'm also not capable to lead such project and would have to take that into consideration when deciding which GUI toolkit to use with D. In any case, for now, I plan to learn more D, master some CMake and start playing with SWIG in order to provide bindings for 3rd party C library which we'll use. Then, in the meantime, maybe there will be more clear which toolkit is optimal to use when writing desktop app in D *today*. Sincerely, Gour -- One who restrains his senses, keeping them under full control, and fixes his consciousness upon Me, is known as a man of steady intelligence. http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
signature.asc
Description: PGP signature
