Re: Unable to make dist after recent changes
On zaterdag 3 december 2011, John Ralls wrote: OK, all of that's committed. Make distcheck now works on both Mac and Linux. Yay! John, thanks for these fixes. Nice job ! The symbol imported from both (sw_engine) and (gnucash engine) warnings are still there, I see, but these are less critical. Next, I want to get rid of all of the errors from calling ENTER and LEAVE when QOFLog hasn't been inited. Easy enough in C, but I don't see a way to init QOFLog from Scheme. Anybody know of one? Unfortunately I don't know. Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Unable to make dist after recent changes
On zaterdag 3 december 2011, John Ralls wrote: OK, all of that's committed. Make distcheck now works on both Mac and Linux. Yay! I found one more problem: the python bindings tests fail if you have enabled them: make check-TESTS make[5]: Entering directory `/kobaltnet/janssege/Development/Builds/gnucash- f15-trunk/src/optional/python-bindings/tests' Traceback (most recent call last): File /kobaltnet/janssege/Development/EclipseGnuCash/GnuCash- git/src/optional/python-bindings/tests/runTests.py, line 5, in module from test_book import TestBook File /kobaltnet/janssege/Development/EclipseGnuCash/GnuCash- git/src/optional/python-bindings/tests/test_book.py, line 3, in module from gnucash import Session ImportError: No module named gnucash FAIL: runTests.py == 1 of 1 test failed Please report to gnucash-devel@gnucash.org == make[5]: *** [check-TESTS] Error 1 Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
FW: OpenSuse 12.1 Guile 2.0
Hello, in the moment I am using this version (J.Engel) http://download.opensuse.org/repositories/home:/j-engel/openSUSE_12.1/i586/ It is working including the onelinebanking (hbci), but the the reports have severe problems (hanging, crashing) In Guile 2.0 several procedures are completly deleted: the GH Interface (isthis of any relevance??) maxdepth, scm_string_chars (already corrected in trunk), scm_stringp, scm_symbol_chars scm_symbol_chars appears in the following files: guile-util.c, option-util.c, engine-helpers.c, dialog-tax-info.c, druid-qif-import.c At least here a correction is needed (may be with scm_symbol_to_string, scm_to_utf8_stringn) My capabilities are are limited, sorry Rudolf ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: 2.4.99 on opensuse 12.1
2.4.99 from github On Fri, Dec 2, 2011 at 7:46 PM, John Ralls jra...@ceridwen.us wrote: On Dec 2, 2011, at 5:06 PM, Ted Creedon wrote: put guile 1.8.7 in its own directory # CPPFLAGS=-I/root/guile-1.8.7/include LDFLAGS=-L/root/guile-1.8.7/lib64 ./configure --disable-error-on-warning --disable-dbi --enable-debug # GUILE_AUTO_COMPILE=0 gnucash --debug --extra This is a development version. It may or may not work. Report bugs and other problems to gnucash-devel@gnucash.org. You can also lookup and file bug reports at http://bugzilla.gnome.org The last stable version was GnuCash 2.4.7 The next stable version will be GnuCash 2.6 WARNING: (gnucash import-export qif-import): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) WARNING: (gnucash import-export qif-import): `gnc-build-dotgnucash-path' imported from both (sw_engine) and (gnucash core-utils) WARNING: (gnucash report report-system): `GNC-DENOM-AUTO' imported from both (sw_engine) and (gnucash engine) overrides core binding `N_' [Snip] WARNING: (gnucash report easy-invoice): imported module (gnucash app-utils) overrides core binding `N_' ice-9/psyntax.scm:1326:30: In procedure chi-macro: ice-9/psyntax.scm:1326:30: Syntax error: unknown location: source expression failed to match any pattern in form do What revision is this? Did you check it out from code.gnucash.org or github.com/Gnucash/gnucash, or did it come from some other source? Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: FW: OpenSuse 12.1 Guile 2.0
Guile 2.0 has sabotaged guncash I'm told to build 2.4.99/2.4.8 against guile 1.8.x which I have with limited success Also discovered dbus problem with running via ssh -X -A tedc On Sat, Dec 3, 2011 at 2:44 AM, rbibr...@t-online.de rbibr...@t-online.dewrote: Hello, in the moment I am using this version (J.Engel) http://download.opensuse.org/repositories/home:/j-engel/openSUSE_12.1/i586/ It is working including the onelinebanking (hbci), but the the reports have severe problems (hanging, crashing) In Guile 2.0 several procedures are completly deleted: the GH Interface (isthis of any relevance??) maxdepth, scm_string_chars (already corrected in trunk), scm_stringp, scm_symbol_chars scm_symbol_chars appears in the following files: guile-util.c, option-util.c, engine-helpers.c, dialog-tax-info.c, druid-qif-import.c At least here a correction is needed (may be with scm_symbol_to_string, scm_to_utf8_stringn) My capabilities are are limited, sorry Rudolf ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Explorer's log: Entering the maze
Thanks for all the help so far. I now generate the users and doxygen documentation, and have started exploring it. The internal system documentation is a maze. And unlike mazes printed in puzzle books, there aren't clearly identified start and finish points :) Or, at least, I haven't found them yet. I'm going to try and keep a log of my adventures getting into the maze; it may help later when I or someone else is writing or rewriting documentation. Should I send the log entries here? Most will not be cries for help, but they may serve as a guide for an author of a StartReadingHere page or some such. I hope my style here will be light and engaging, but if it doesn't turn out that way, I can only apologize. So far I've found gnucash/src/doc/html/index.html, which looks like a start page. It contains lots of links, but has no notion of which links are more or less important. The first Doxygen overviews I went to were Engine Framework and Engine Architecture. Engine Framework is minimal, and doesn't seem to have anything to say about an engine framework. It does have an API link, and that's perhaps the important part of that page. Other than that, there's a mention of additional API documentatino in src/doc/design/engine.texinfo, which , rather helpfully, advises me not to read it as being hopeless obsolete. The companion page, Engine Architecture, merely tells me it is becoming obsolete, and, rather helpfully, recommends I refer to the design documentation in src/doc/design for a complete description of the Engine architecture src/doc/design for a complete description of the Engine architecture. I do so, and discover that every file with content in that directory is marked as hopelessly obsolete. No, don't rush to delete them right away -- I think the history is valuable. They are plainly enough marked that they won't confuse anybody as too the current state of affairs. Now the API link I mentioned above (to file:///home/hendrik/dv/gnucash/ workspace/gnucash/src/doc/html/group__Engine.html) *is* important, and links to that kind of stuff is what should be on an API intro page, together with short descriptions of what one can expect to find at the end of each link. The group__*.html pages seem to organize the meat of the API. I'll start on such a page. I'll leave it to later to decide whether it should be assembled out of pieces by doxygen or written as a single coherent piece of prose. I'll have to have some content before determining the form. -- hendrik ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Explorer's log: Entering the maze
On Dec 3, 2011, at 12:08 PM, Hendrik Boom wrote: Thanks for all the help so far. I now generate the users and doxygen documentation, and have started exploring it. The internal system documentation is a maze. And unlike mazes printed in puzzle books, there aren't clearly identified start and finish points :) Or, at least, I haven't found them yet. I'm going to try and keep a log of my adventures getting into the maze; it may help later when I or someone else is writing or rewriting documentation. Should I send the log entries here? Most will not be cries for help, but they may serve as a guide for an author of a StartReadingHere page or some such. I hope my style here will be light and engaging, but if it doesn't turn out that way, I can only apologize. So far I've found gnucash/src/doc/html/index.html, which looks like a start page. It contains lots of links, but has no notion of which links are more or less important. The first Doxygen overviews I went to were Engine Framework and Engine Architecture. Engine Framework is minimal, and doesn't seem to have anything to say about an engine framework. It does have an API link, and that's perhaps the important part of that page. Other than that, there's a mention of additional API documentatino in src/doc/design/engine.texinfo, which , rather helpfully, advises me not to read it as being hopeless obsolete. The companion page, Engine Architecture, merely tells me it is becoming obsolete, and, rather helpfully, recommends I refer to the design documentation in src/doc/design for a complete description of the Engine architecture src/doc/design for a complete description of the Engine architecture. I do so, and discover that every file with content in that directory is marked as hopelessly obsolete. No, don't rush to delete them right away -- I think the history is valuable. They are plainly enough marked that they won't confuse anybody as too the current state of affairs. Now the API link I mentioned above (to file:///home/hendrik/dv/gnucash/ workspace/gnucash/src/doc/html/group__Engine.html) *is* important, and links to that kind of stuff is what should be on an API intro page, together with short descriptions of what one can expect to find at the end of each link. The group__*.html pages seem to organize the meat of the API. I'll start on such a page. I'll leave it to later to decide whether it should be assembled out of pieces by doxygen or written as a single coherent piece of prose. I'll have to have some content before determining the form. This should be interesting. ;-) How about a wiki page on http://wiki.gnucash.org/wiki? Link it to the GnuCash page under Development. If you haven't already, you might find it helpful to take a few minutes to skim over the Doxygen documentation. That will help you understand why the docs are structured the way they are. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Unable to make dist after recent changes
On Dec 3, 2011, at 2:13 AM, Geert Janssens wrote: On zaterdag 3 december 2011, John Ralls wrote: OK, all of that's committed. Make distcheck now works on both Mac and Linux. Yay! I found one more problem: the python bindings tests fail if you have enabled them: make check-TESTS make[5]: Entering directory `/kobaltnet/janssege/Development/Builds/gnucash- f15-trunk/src/optional/python-bindings/tests' Traceback (most recent call last): File /kobaltnet/janssege/Development/EclipseGnuCash/GnuCash- git/src/optional/python-bindings/tests/runTests.py, line 5, in module from test_book import TestBook File /kobaltnet/janssege/Development/EclipseGnuCash/GnuCash- git/src/optional/python-bindings/tests/test_book.py, line 3, in module from gnucash import Session ImportError: No module named gnucash FAIL: runTests.py == 1 of 1 test failed Please report to gnucash-devel@gnucash.org == make[5]: *** [check-TESTS] Error 1 Fixed, and I'll push it with the next batch later today. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Strategy
I've been watching with interest the messages flying by from various people that confirm the impression (from just trying to build it) that Gnucash has become a gigantic hairball. John Ralls has been saying a number of things that sound smart (I'll tell you later where to send the check, John) about design errors, problems in the data model, etc., and has embarked upon a re-design. Christian has taken a similar step back with Cutecash. Then there's the whole issue of the use of Scheme. Much as I love the elegance of the language, I doubt that its use is appropriate here, for all the reasons that we've discussed ad nauseum. So I'd like to suggest that perhaps none of the proposed ways-forward are radical enough. I have little to no knowledge of Gnucash internals. The only thing I know about the quality of the design and the code is what I read from the people who are currently doing the real work. But I do have many, many years of experience working and managing projects of similar and greater complexity, and there are times when you just have to cut your losses. Gnucash has been around for a long time, and its life-span covers the development of a lot of tools. If you were going to start with a blank sheet of paper today, I doubt very much whether you would do a lot of the system as it is today. The big question is, when is it worth it to cut your losses and start over? I don't know that Gnucash is at that point, but I'm suggesting that you give this question very careful consideration, before doing something incremental. Keep in mind that if you did start over, the current system wouldn't be a total loss. I'm sure there is a lot of value in things like accounting rules that it enforces, and other knowledge embedded in the code. Some of it might be salvageable by lifting parts of the code itself, or at least doing translations. Other cases might involve just transferring knowledge of how to do things and how not to do things. But I say don't throw good money *possibly* (not definitely) after bad without at least considering whether it's time for Gnucash II. /Don ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Strategy
On Sat, 2011-12-03 at 16:40 -0500, Donald Allen wrote: The big question is, when is it worth it to cut your losses and start over? I don't have strong opinions, but others do, in the opposite direction: Joel Spolsky says (in the context of Netsape) single worst strategic mistake that any software company can make: They decided to rewrite the code from scratch. and also As a corollary of this axiom, you can ask almost any programmer today about the code they are working on. It's a big hairy mess, they will tell you. I'd like nothing better than to throw it out and start over. There's more in his essay Things You Should Never Do http://www.joelonsoftware.com/articles/fog69.html Ross Boylan ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Get quotes broken again?
Hi all, I've just joined this list after searching the archives and finding this thread from earlier this year: On 19.01.2011 05:22, Mike Alexander wrote: --On January 18, 2011 4:07:17 PM -0800 Russ Walasek kesalaw at gmail.com wrote: Price quotes work on 2.4, but don't work on the latest trunk release. On OS X 10.6.6, building from source. This should be fixed in revision 20126. The bug was introduced in revision 20042. Yes, I built r20126 and can confirm that it works again. I am running Ubuntu Lucid 64 bit, and I initially thought that the problem was because the repos contain an older version. But I have now manually installed Gnucash 2.4.7, built from rb5bdf19+. When I try to update the quotes, I get unable to retrieve quotes. The last time it ran successfully was 10/14/2011. Any help appreciated. Thanks, Devin ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
