About this time last year, I said that I was interested in converting the QIF Import to C++. I did some top level investigation for a couple of months to figure out a path forward, then work and life got in the way and I had to set it aside. Now I am retired and caught up on everything, so I'm starting to get back into this project.
I don't want to make any changes to the UI code more than necessary. I'm learning a lot here - gnucash, glib, scheme - trying to figure out a UI toolkit that I'm not familiar with seems too much, especially given that I am still learning the functionality of the import itself. The path that I have been experimenting with is to create a thin C API layer to wrap the (not yet designed) C++ interface and update the GUI C code to replace all scheme calls and data structures with C API calls. All non-gui data structures would be moved into the C++ implementation. Let me know if there is another direction that would be preferable. Where my sandbox code stands right now is that I have a version of the UI code that replaces all guile with C calls. The C calls are not implemented and need better organization and documentation if I continue down this path. The C++ interface design would be the next step after that. I plan to submit the project for review at various phases - defining the C API, defining the C++ interface, multiple implementation and test reviews. For the C++ classes, I am planning to create a set of base classes that can someday be used as a basis for new implementations of other import functionality, and QIF specific classes that inherit from these base classes. Brian
_______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
