Re: [GNC-dev] GnuCash 3.904 Released - problems with release notes
Hi Chris, Fixed in commit 6f47e41. Thanks! Frank Am 08.06.20 um 03:43 schrieb Chris Good: > Message: 1 > Date: Sun, 7 Jun 2020 13:09:14 -0700 > From: John Ralls > To: gnucash-annou...@gnucash.org > Cc: Gnucash Users , gnucash-devel > > Subject: > Message-ID: <6bf016e7-1038-4d44-8230-3c513b76f...@ceridwen.us> > Content-Type: text/plain; charset=utf-8 > ... > > ? A new separate executable, gnucash-cli (gnucash-cli.exe on > Microsoft Windows) for doing command-line things like updating the prices in > your book. gnucash-cli gains the ability to run reports from the command > line. Specify reports to run by name or guid. It also provides an export > format and an output file name without which it will output the report to > stdout. > ? gnucash --report run --name=[reportname/guid] > datafile.gnucash > ? gnucash --report run --name=[reportname/guid] > --output-file=x.html datafile.gnucash > ? gnucash --report run --name=[reportname/guid] > --output-file=x.html --export-type=TYPE datafile.gnucash > > > Shouldn't the examples be using gnucash-cli instead of gnucash ??? > > If you're going to fix that, you might also like to change > > Open Business items will also save *there* column widths to the page section > so these can temporarily have different widths. > > To > > Open Business items will also save *their* column widths to the page section > so these can temporarily have different widths. > > Regards, Chris Good > > ___ > 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
Re: [GNC-dev] GnuCash 3.904 Released - problems with release notes
Message: 1 Date: Sun, 7 Jun 2020 13:09:14 -0700 From: John Ralls To: gnucash-annou...@gnucash.org Cc: Gnucash Users , gnucash-devel Subject: Message-ID: <6bf016e7-1038-4d44-8230-3c513b76f...@ceridwen.us> Content-Type: text/plain; charset=utf-8 ... ? A new separate executable, gnucash-cli (gnucash-cli.exe on Microsoft Windows) for doing command-line things like updating the prices in your book. gnucash-cli gains the ability to run reports from the command line. Specify reports to run by name or guid. It also provides an export format and an output file name without which it will output the report to stdout. ? gnucash --report run --name=[reportname/guid] datafile.gnucash ? gnucash --report run --name=[reportname/guid] --output-file=x.html datafile.gnucash ? gnucash --report run --name=[reportname/guid] --output-file=x.html --export-type=TYPE datafile.gnucash Shouldn't the examples be using gnucash-cli instead of gnucash ??? If you're going to fix that, you might also like to change Open Business items will also save *there* column widths to the page section so these can temporarily have different widths. To Open Business items will also save *their* column widths to the page section so these can temporarily have different widths. Regards, Chris Good ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Feedback on GnuCash 3.903
Hi Rob, FYI - I've just installed 3.904 in case it makes a difference... 1) Well that's the issue I guess - accounts grow to fill the available space :-) Gnucash has given me plenty of space/nesting ability over the years so some of my account names are quite long eg "Assets:Fixed Assets:Superannuation:Super - David:Super:Super Income Account" and "Expenses:Mobile Phone:David:xxx: 999 999:Month to Month Plan". So when I revert to defaults (in transaction journal view) because there's nothing in the split description and the transaction description is only about 25 characters it looks a bit ridiculous to have the description column so large and the account name truncated so severely. I'm not sure that "Expenses:Automobile:Gasoline" is a sufficiently good example to be using to base the default column width on - even my auto expenses are broken down by vehicle so end up looking more like "Expenses:Auto:Nissan XTrail:Repairs and Maintenance". 2) Perhaps it would be better to base it on the "Tot Funds Out" header length which is 2 characters longer instead as that's what is being truncated. Yes I worked out that depending on which line was highlighted the column headers/double clicking changed. Second point seems to have resolved itself - not sure if it was connected to the Tools-->General default setting (point 3) that I used moments ago but the "Created Transactions" tab now appears to be using the column widths I expected. 3) Ah my bad - to my knowledge I have never used any Journals in Gnucash in my life so didn't realise this would affect the scheduled txn layout - all good now. Also thanks to you and the other devs for all your hard work on gnucash, it is much appreciated. As a former C# developer I know just how hard it can be to keep everyone happy :-) Cheers David H. On Sun, 7 Jun 2020 at 23:06, Robert Fewell <14ubo...@gmail.com> wrote: > David, > Thanks for trying and the feedback, will try and answer your points... > 1) The program default widths have not changed and are based on example > strings in code. So for the account / transfer column it is based on > "Expenses:Automobile:Gasoline" plus some space for the button. I added > those accounts to my test book and it fitted exactly. > 2) Same thing here but it is based on a number, "999,999.000". I did fix > the double clicking on the header but you need the highlighted line to be > on the transaction as opposed to the splits. Not sure I understand the > second point. > 3) Do not know why that is, you should be able to adjust the column widths > and they will be remembered as before, this aspect has not been touched. > The scheduled transactions template > is based on the REG_TYPE_GROUP_JOURNAL group so go to 'Tools->General > Journal' and setup the desired widths from there. Will see if I can add the > menu options to the template window. > > > On Sun, 7 Jun 2020 at 00:29, David H wrote: > >> Hi Robert/Geert, >> >> Thanks for that. I only use Gnucash for my personal expenses so it looks >> like I'm only using the first register group. I've installed 3.903 and am >> happy that my use case apart from scheduled transactions is generally >> unaffected so will leave installed and continue using and if anything pops >> out of the woodwork I'll post something here if that's the way to go. >> >> For your info my setup is Win 10 Pro and I'm running gnucash on a 27" >> monitor at 1920 x 1080 res and I always run it full screen. Dual monitor >> with laptop screen as secondary display. >> >> A few minor things I did notice are as follows :- >> >> 1. Reverting to default on a register seems to shrink the Transfer column >> down a lot further than I expected and really truncates the column. >> 2. When I review scheduled Created Transactions and revert to default it >> also cuts off the left side of the "Tot Funds In" and "Tot Funds Out" >> columns (see pic attached). Also if I close without saving after reverting >> to default when Gnucash restarts and recreates the txn's it doesn't pick up >> the new default it seems to remain on the reverted view with the truncated >> columns. This is also after I go to another account register with good >> columns and click on use as default for this group so it's like it's become >> orphaned from the defaults. >> 3. My list of scheduled txns seems to have shrunk the Name column. Also >> in all of the template transactions the account column has shrunk right >> down and the Windows menu when you're in the template editor doesn't >> include the new register default entries which leads me to thinks this is >> possibly an unintended consequence and since I've got a lot of these I'm >> probably have to go and re-adjust each one :-( >> 4. If I go in and change the widths of some columns and then scroll up a >> couple of pages of txns and decide "meh this isn't looking so good" I just >> close the register and re-open it to get the defaults back so that's good. >> >> Thanks David. >> >> >> >> >> On
Re: [GNC-dev] [GNC] GnuCash 3.904 Released
Lots of improvements coming to the next stable release! Thanks o the developers for their hard work! On Sun, Jun 7, 2020 at 3:11 PM John Ralls wrote: > The GnuCash development team announces GnuCash 3.904, the third testing > release for what will soon be GnuCash 4.0. > > Changes > > Baseline requirements > > Operating Systems: > > • Linux: Ubuntu 18.04LTS > • MacOS: 10.13 > • Windows: 8.1 > Software Dependencies: > > • C++ standard is now C++17, requires gcc 8.0 or clang 6.0. > • Cmake 3.10 > • boost 1.67.0 > • gettext 0.19.6 for general use, 0.20 to generate gnucash.pot. > • glib-2.0 2.56.1, gtk 3.22.30 > • googletest 1.8.0 > • ICU, any version. > • libdbi 0.8.3 > • libxml2 2.9.4 > • swig 3.0.12 Now required for building from tarballs as well as > from git. > • Webkit 2.4.11 Mac & Win32, 2.14.1 Linux/BSD > New Features > > 3.903 was the feature-freeze release. However, the command-line arguments > for both gnucash and gnucash-cli have been adjusted as follows: > > • --add-price-quotes is changed to --quotes get > • --run-reports is changed to --report run --name > • Added --report list to produce a list of available reports. > • Added --report show --name to describe the options changed from > the default values in the named report. > The intent is to have command categories with subcommands to better enable > a richer command line capability as illustrated with the new report > commands list and show. > > • A new separate executable, gnucash-cli (gnucash-cli.exe on > Microsoft Windows) for doing command-line things like updating the prices > in your book. gnucash-cli gains the ability to run reports from the command > line. Specify reports to run by name or guid. It also provides an export > format and an output file name without which it will output the report to > stdout. > • gnucash --report run --name=[reportname/guid] > datafile.gnucash > • gnucash --report run --name=[reportname/guid] > --output-file=x.html datafile.gnucash > • gnucash --report run --name=[reportname/guid] > --output-file=x.html --export-type=TYPE datafile.gnucash > • When deleting accounts the destination accounts of moved splits > will be checked to ensure that they have the same commodity as the source > account. If they don't you'll get a warning and the opportunity to pick > another account or to carry on regardless. > • New type-ahead search added to sequential search when selecting > an account in the register: Instead of typing the first few characters of a > top level account, the separator, the first few characters of the next > level account and so on you may instead type a few characters of any part > of a full account name and the drop-list will be filtered to contain only > matching accounts. Once you have a small enough list you can use the arrow > keys to select the account that you want. > • Python bindings are now localized and their strings available > for translation. > • The new reports introduced in the Experimental Reports menu are > moved to the main menu and the old reports hidden; the old reports can be > unhidden by running GnuCash from the commandline with the --extra argument. > That will cause the old reports to appear in their regular locations on the > menu labeled (legacy). Note that new reports use different options and > layouts and you may need to adjust your saved report configurations. > • A new Transaction Association dialog, available from the new > Update Transaction Association item in the register context menu, provides > the ability to have multiple associations for a single transaction. > Associations may now be easily removed. > • Allow Associations to be added to invoices. The actual > association when present is added as a link button which is shown below the > notes. > • A symbol is now displayed on transactions in the register when > they have an attachment and the selected font supports the symbol. > • The OFX file importer can now import more than one file at a > time. > • A new report menu supbmenu Multicolumn contains the old > custom-multicolumn report and a new Dashboard report containing Account > reports for expenses and income, an income-expense chart, and an account > summary. > • When importing, the matcher will no longer offer to match a > transaction to one that has already matched in a previous import, nor will > it offer to match more than one imported transaction to a single existing > transaction. > • Support for UK VAT and Australian GST added to the Income-GST > report. The reports options are changed from source accounts to source > sales and purchase accounts to permit proper reporting of capital > purchases. N.B. This is incompatible with previous versions of the report >
[GNC-dev] GnuCash 3.904 Released
The GnuCash development team announces GnuCash 3.904, the third testing release for what will soon be GnuCash 4.0. Changes Baseline requirements Operating Systems: • Linux: Ubuntu 18.04LTS • MacOS: 10.13 • Windows: 8.1 Software Dependencies: • C++ standard is now C++17, requires gcc 8.0 or clang 6.0. • Cmake 3.10 • boost 1.67.0 • gettext 0.19.6 for general use, 0.20 to generate gnucash.pot. • glib-2.0 2.56.1, gtk 3.22.30 • googletest 1.8.0 • ICU, any version. • libdbi 0.8.3 • libxml2 2.9.4 • swig 3.0.12 Now required for building from tarballs as well as from git. • Webkit 2.4.11 Mac & Win32, 2.14.1 Linux/BSD New Features 3.903 was the feature-freeze release. However, the command-line arguments for both gnucash and gnucash-cli have been adjusted as follows: • --add-price-quotes is changed to --quotes get • --run-reports is changed to --report run --name • Added --report list to produce a list of available reports. • Added --report show --name to describe the options changed from the default values in the named report. The intent is to have command categories with subcommands to better enable a richer command line capability as illustrated with the new report commands list and show. • A new separate executable, gnucash-cli (gnucash-cli.exe on Microsoft Windows) for doing command-line things like updating the prices in your book. gnucash-cli gains the ability to run reports from the command line. Specify reports to run by name or guid. It also provides an export format and an output file name without which it will output the report to stdout. • gnucash --report run --name=[reportname/guid] datafile.gnucash • gnucash --report run --name=[reportname/guid] --output-file=x.html datafile.gnucash • gnucash --report run --name=[reportname/guid] --output-file=x.html --export-type=TYPE datafile.gnucash • When deleting accounts the destination accounts of moved splits will be checked to ensure that they have the same commodity as the source account. If they don't you'll get a warning and the opportunity to pick another account or to carry on regardless. • New type-ahead search added to sequential search when selecting an account in the register: Instead of typing the first few characters of a top level account, the separator, the first few characters of the next level account and so on you may instead type a few characters of any part of a full account name and the drop-list will be filtered to contain only matching accounts. Once you have a small enough list you can use the arrow keys to select the account that you want. • Python bindings are now localized and their strings available for translation. • The new reports introduced in the Experimental Reports menu are moved to the main menu and the old reports hidden; the old reports can be unhidden by running GnuCash from the commandline with the --extra argument. That will cause the old reports to appear in their regular locations on the menu labeled (legacy). Note that new reports use different options and layouts and you may need to adjust your saved report configurations. • A new Transaction Association dialog, available from the new Update Transaction Association item in the register context menu, provides the ability to have multiple associations for a single transaction. Associations may now be easily removed. • Allow Associations to be added to invoices. The actual association when present is added as a link button which is shown below the notes. • A symbol is now displayed on transactions in the register when they have an attachment and the selected font supports the symbol. • The OFX file importer can now import more than one file at a time. • A new report menu supbmenu Multicolumn contains the old custom-multicolumn report and a new Dashboard report containing Account reports for expenses and income, an income-expense chart, and an account summary. • When importing, the matcher will no longer offer to match a transaction to one that has already matched in a previous import, nor will it offer to match more than one imported transaction to a single existing transaction. • Support for UK VAT and Australian GST added to the Income-GST report. The reports options are changed from source accounts to source sales and purchase accounts to permit proper reporting of capital purchases. N.B. This is incompatible with previous versions of the report and will require regenerating saved configurations. • Add option to save Layout for Business items Add two menu items under windows, one to save an existing layout for Invoices, Bills and Vouchers to their respective default layouts so the user set column widths will be used. The
Re: [GNC-dev] Feedback on GnuCash 3.903
David, Thanks for trying and the feedback, will try and answer your points... 1) The program default widths have not changed and are based on example strings in code. So for the account / transfer column it is based on "Expenses:Automobile:Gasoline" plus some space for the button. I added those accounts to my test book and it fitted exactly. 2) Same thing here but it is based on a number, "999,999.000". I did fix the double clicking on the header but you need the highlighted line to be on the transaction as opposed to the splits. Not sure I understand the second point. 3) Do not know why that is, you should be able to adjust the column widths and they will be remembered as before, this aspect has not been touched. The scheduled transactions template is based on the REG_TYPE_GROUP_JOURNAL group so go to 'Tools->General Journal' and setup the desired widths from there. Will see if I can add the menu options to the template window. On Sun, 7 Jun 2020 at 00:29, David H wrote: > Hi Robert/Geert, > > Thanks for that. I only use Gnucash for my personal expenses so it looks > like I'm only using the first register group. I've installed 3.903 and am > happy that my use case apart from scheduled transactions is generally > unaffected so will leave installed and continue using and if anything pops > out of the woodwork I'll post something here if that's the way to go. > > For your info my setup is Win 10 Pro and I'm running gnucash on a 27" > monitor at 1920 x 1080 res and I always run it full screen. Dual monitor > with laptop screen as secondary display. > > A few minor things I did notice are as follows :- > > 1. Reverting to default on a register seems to shrink the Transfer column > down a lot further than I expected and really truncates the column. > 2. When I review scheduled Created Transactions and revert to default it > also cuts off the left side of the "Tot Funds In" and "Tot Funds Out" > columns (see pic attached). Also if I close without saving after reverting > to default when Gnucash restarts and recreates the txn's it doesn't pick up > the new default it seems to remain on the reverted view with the truncated > columns. This is also after I go to another account register with good > columns and click on use as default for this group so it's like it's become > orphaned from the defaults. > 3. My list of scheduled txns seems to have shrunk the Name column. Also > in all of the template transactions the account column has shrunk right > down and the Windows menu when you're in the template editor doesn't > include the new register default entries which leads me to thinks this is > possibly an unintended consequence and since I've got a lot of these I'm > probably have to go and re-adjust each one :-( > 4. If I go in and change the widths of some columns and then scroll up a > couple of pages of txns and decide "meh this isn't looking so good" I just > close the register and re-open it to get the defaults back so that's good. > > Thanks David. > > > > > On Sat, 6 Jun 2020 at 18:34, Robert Fewell <14ubo...@gmail.com> wrote: > >> David, >> There are 6 different layouts that all registers are based on as >> described below... >> >> REG_TYPE_GROUP_CURRENCY; >> BANK_REGISTER: >> CASH_REGISTER: >> ASSET_REGISTER: >> CREDIT_REGISTER: >> LIABILITY_REGISTER: >> INCOME_REGISTER: >> EXPENSE_REGISTER: >> EQUITY_REGISTER: >> TRADING_REGISTER: >> >> REG_TYPE_GROUP_APAR; >> PAYABLE_REGISTER: >> RECEIVABLE_REGISTER: >> >> REG_TYPE_GROUP_JOURNAL; >> INCOME_LEDGER: >> GENERAL_JOURNAL: >> SEARCH_LEDGER: >> >> REG_TYPE_GROUP_STOCK; >> STOCK_REGISTER: >> CURRENCY_REGISTER: >> >> REG_TYPE_GROUP_PORTFOLIO; >> PORTFOLIO_LEDGER: >> >> Opening sub accounts uses the Portfolio layout. >> >> On Sat, 6 Jun 2020 at 00:31, David H wrote: >> >>> Geert, >>> >>> Thanks for your explanation but I still don't understand what the 6 >>> different register types you refer to are - can you point me to where >>> these >>> are described? >>> >>> My reason for having different column widths is as previously posted ... >>> >>> "... I have 2 savings accounts and 4 credit card accounts that I have >>> open >>> all the time and over the years I've gone to the trouble of setting these >>> up just the way I like them. Of course flicking through the register >>> tabs >>> the columns aren't all in the same places as I'm using accounts with >>> different nesting levels in each so the Transfer column widths vary even >>> within each account type. Are you saying that these would be treated as >>> 2 >>> register types and you are going to blow away all my good work and just >>> randomly choose one of the open settings as the default when you remove >>> old >>> configurations? " >>> >>> Why do I like things just the way they are ? Well it generally depends >>> on >>> the level of nesting in my EXPENSES category - some of them are nested >>> to 6 >>> levels deep so the TRANSFER column is wider in a couple of these >>> registers >>> and the
