On 3/4/10 3:34 PM, Christian Stimming said: > [...] > Announcing a new sub-project in gnucash: The non-GUI parts are re-used in the > state they are, in the C language. This means the double-entry principles and > all of the other achievments in the "engine" and xml-backend and eventually > other backends can be re-used. But the GUI is rewritten completely new, from > scratch, in C++ and using the Qt toolkit. Fun again. The build system is > CMake > because its configuration runs magnitudes faster. Fun again. And as a final
Sounds fun. Are you doing this as a sub-project because you'd like to see Cutecash become, someday, an optional (maybe default) front-end for GnuCash? Or would you be OK with forking Cutecash off and re-implementing a single Qt-based GUI? I ask because the latter option seems more attractive to me--a separate, back-to-basics project can have its own repo and forum, and can take advantage of the latest DVCS and integrated web-hosted project sites (Launchpad, GitHub, BitBucket, etc.). A Launchpad project may also be able to keep continuously importing an SVN repo's commits and rebasing the project's own commits on top of those. This last bit, I'm not sure of though. Even without it, I think there's probably a way to keep tracking GnuCash development while still working on a separate project. Anyway, my point is that a simple, elegant and tightly-integrated C++/Qt/WebKit financial app sounds like a very good idea, but it should ideally be separate from the GnuCash project itself. Of course, you may have a different end goal. Cheers, Yawar
signature.asc
Description: OpenPGP digital signature
_______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
