Re: [GNC-dev] Master now requires C++17
John, Defaults on Linux Mint 19.2 are: gcc 7.4.0 (gcc 8.3.0 is available for Ubuntu 18.04 (Bionic) at https://packages.ubuntu.com/bionic/gcc-8) clang6.0.0 libboost 1.65.1 (it will likely be patched as it is Ubuntu 18.04 based. There is also a ppa where libboost 1.67 is available for 18.04 https://asciinema.org/a/199344 if you are not averse to installing from non distro resources.) David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Mouse usage in Gnucash
Thanks Tommy, The gnome developers guide is a useful read in any case apart from the mouse specific issues. They seem to settle on the primary and secondary descriptions in one place and then use the left-click right-click etc, particularly in the glossary (https://developer.gnome.org/gdp-style-guide/2.32/gdp-style-guide.html#gnome-glossary-user-actions) description of user actions. It may be useful to link to this from the wiki on udpdating the documentation( see below). Perhaps a glossary may be a useful place to eventually include references/crossreferences to alternate actions. The current docbook glossary is not terribly useful for html documents as it simply displays a popup with the glossary term in it rather than the definition part of the glossary entry which would be really useful. That behavior could be altered by using some custon xslt processing in the build but I don't have any expertise in that as yet. At present the glossary exists only in the guide and not the help manual. There is a way of making a common glossary available in both but it will require some alteration of the build structure. I am avoiding that at the moment because I think it is more important to update the documentation in a few areas where there were new features in V3 and I don't have the expertise in the cmake and xslt processing to do it easily at the moment. This section is a pretty good guide to usage in developments and the organization of GTK3 https://developer.gnome.org/hig-book/unstable/input-mouse.html.en particularly the table of mouse and keyboard equivalents. The GDK reference manual refers to Button 1,2,3 with 1 Left 2 Middle and 3 Right but that is more related to usage in coding than in user documentation. There is no style guide in the Gnome documentation guide sense but there is the wiki on updating documentation (https://wiki.gnucash.org/wiki/Documentation_Update_Instructions) but it doesn't refer to mouse interaction descrptions. My inclination is to stay with left click, right click descriptions as for a two button mouse for the moment. It is probably more important to be consistent rather than totally compliant with being as general as possible. I think some general reference to the GTK3 input-mouse.html document would be useful as all the intefaces are based on it as well as https://developer.gnome.org/hig/stable/pointer-and-touch-input.html.en bu that is problematical as these are external references. If it is desired to change this a global search and replace can always be used and much of the current documentation uses a left click, right click convention David - David Cousens -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[GNC-dev] Master now requires C++17
After a bit of a false start last week I've set the master branch--the one that we'll release in a few months as GnuCash 4.0--to build its C++ files with C++17. >From a coding standpoint that pretty much affects only Geert and me: No one >else is actively working with C++. >From a building and using standpoint it means that you're going to need a >fairly recent distro or operating system release: The required compilers are >gcc 8.0 and clang 6.0, and boost must in general be 1.67 or later. I say in >general because we found that although Ubuntu 18.04 *nominally* ships with >boost 1.65, they've patched the one library (boost::locale) that had a C++17 >incompatibility until 1.67 so GnuCash builds. There may be others that have >done something similar. Other distros we tested on: Debian Buster, Bullseye, and Sid; Fedora 28, 29, and 30; OpenSuSE Tumbleweed (Leap 15.2 doesn't work). OpenBSD doesn't work (boost is too old). MacOS will require Sierra or later. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Mouse usage in Gnucash
The Gnome Documentation Style Gude says to refer to Left, Middle, and Right mouse buttons or clicks https://developer.gnome.org/gdp-style-guide/ KMymoney seems to use the same or similar convention https://kmymoney.org/documentation.php I know one of the things that generated the discussion was concern about tablets, touchpads, touchscreens or other non-mouse interactions... so I looked for the Android documentation style guide. My interpretation is they encourage writers to emphasize the task more than the mechanics. https://developers.google.com/style I had some more thoughts but I want to ponder them more carefully... And before I put my foot in my mouth... is there already a GnuCash documentation Style Guide, or some suggestions for writers? I vaguely recall seeing something, but I may be mistaken. On Sat, Oct 12, 2019 at 6:30 AM David Carlson wrote: > Are there examples in other major applications to compare to? > > > David Carlson > > On Fri, Oct 11, 2019, 11:33 PM D via gnucash-devel < > gnucash-devel@gnucash.org> wrote: > > > > > > > On October 12, 2019, at 3:45 AM, John Ralls wrote: > > > > > > > >> On Oct 10, 2019, at 10:26 PM, David Cousens > > > wrote: > > >> > > >> Do we by any chance have some sort of standard description of mouse > > usage in > > >> GNuCash on the various OS. > > >> > > >> I am updating documentation. Docbooks has tags for description of > mouse > > >> operations. With configurable mouses for LH or RH operation terms > like > > Left > > >> Click and Right Click start to become ambiguous. DocBooks has tags for > > >> . In a review of some recent changes Frank suggested > using > > >> Button1, Button2 and Button 3 rather than Left, Middle and Right to > > avoid > > >> the LH/RH mouse conundrum. I haven't been able to find anything in > the > > >> documentation re input devices but I could have missed it > > >> > > >> Two of my mice have 6 buttons and two scroll wheels (basic config is > a 2 > > >> button + central scroll/button) and another only has 2 buttons and a > > single > > >> scroll wheel/button. Linux Mint can configure that for LH operation, > > >> emulation of a centre button by pressing both buttons together, > > scrolling > > >> reversal and double click timeout and I presume most OSs will have > > something > > >> similar. Then we go to Macs and we have single buttons and magic mice > to > > >> contend with. Then there are tablets and touchpads and gestures. > GTK3 > > >> seems to support a wide range > > >> https://developer.gnome.org/gtk3/stable/chap-input-handling.html and > > does > > >> interpret the scroll wheel appropriately on my mice but the wheel > button > > >> inserts "another" each time it is pressed while editing a transaction > > in a > > >> register - not too useful. > > >> > > >> It is clearly far too onerous to describe all possible mice/input > > >> variations. > > >> > > >> My own preference would to perhaps settle on a fairly common 2 button > RH > > >> basic mouse and keyboard configuration and describe operations in > terms > > of > > >> that. Perhaps then offer in a wiki section some translations from this > > >> configuration to other configurations like track pads that could be > > >> populated by users. I think Left (Centre) Right for a RH mouse is > > likely to > > >> be far less confusing to translate than a "Button1 Button2, Button3 > > where > > >> it is totally ambiguous whether the mouse is LH RH or upside down. > > >> > > >David, > > >The middle-button behavior on Linux is an X-Windows thing: The right > > button begins a selection, the left button completes the selection, and > the > > middle button pastes the selection. I don't know if Wayland has that > > behavior as well. Gtk has a GdkSelection class to try to provide it on > > other Ones but it was implemented only partly on Windows and not at all > on > > MacOS. It's been deprecated for some time. > > >If you don't like "left click" or "click button 1", how about "primary > > click" and "secondary click"? You could even say "primary click/tap" to > > include the touchpad users. > > >I don't think that it's particularly useful for our documentation to try > > to teach users the basics of using their computers, and explaining > > everything at that level quickly gets tiresome for the majority of users > > who know how to click a button, select some text, or open a context menu. > > >Regards, > > >John Ralls > > >___ > > >gnucash-devel mailing list > > >gnucash-devel@gnucash.org > > >https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > > +1 to John's comments. > > > > I think it best to focus on the task, rather than the specific mechanics. > > > > David T. > > ___ > > gnucash-devel mailing list > > gnucash-devel@gnucash.org > > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > > ___ > gnucash-devel mailing
Re: [GNC-dev] Mouse usage in Gnucash
Are there examples in other major applications to compare to? David Carlson On Fri, Oct 11, 2019, 11:33 PM D via gnucash-devel < gnucash-devel@gnucash.org> wrote: > > > On October 12, 2019, at 3:45 AM, John Ralls wrote: > > > > >> On Oct 10, 2019, at 10:26 PM, David Cousens > wrote: > >> > >> Do we by any chance have some sort of standard description of mouse > usage in > >> GNuCash on the various OS. > >> > >> I am updating documentation. Docbooks has tags for description of mouse > >> operations. With configurable mouses for LH or RH operation terms like > Left > >> Click and Right Click start to become ambiguous. DocBooks has tags for > >> . In a review of some recent changes Frank suggested using > >> Button1, Button2 and Button 3 rather than Left, Middle and Right to > avoid > >> the LH/RH mouse conundrum. I haven't been able to find anything in the > >> documentation re input devices but I could have missed it > >> > >> Two of my mice have 6 buttons and two scroll wheels (basic config is a 2 > >> button + central scroll/button) and another only has 2 buttons and a > single > >> scroll wheel/button. Linux Mint can configure that for LH operation, > >> emulation of a centre button by pressing both buttons together, > scrolling > >> reversal and double click timeout and I presume most OSs will have > something > >> similar. Then we go to Macs and we have single buttons and magic mice to > >> contend with. Then there are tablets and touchpads and gestures. GTK3 > >> seems to support a wide range > >> https://developer.gnome.org/gtk3/stable/chap-input-handling.html and > does > >> interpret the scroll wheel appropriately on my mice but the wheel button > >> inserts "another" each time it is pressed while editing a transaction > in a > >> register - not too useful. > >> > >> It is clearly far too onerous to describe all possible mice/input > >> variations. > >> > >> My own preference would to perhaps settle on a fairly common 2 button RH > >> basic mouse and keyboard configuration and describe operations in terms > of > >> that. Perhaps then offer in a wiki section some translations from this > >> configuration to other configurations like track pads that could be > >> populated by users. I think Left (Centre) Right for a RH mouse is > likely to > >> be far less confusing to translate than a "Button1 Button2, Button3 > where > >> it is totally ambiguous whether the mouse is LH RH or upside down. > >> > >David, > >The middle-button behavior on Linux is an X-Windows thing: The right > button begins a selection, the left button completes the selection, and the > middle button pastes the selection. I don't know if Wayland has that > behavior as well. Gtk has a GdkSelection class to try to provide it on > other Ones but it was implemented only partly on Windows and not at all on > MacOS. It's been deprecated for some time. > >If you don't like "left click" or "click button 1", how about "primary > click" and "secondary click"? You could even say "primary click/tap" to > include the touchpad users. > >I don't think that it's particularly useful for our documentation to try > to teach users the basics of using their computers, and explaining > everything at that level quickly gets tiresome for the majority of users > who know how to click a button, select some text, or open a context menu. > >Regards, > >John Ralls > >___ > >gnucash-devel mailing list > >gnucash-devel@gnucash.org > >https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > +1 to John's comments. > > I think it best to focus on the task, rather than the specific mechanics. > > David T. > ___ > 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
