Mark Jenkins <[EMAIL PROTECTED]> writes: > Jeff Green wrote: >> The best bet might be to put the non-language specific stuff into a >> separate file (it would mostly consist of common typedefs and function >> declarations) and have the language specific interface files %include >> that file. > >> I think doing it this way would work well, I'm just slightly reluctant >> to do it because it would involve mucking around with things unrelated >> to the Python bindings. > > Thanks for investigating this. > > The plan seems fine, and I think we should give it a try and muck with > the needed stuff outside of src/optional/python-bindings in ParIT's > private repo for awhile until this is ready. In fact, if as you suggest > there are changes needed outside of src/optional/python-bindings that > will make GnuCash's SWIG interface files more flexible, generic, and > useful to our use case, perhaps you and I should send in a patch with > just that and only that first.
Sounds good to me. >> that file. There would also still need to be separate typemaps for more >> complex types like GList since they need to be handled in a particular > > Yeah proper GList support is going to be fun. I'm going to want to see a > python wrapper class that implements the python list api. :) I think that's between you and python ;) > I wonder if there is any overlap with this project: > https://launchpad.net/pyglib Possibly! I was under the impression you were working with those guys. I guess I was wrong in assuming that? (Note that I haven't looked at their code so I don't know how good it is or whether it's in a shape capable of being integrated into gnucash). > Mark -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
