[GNC-dev] GnuCash Task Persists Despite Shutdown
Hi, I've been running 5.1 on Windows 11 and have decided 5.4 (installer version 5.4.1) seems stable enough to upgrade. For the first time in at least a dozen GnuCash upgrades, I encountered an issue with the install. The installer insisted two instances of "gnucash.exe" were still running even though I had shut down GnuCash 5.1 before starting the upgrade. Retrying the install also failed, but it eventually succeeded after I terminated both instances with the Task Manager. I then checked with the new install (5.4 / installer 5.4.1) and discovered that "gnucash.exe - GnuCash Program File (32-bit)" remains in the task list indefinitely after shutting GnuCash down. Is this expected? Is it some weird post-caching in the task manager display (they rewrote it for Win 11 with even less deterministic information - I hate the way Windows boxes are getting more and more like Macs every release)? Paul ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Build Issues on Ubuntu jammy
> Did you follow https://wiki.gnucash.org/wiki/Building_On_Ubuntu? No, I missed that. I was following the main (Building_On_Linux) instructions. I will revert to a prior checkpoint and start again using the Ubuntu instructions. The repology site is down for me. Will keep trying it. P ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Build Issues on Ubuntu jammy - guile
Line 5 in the large list at https://wiki.gnucash.org/wiki/Installing_Dependencies -Original Message- From: Frank H. Ellenberger Sent: July 17, 2022 12:27 PM To: Paul Kroitor Cc: gnucash-devel@gnucash.org Subject: Re: [GNC-dev] Build Issues on Ubuntu jammy - guile Am 17.07.22 um 17:25 schrieb Paul Kroitor: > *the documentation says use guile 2.0 but only 2.2 or 3.0 are > available - is there any reason not to install 3.0? > Where exactly? Perhaps it was written a few years ago with conservatie LTS users in mind, which can be 5 years behind. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[GNC-dev] Build Issues on Ubuntu jammy
I have abandoned my rather optimistic attempt to build on Rocky 9 - which is after all less than a week old - as there are far too many dependencies that aren't findable. I've gone back to Ubuntu, but made a new VM for it with 22.04 (jammy), which is all of three months old. All the dependencies stated in the docs install (although a few version numbers are out of date - especially guile*), but it won't build because gwenhywfar is missing and not in the repository. Gwenhywfar-tools is available, but installing it doesn't help. The gwenhywfar website doesn't clarify anything either. Has anyone else encountered this issue? Paul *the documentation says use guile 2.0 but only 2.2 or 3.0 are available - is there any reason not to install 3.0? ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Simple Start to Contributing
Thanks for your kind welcome, John. Well, my first real language was Fortran in the early 70s, but my first love was 360/ASM. I knew (at least some of) 14 languages when I graduated in 1976 but you won't have heard of many of them. My first job was maintaining/extending the (assembly-language, on punch card) mainframe operating system at a big pharma firm, although everyone else there was strictly COBOL. I still recall one of my peers trying to persuade the rest of us that you could write programs without Go-Tos with a new-fangled thing called Structured Programming. Of course, this wasn't any of my business as 360/ASM doesn't have the instructions for it. Then, as a young IT department manager in the early 80s, I can still vividly recall two young whippersnappers (they were 20; I was 25) in my office trying to persuade me that COBOL was out of date, and we would all be using C soon. In later years I spent most of my time in C, Pascal, and C++, but as Project Manager or Director of Development. That said, I was always the type to get my hands dirty, and whenever there was a requirement for low-level stuff (like x86 Assembler), I always wound up assigning it to myself (it's still my favourite part). I've written hundreds of things in C++ and other object-oriented languages. These days the first thing I reach for -- given the simple things that come my way -- is Python, Powershell, or Javascript. The source control I've used is almost exclusively CVS and Subversion, but I do understand what git is and why it's better. My question about making a feature branch was a response to an instruction in the Wiki about when to do so -- this little project seemed to be just on the borderline. Based on your comments, I'll play it safe and do so. I have no trouble following the Guile/Scheme -- Lisp was one of the original 14 languages I studied in college -- and many reports date back 20 years or more anyway. The difficulties come more with the layers of approaches / authors you get in such mature systems. For example, the balance sheet and income statement use common support modules that enable certain standard optional behaviours, but the cash flow wasn't written to use said modules, so one has to duplicate the functionality but really should toss half the cash-flow and use the (better) common support modules. I've built a Rocky 9 (just released, and I want to start testing it anyway) VM for this and will set up the GnuCash build environment on it next (I did a similar thing a couple of years ago, it went fine). Then I will move on to integrating the changes. You should know that although I'm retired, I'm very overcommitted, and I only get to a small percentage of what I hope to achieve. But I will do what I have time for, with your valuable help. Paul -Original Message- From: John Ralls Sent: July 15, 2022 7:04 PM To: Paul Kroitor Cc: gnucash-devel@gnucash.org Subject: Re: [GNC-dev] Simple Start to Contributing > On Jul 15, 2022, at 10:58 AM, Paul Kroitor wrote: > > Hi, my apologies for asking such basic questions, but I'm new to > GnuCash contributions - although not to coding - and want to try a > simple (useful) change to get my feet wet. So I've "fixed" the > cash-flow.scm module (the Cash Flow report) locally to adjust a minor > annoyance (I added a "Show Accounts as Hyperlinks" checkbox so it can > match the other two standard financial statements). It works the way > it should now, but needs testing against a broader set of inputs, and the localizations must get queued. > > Welcome to GnuCash! What languages and programming styles (I mean what are sometimes rather grandly called paradigms, like object-oriented or functional) do you like? Your question about feature branches suggests that you may not be familiar with git. What source control systems have you used? > > Some questions arise: > > 1.Do I have to post anywhere / get agreement before embarking on such > a contribution (I have 30+ years of experience managing programmers > and do know I must keep the changes homogenous in style and approach > to the existing codebase)? For simple changes like this, no. For more substantial changes or new features it's wise to discuss here starting with whether the proposed change is even something that we'll accept and once that's settled working out the design. > 2.Must I checkout and build the entire project if I am only going to > be working in Guile/Scheme for the moment, or is there a simple way to > do a subset? GnuCash doesn't have any subprojects so you have to clone the whole thing. If you don't want to build yourself you can enable CI on your personal GitHub repo and let Github actions run the building and testing part for you. > 3.Do a make a "feature branch" for this very localized change? It's > about 10 lines in a single file. Unless you're pl
[GNC-dev] Simple Start to Contributing
Hi, my apologies for asking such basic questions, but I'm new to GnuCash contributions - although not to coding - and want to try a simple (useful) change to get my feet wet. So I've "fixed" the cash-flow.scm module (the Cash Flow report) locally to adjust a minor annoyance (I added a "Show Accounts as Hyperlinks" checkbox so it can match the other two standard financial statements). It works the way it should now, but needs testing against a broader set of inputs, and the localizations must get queued. Some questions arise: 1. Do I have to post anywhere / get agreement before embarking on such a contribution (I have 30+ years of experience managing programmers and do know I must keep the changes homogenous in style and approach to the existing codebase)? 2. Must I checkout and build the entire project if I am only going to be working in Guile/Scheme for the moment, or is there a simple way to do a subset? 3. Do a make a "feature branch" for this very localized change? It's about 10 lines in a single file. 4. I have about 10 sets of production books here, but I use no business or shareholding features. The changes shouldn't interact with these, but they should be checked anyway. Are there test .gnucash databases with "one of everything" than can be used to test against (I do use multiple currencies, and have tested that)? 5. I understand that the localizations will happen semi-automatically by a different team, but is there a way to use a common instance of the base (English) text constant so they don't have to re-translate strings that are already there (e.g. the "Show Accounts as Hyperlinks" string is already in a half-dozen other scheme files, and thus will have already been translated into many languages)? 6. How / who do I tell that it's new and should be tested before release? Thanks for all help as always, Paul ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
