Re: [GNC-dev] Missing FreeType2 for Mac OS Development
While you're getting familiar enough with GnuCash ask questions here. Once you've got a PR written we can move the discussion to that PR. Regards, John Ralls > On Jan 14, 2023, at 4:21 PM, Vincent Lucarelli > wrote: > > It looks like freetype2 picked up a dependency on > /opt/homebrew/lib/libbrotlidec.dylib even though I started with a new user > account and insulated the build with >> >> cmakeargs = >> '-DCMAKE_SYSTEM_IGNORE_PATH="/opt/homebrew:/opt/macports:/sw:/usr/local"' > as suggested at > https://wiki.gnome.org/action/show/Projects/GTK/OSX/Building#Prerequisites > > > So when harfbuzz-no-cairo tried to configure against freetype2, it was > looking for libbrotlidec.pc, but that wasn’t built by jhbuild. > > I’ll try again tomorrow to see if I can track down exactly how homebrew is > poisoning the build environment. > > Provided I can actual build gnucash, should development questions about > integrating FQ get_features() take place on this mailing list in a new thread > or on GitHub under and issue? > > Best, > > Vince > > >> On Jan 14, 2023, at 4:44 PM, John Ralls wrote: >> >> >> >>> On Jan 14, 2023, at 10:22 AM, Vincent Lucarelli >>> wrote: >>> >>> Hi, >>> >>> I am attempting to setup a new Mac OS X user account on Ventura 13.0.1 to >>> build gnucash so I can attempt to help integrate a new Finance::Quote >>> feature into GnuCash. Ran into 2 problems following the instructions at >>> https://wiki.gnucash.org/wiki/MacOS/Quartz >>> >>> First issue - was able to solve - copying /bin/bash to $HOME/.new_local/bin >>> doesn’t seem to work on Ventura. The process is immediately killed when >>> the alternate copy of bash is run. Some googling suggests it might have >>> something to do with quarantine or code signing, but a few of the suggested >>> solutions didn’t work. I have homebrew installed (but not in the path for >>> the account I’m using to try and build gnucash), so I just installed bash >>> with brew and then copied that executable into .new_local/bin. >>> >>> Second issue - not sure how to proceed. The bootstrap run successfully, >>> but the jhbuild step failed to find freetype2 >>> PREFIX=$HOME/opt/gnucash jhbuild build >>> ../../src/harfbuzz-4.1.0/meson.build:87:0: ERROR: Dependency 'freetype2' is required but not found. A full log can be found at /Users/gnucash/opt/gnucash/build/harfbuzz-4.1.0/meson-logs/meson-log.txt WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated. *** Error during phase configure of harfbuzz-no-cairo: ## Error running meson --prefix /Users/gnucash/opt/gnucash/inst --libdir lib -Dcoretext=enabled -Dfreetype=enabled -Ddocs=disabled -Dbenchmark=disabled -Dintrospection=disabled --wrap-mode=nofallback /Users/gnucash/opt/gnucash/src/harfbuzz-4.1.0 *** [20/76] [1] Rerun phase configure [2] Ignore error and continue to build [3] Give up on module [4] Start shell [5] Reload configuration [6] Go to phase "wipe directory and start over" choice: >>> >>> Any advice how how to proceed is appreciated. >> >> harfbuzz-no-cairo depends on freetype-no-harfbuzz. If >> $PREFIX/lib/pkgconfig/freetype2.pc isn't installed then something went wrong >> with the latter. Scroll back in your terminal session to see what. >> >> Regards, >> John Ralls > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Missing FreeType2 for Mac OS Development
It looks like freetype2 picked up a dependency on /opt/homebrew/lib/libbrotlidec.dylib even though I started with a new user account and insulated the build with > > cmakeargs = > '-DCMAKE_SYSTEM_IGNORE_PATH="/opt/homebrew:/opt/macports:/sw:/usr/local"' as suggested at https://wiki.gnome.org/action/show/Projects/GTK/OSX/Building#Prerequisites So when harfbuzz-no-cairo tried to configure against freetype2, it was looking for libbrotlidec.pc, but that wasn’t built by jhbuild. I’ll try again tomorrow to see if I can track down exactly how homebrew is poisoning the build environment. Provided I can actual build gnucash, should development questions about integrating FQ get_features() take place on this mailing list in a new thread or on GitHub under and issue? Best, Vince > On Jan 14, 2023, at 4:44 PM, John Ralls wrote: > > > >> On Jan 14, 2023, at 10:22 AM, Vincent Lucarelli >> wrote: >> >> Hi, >> >> I am attempting to setup a new Mac OS X user account on Ventura 13.0.1 to >> build gnucash so I can attempt to help integrate a new Finance::Quote >> feature into GnuCash. Ran into 2 problems following the instructions at >> https://wiki.gnucash.org/wiki/MacOS/Quartz >> >> First issue - was able to solve - copying /bin/bash to $HOME/.new_local/bin >> doesn’t seem to work on Ventura. The process is immediately killed when the >> alternate copy of bash is run. Some googling suggests it might have >> something to do with quarantine or code signing, but a few of the suggested >> solutions didn’t work. I have homebrew installed (but not in the path for >> the account I’m using to try and build gnucash), so I just installed bash >> with brew and then copied that executable into .new_local/bin. >> >> Second issue - not sure how to proceed. The bootstrap run successfully, but >> the jhbuild step failed to find freetype2 >> >>> PREFIX=$HOME/opt/gnucash jhbuild build >> >>> ../../src/harfbuzz-4.1.0/meson.build:87:0: ERROR: Dependency 'freetype2' is >>> required but not found. >>> >>> A full log can be found at >>> /Users/gnucash/opt/gnucash/build/harfbuzz-4.1.0/meson-logs/meson-log.txt >>> WARNING: Running the setup command as `meson [options]` instead of `meson >>> setup [options]` is ambiguous and deprecated. >>> *** Error during phase configure of harfbuzz-no-cairo: ## Error >>> running meson --prefix /Users/gnucash/opt/gnucash/inst --libdir lib >>> -Dcoretext=enabled -Dfreetype=enabled -Ddocs=disabled -Dbenchmark=disabled >>> -Dintrospection=disabled --wrap-mode=nofallback >>> /Users/gnucash/opt/gnucash/src/harfbuzz-4.1.0 *** [20/76] >>> >>> [1] Rerun phase configure >>> [2] Ignore error and continue to build >>> [3] Give up on module >>> [4] Start shell >>> [5] Reload configuration >>> [6] Go to phase "wipe directory and start over" >>> choice: >> >> Any advice how how to proceed is appreciated. > > harfbuzz-no-cairo depends on freetype-no-harfbuzz. If > $PREFIX/lib/pkgconfig/freetype2.pc isn't installed then something went wrong > with the latter. Scroll back in your terminal session to see what. > > Regards, > John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Missing FreeType2 for Mac OS Development
> On Jan 14, 2023, at 10:22 AM, Vincent Lucarelli > wrote: > > Hi, > > I am attempting to setup a new Mac OS X user account on Ventura 13.0.1 to > build gnucash so I can attempt to help integrate a new Finance::Quote feature > into GnuCash. Ran into 2 problems following the instructions at > https://wiki.gnucash.org/wiki/MacOS/Quartz > > First issue - was able to solve - copying /bin/bash to $HOME/.new_local/bin > doesn’t seem to work on Ventura. The process is immediately killed when the > alternate copy of bash is run. Some googling suggests it might have > something to do with quarantine or code signing, but a few of the suggested > solutions didn’t work. I have homebrew installed (but not in the path for the > account I’m using to try and build gnucash), so I just installed bash with > brew and then copied that executable into .new_local/bin. > > Second issue - not sure how to proceed. The bootstrap run successfully, but > the jhbuild step failed to find freetype2 > >> PREFIX=$HOME/opt/gnucash jhbuild build > >> ../../src/harfbuzz-4.1.0/meson.build:87:0: ERROR: Dependency 'freetype2' is >> required but not found. >> >> A full log can be found at >> /Users/gnucash/opt/gnucash/build/harfbuzz-4.1.0/meson-logs/meson-log.txt >> WARNING: Running the setup command as `meson [options]` instead of `meson >> setup [options]` is ambiguous and deprecated. >> *** Error during phase configure of harfbuzz-no-cairo: ## Error >> running meson --prefix /Users/gnucash/opt/gnucash/inst --libdir lib >> -Dcoretext=enabled -Dfreetype=enabled -Ddocs=disabled -Dbenchmark=disabled >> -Dintrospection=disabled --wrap-mode=nofallback >> /Users/gnucash/opt/gnucash/src/harfbuzz-4.1.0 *** [20/76] >> >> [1] Rerun phase configure >> [2] Ignore error and continue to build >> [3] Give up on module >> [4] Start shell >> [5] Reload configuration >> [6] Go to phase "wipe directory and start over" >> choice: > > Any advice how how to proceed is appreciated. harfbuzz-no-cairo depends on freetype-no-harfbuzz. If $PREFIX/lib/pkgconfig/freetype2.pc isn't installed then something went wrong with the latter. Scroll back in your terminal session to see what. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[GNC-dev] Missing FreeType2 for Mac OS Development
Hi, I am attempting to setup a new Mac OS X user account on Ventura 13.0.1 to build gnucash so I can attempt to help integrate a new Finance::Quote feature into GnuCash. Ran into 2 problems following the instructions at https://wiki.gnucash.org/wiki/MacOS/Quartz First issue - was able to solve - copying /bin/bash to $HOME/.new_local/bin doesn’t seem to work on Ventura. The process is immediately killed when the alternate copy of bash is run. Some googling suggests it might have something to do with quarantine or code signing, but a few of the suggested solutions didn’t work. I have homebrew installed (but not in the path for the account I’m using to try and build gnucash), so I just installed bash with brew and then copied that executable into .new_local/bin. Second issue - not sure how to proceed. The bootstrap run successfully, but the jhbuild step failed to find freetype2 > PREFIX=$HOME/opt/gnucash jhbuild build > ../../src/harfbuzz-4.1.0/meson.build:87:0: ERROR: Dependency 'freetype2' is > required but not found. > > A full log can be found at > /Users/gnucash/opt/gnucash/build/harfbuzz-4.1.0/meson-logs/meson-log.txt > WARNING: Running the setup command as `meson [options]` instead of `meson > setup [options]` is ambiguous and deprecated. > *** Error during phase configure of harfbuzz-no-cairo: ## Error > running meson --prefix /Users/gnucash/opt/gnucash/inst --libdir lib > -Dcoretext=enabled -Dfreetype=enabled -Ddocs=disabled -Dbenchmark=disabled > -Dintrospection=disabled --wrap-mode=nofallback > /Users/gnucash/opt/gnucash/src/harfbuzz-4.1.0 *** [20/76] > > [1] Rerun phase configure > [2] Ignore error and continue to build > [3] Give up on module > [4] Start shell > [5] Reload configuration > [6] Go to phase "wipe directory and start over" > choice: Any advice how how to proceed is appreciated. Thanks, Vince ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Sample Report with Examples
All good suggestions. Let's see how many are reasonable for flywire to pick up and fix. (flywire, I have no idea of your skill level and willingness to work on this...) I would already take partial fixes as a step in the good direction. Regards, Geert Op zaterdag 14 januari 2023 16:58:09 CET schreef john: > Geert, > > Roger. The problem with that argument is that someone with that little > programming experience isn't going to be able to write a custom report > anyway. Even someone with enough programming experience to agree that > default option values aren't significant to the structure of the code isn't > going to be able to write a custom report unless at least some of that > experience is in one of the Lispish languages. The Lispish paradigms of > car, cdr, lambda, map, and so on are utterly foreign to most procedural > language programmers, but required for writing GnuCash reports. > > Yes, the use of Hello, World is a bit flippant, and yes, hello-world.scm > isn't a minimal Scheme program. It's also not a sample report because it > doesn't demonstrate querying the GnuCash data performing analysis, or > presenting results. So if someone feels motivated to make it less flippant > and better described then I suggest: > > * Change the filename to options-example.scm, and the menu-name to "Options > Example". * Add a report title option. Most of the real reports have one. > Set its default to "Example Title". * Fix the comment describing the value > of `name from "This will be used, among other things for making its menu > item in the main menu.". It doesn't do that, it sets the name on the > options dialog's title bar and the default value for the General section's > Report Name option. "menu-name", which is part of the report-registration > block at the bottom, sets the menu name. The comment should also explain > that changing the report name option will change the value of the report's > window or tab title but not its options dialog title. * Change the name > value to "Options Example Report". > * Change the two Hello… section names to something like Tab A and Tab B to > make clear that "Sections" in the option block map to tabs on the dialog > box. * Change the string option default to "String Option Default". > * Speaking of the General section, there should be a comment explaining that > a skeleton General section gets added by gnc:report-template-new-options > that provides the name (but not the title, reports must add that > themselves) and stylesheet options. > > Regards, > John Ralls > > > On Jan 14, 2023, at 2:02 AM, Geert Janssens > > wrote: > > > > Ok, I tend to agree partially with flywire on this one. > > > > John, you and I have years of programming experience and to us the default > > value of an option is a minor detail. > > > > However I can imagine someone with hardly any development experience at > > all will have a much harder time to map the same string used multiple > > times in the report code to the output visible on screen. And I > > sympathize with those that try to create their own custom reports. So > > yes, using different sample strings in code (even for default values) > > makes it easier to relate output on the report with what's written in the > > code - before - any option is changed. > > > > To us this may look like bikeshedding, I think for someone trying to wrap > > their head around the gnucash code this may actually help. > > > > And while bikeshedding was mentioned, I'd rather use values like > > "Sample string", "Sample Document Title" and "Sample Report" than the > > half-baked "Hello String" and "Hello Example". ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Sample Report with Examples
Geert, Roger. The problem with that argument is that someone with that little programming experience isn't going to be able to write a custom report anyway. Even someone with enough programming experience to agree that default option values aren't significant to the structure of the code isn't going to be able to write a custom report unless at least some of that experience is in one of the Lispish languages. The Lispish paradigms of car, cdr, lambda, map, and so on are utterly foreign to most procedural language programmers, but required for writing GnuCash reports. Yes, the use of Hello, World is a bit flippant, and yes, hello-world.scm isn't a minimal Scheme program. It's also not a sample report because it doesn't demonstrate querying the GnuCash data performing analysis, or presenting results. So if someone feels motivated to make it less flippant and better described then I suggest: * Change the filename to options-example.scm, and the menu-name to "Options Example". * Add a report title option. Most of the real reports have one. Set its default to "Example Title". * Fix the comment describing the value of `name from "This will be used, among other things for making its menu item in the main menu.". It doesn't do that, it sets the name on the options dialog's title bar and the default value for the General section's Report Name option. "menu-name", which is part of the report-registration block at the bottom, sets the menu name. The comment should also explain that changing the report name option will change the value of the report's window or tab title but not its options dialog title. * Change the name value to "Options Example Report". * Change the two Hello… section names to something like Tab A and Tab B to make clear that "Sections" in the option block map to tabs on the dialog box. * Change the string option default to "String Option Default". * Speaking of the General section, there should be a comment explaining that a skeleton General section gets added by gnc:report-template-new-options that provides the name (but not the title, reports must add that themselves) and stylesheet options. Regards, John Ralls > On Jan 14, 2023, at 2:02 AM, Geert Janssens > wrote: > > Ok, I tend to agree partially with flywire on this one. > > John, you and I have years of programming experience and to us the default > value of an option is a minor detail. > > However I can imagine someone with hardly any development experience at all > will have a much harder time to map the same string used multiple times in > the report code to the output visible on screen. And I sympathize with those > that try to create their own custom reports. So yes, using different sample > strings in code (even for default values) makes it easier to relate output on > the report with what's written in the code - before - any option is changed. > > To us this may look like bikeshedding, I think for someone trying to wrap > their head around the gnucash code this may actually help. > > And while bikeshedding was mentioned, I'd rather use values like > "Sample string", "Sample Document Title" and "Sample Report" than the > half-baked "Hello String" and "Hello Example". > > As with these changes "Hello, World" is never used, the file name is probably > better changed as well. > > Regards, > > Geert > > Op zaterdag 14 januari 2023 05:47:29 CET schreef john: > > > On Jan 13, 2023, at 6:46 PM, flywire wrote: > > > > > > The point is not about the changes options make to reports, it's about how > > > the report source code changes the report and report options. Why > > > wouldn't unique string values help people unfamiliar with reports see the > > > relationship more clearly? > > While it's possible in Scheme to take that quoted option value and convert > > it to code I don't know of any report code in GnuCash that does so. That's > > a very good thing, we have enough Scheme-induced vulnerabilities without > > that. > > > > With that in mind, no, the quoted-string default values do not in any way > > have anything to do with illustrating how the report source code changes > > the report and report options. Nor, for that matter, does hello-world.scm > > illustrate anything of the sort. hello-world.scm simply provides examples > > of the different types of options and very simply displays the values in > > the report. There's not a single line of code that changes the behavior of > > the report based on an option value--unlike many of the real options in > > most of the real reports. > > > > Regards, > > John Ralls > > > > ___ > > 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] Sample Report with Examples
Hi again, Am 14.01.23 um 13:19 schrieb flywire: I've made that change in my fork as well Did you also adjust test-stress-options? if failed in your previous PR. See e.g. https://github.com/Gnucash/gnucash/actions/runs/3909419637/jobs/6688757781 Regards Frank ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Sample Report with Examples
Hi, Am 14.01.23 um 13:19 schrieb flywire: renamed file to sample-report.scm. perhaps options-sample.scm would fit better? ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] GnuCash 4.900 Released
For information, I have updated my windows build machine and successfully built the current master 4.900 version which resulted in a file size of 150M. With an existing install of 4.13, I was able to install my 4.900 version resulting in no errors in the trace file. I was also able to install the current nightly master version successfully. Also tried to do the same on my Windows 11 VM, again starting from 4.13 was able to successfully install my version and also the nightly master version. Regards, Bob On Fri, 13 Jan 2023 at 23:50, David H wrote: > Hi again John and Devs, > > I've just updated my Ubuntu 22.10 flatpak to the Gnucash 4.900 beta and am > having the same issues as on Win 10. Attached are trace files from each OS > in case it helps. > > Regards David H > > > On Thu, 12 Jan 2023 at 08:25, David H wrote: > > > Hi John and devs, > > > > Thanks for the update. I had a number of problems as per the following:- > > > > System > > --- > > > > Lenovo laptop, Intel i5, 8 Gb ram, Gnucash 4.13 / Finance Quote 1.54 / > Win > > 10 Pro, Version 22H2, OS Build 19044.2486, Win32 strawberry-perl 5.32.1.1 > > #1 Sun Jan 24 12:17:47 2021 i386 > > > > Process > > > > > > Installed 4.900 which auto uninstalled 4.13. > > Started Gnucash 4.900 which displayed the "Tip of The Day" and then the > > "Welcome to Gnucash" dialogs. > > Unfortunately Gnucash 4.900 didn't seem to find my xml data file and the > > Most Recent file list just displays "RecentFile0Action" (Function name?) > > instead of the usual 2-3 file names. > > Manually opened the last file used which is just a copy of my usual > > Gnucash file, it opened fine and re-displayed all the tabs that were > > previously open. > > Got the message about the Budget amounts being fixed during the open > > process. > > It doesn't seem to be finding my saved report options - the report names > > are included in the save report config list but no options and the > Accounts > > Selected has reverted to all accounts. > > Get quotes is now not working - the button is simply greyed out. > > Like Glenn I also can't turn off the Tip of the Day or the Display > Welcome > > Dialog Again? and on exiting and restarting Gnucash I repeatedly get > > prompted to Create a new set of accounts / Import my QIF files / Open the > > new user tutorial. > > > > Also yesterday I happened to update and save Report Options for a saved > > report configuration and it seemed Gnucash crashed, repeating the > process > > today did NOT result in a crash. > > > > Hope this helps and once again thanks to you and the other devs for all > > your hard work on Gnucash. > > > > Regards David H. > > > > > > > > > > > > > > On Tue, 10 Jan 2023 at 15:03, John Ralls wrote: > > > >> The GnuCash development team announces GnuCash 4.900, the first unstable > >> release leading to GnuCash 5.0. > >> > >> This is an unstable release for testing purposes. Do not use it with > >> production data! Make a copy of your book to test this release. > >> > >> New Features > >> > >> A new Stock Transaction Assistant to guide you through entering most > >> investment transactions for stocks, bonds, and mutual funds. You can > access > >> it from Actions>Stock Assistant when you have the Accounts page ora > Stock > >> or Fund account register open. > >> A new Investment Lots report showing a graph of capital gains and > >> losses in a period by investment lot. Note that if you don't use the > View > >> Lots dialog to manage capital gains and losses this report won't have > >> anything to show you. Use Reports>Assets & Liabilities>Investment Lots > to > >> see the report. > >> A new tab on the New/Edit Account dialog called More Properties > >> includes entries to set a high and low limit on an account. That's > coupled > >> to a new column that's available on the Accounts Page, Balance Limit. If > >> you set a high or low limit and the account balance falls above or below > >> the respective limit an indicator will be shown in the Balance Limit > column. > >> The description field quickfill in the register now displays a > >> drop-down list of possible completions instead of just one inline > >> completion. > >> File import menu items for the MT940, MT942, and DTAUS formats is > >> replaced with a single Import from AQBanking that supports importing any > >> file format supported by AQBanking, including the frequently requested > CAMT. > >> > >> Between 4.13 and 4.900, the following bugfixes were accomplished: > >> The following fixes will also appear in GnuCash 4.14: > >> > >> Bug 798588 - sx scrubbing was using incorrect free function > >> Bug 798625 - "Last up through report date" changed in 4.12 > >> Bug 798679 - Unicode normalization should be used for comparison but > >> not stored. > >> Bug 798702 - Crash in gnc_plugin_page_focus_idle_destroy() closing a > >> report before it completes. > >> Bug 798705 - New: UI string mismatch: OK vs. Next > >>
Re: [GNC-dev] Sample Report with Examples
Geert Janssens wrote: > I'd rather use values like "Sample string", "Sample Document Title" and > "Sample Report" > I've made that change in my fork as well as changed section to Sample! and renamed file to sample-report.scm. It looks good and not like a kludge. I'd also suggest: * minor format fixes and update references * Delete welcome-to-gnucash.scm given it was gutted in December 2017 Trivial updates would be needed for: https://www.gnucash.org/docs/v4/C/gnucash-help/report-create.html https://wiki.gnucash.org/wiki/index.php?title=Custom_Reports and https://wiki.gnucash.org/wiki/Report_GUIDs Need to check GnuCash repo for hello-world.scm references. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Sample Report with Examples
Ok, I tend to agree partially with flywire on this one. John, you and I have years of programming experience and to us the default value of an option is a minor detail. However I can imagine someone with hardly any development experience at all will have a much harder time to map the same string used multiple times in the report code to the output visible on screen. And I sympathize with those that try to create their own custom reports. So yes, using different sample strings in code (even for default values) makes it easier to relate output on the report with what's written in the code - before - any option is changed. To us this may look like bikeshedding, I think for someone trying to wrap their head around the gnucash code this may actually help. And while bikeshedding was mentioned, I'd rather use values like "Sample string", "Sample Document Title" and "Sample Report" than the half-baked "Hello String" and "Hello Example". As with these changes "Hello, World" is never used, the file name is probably better changed as well. Regards, Geert Op zaterdag 14 januari 2023 05:47:29 CET schreef john: > > On Jan 13, 2023, at 6:46 PM, flywire wrote: > > > > The point is not about the changes options make to reports, it's about how > > the report source code changes the report and report options. Why > > wouldn't unique string values help people unfamiliar with reports see the > > relationship more clearly? > While it's possible in Scheme to take that quoted option value and convert > it to code I don't know of any report code in GnuCash that does so. That's > a very good thing, we have enough Scheme-induced vulnerabilities without > that. > > With that in mind, no, the quoted-string default values do not in any way > have anything to do with illustrating how the report source code changes > the report and report options. Nor, for that matter, does hello-world.scm > illustrate anything of the sort. hello-world.scm simply provides examples > of the different types of options and very simply displays the values in > the report. There's not a single line of code that changes the behavior of > the report based on an option value--unlike many of the real options in > most of the real reports. > > Regards, > John Ralls > > ___ > 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] [GNC] GnuCash 4.900 Released
Op zaterdag 14 januari 2023 00:23:21 CET schreef Fred Tydeman: > On Fri, Jan 13, 2023 at 3:00 PM David H wrote: > > Yeah seems to be a typo which will cause the remote-add to fail if you > > already have the flathub repository installed as follows:- > > > > Wiki says - flatpak remote-add --user --if-not-exists *flathub* > > https://flathub.org/beta-repo/flathub-beta.flatpakrepo > > Should be - flatpak remote-add --user --if-not-exists *flathub-beta* > > https://flathub.org/beta-repo/flathub-beta.flatpakrepo > > Thanks. That fix lets me get farther. > I have done a fresh install of Fedora 37 with Gnome 43.2 on Intel 64-bit > CPU. > When I try to install the beta, I get an error saying that beta requires > runtime org.gnome.Platform/x86_64/43 > Is there some way to force the beta to use the system wide Gnome? No, you can't. Runtimes are a fundamental base concept of flatpaks (and snaps or appimages by the way) and you can't avoid them. These runtimes ensure that there's a known common set of libraries available on the system for the flatpak application to depend on, regardless of the state of the base system. Aside from allowing the application to install on systems that don't have the proper base system, it also eliminates a whole host of compatibility issues early on in the development process. Issues that otherwise have to be solved by distribution maintainers when they package the applications for the regular packaging system of said distro. Personally I think both systems (flatpaks vs distro packages) have their own distinct advantages and disadvantages. And I think both have their place. However in this particular scenario - distributing beta software for testing - I believe the isolation is actually a big advantage. So if you want to install the (beta) gnucash flatpak on your system you will also have to accept to install the required gnome runtime for it. If this is a hurdle for you, consider you can also only install it for as long as you want to beta test gnucash. You can easily remove this runtime together with the gnucash beta flatpak when you're done testing with the "flatpak uninstall" command. Regards, Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
