That's great news!
I've collected the links I found so far to this issue:
https://bugs.gnucash.org/show_bug.cgi?id=796019
It is now closed since the AppImage is there and there are ongoing efforts in
getting an official Flatpak image.
> Sent: Friday, January 11, 2019 at 6:34 PM
> From: "Derek
He he, just to make things a bit more complicated and realistic:
> Sent: Sunday, May 13, 2018 at 6:42 PM
> From: "John Ralls"
> To: "Adrien Monteleone"
> Cc: gnucash-devel@gnucash.org
> Subject: Re: [GNC-dev] pricedb policy
>
> Just get local
I'll add a simple case that maybe does not happen often in real accounting but
happens to me all the time.
When traveling and exchanging cash at various small shops, the exchange rate
varies wildly. This, however, should not have the precedence compared to the
official central bank's rate.
Jeffrey, perhaps a stupid question - why don't you install a native linux
version of GnuCash instead of running a Windows version under Wine?
I use the same xml/sql book with linux and windows versions interchangably and
there are no issues (that I can see, at least!).
Also, just for
Frank, thanks a lot. Yes, the new captcha works great!
> Sent: Thursday, April 12, 2018 at 4:47 PM
> From: "Frank H. Ellenberger"
> To: cicko
> Cc: gnucash-devel@gnucash.org, "Derek Atkins"
> Subject: [GNC-dev] Captcha; was:
Thanks for the info, Adrien.
So far I managed to paint most of the application dark by using the * selector
only. It is a bit draconian but things are dark, alright.
Hopefully we can figure out additional selectors for borders and other elements.
The example css for register is a good start for
The recommended link for upgrade info:
g.co/recaptcha/upgrade
> > > - captcha
> > > Captcha on wiki reports that the v1 is to be deprecated soon.
> >
> > Where do you get this ? I don't see this when logging in to our wiki or
> > editing pages. Perhaps because I'm a developer ?
>
> Sent: Thursday, March 29, 2018 at 10:16 AM
> From: "Geert Janssens" <geert.gnuc...@kobaltwit.be>
> To: gnucash-devel@gnucash.org
> Cc: "Alen Siljak" <alen.sil...@gmx.com>
> Subject: Re: Feedback about 2.7.8
>
> Op donderdag 29 maart 2018 1
Soon as in the day after tomorrow!
(just read the warning message again)
> Sent: Thursday, March 29, 2018 at 10:00 AM
> From: "Alen Siljak" <alen.sil...@gmx.com>
> To: "David Carlson" <david.carlson@gmail.com>
> Cc: "GNUCASH devel" <
A few questions/suggestions:
- captcha
Captcha on wiki reports that the v1 is to be deprecated soon.
- gtk3 page.
I've created a Wiki entry for GTK3 with the main idea being sharing tips about
customization - https://wiki.gnucash.org/wiki/GTK3. This is also related to the
issue
> Sent: Wednesday, March 28, 2018 at 3:46 PM
> From: "Christoph R"
> To: gnucash-devel
> Subject: Feedback about 2.7.8
> But I can change the description of a reconciled split without a warning. I
> need to file a bug report on that.
;John Ralls" <jra...@ceridwen.us>
> To: "Julian Wollrath" <jwollr...@web.de>
> Cc: gnucash-devel@gnucash.org
> Subject: Re: [PATCH] Switch to python 3
>
> For further discussion here, though, particularly for Sébastien de Menten and
> Alen Siljak: Is
> Sent: Tuesday, February 13, 2018 at 8:13 AM
> From: "Wm via gnucash-devel"
> To: gnucash-de...@lists.gnucash.org
> Subject: Re: price.date, transaction.post_date and neutral time
>
> That is interesting. There has been quite a lot of enthusiasm for
> mobile / gnc
> Sent: Monday, February 12, 2018 at 7:34 PM
> From: "Wm via gnucash-devel" <gnucash-devel@gnucash.org>
> To: gnucash-de...@lists.gnucash.org
> Subject: Re: price.date, transaction.post_date and neutral time
>
> On 12/02/2018 14:27, Alen Siljak wrote:
> >
This is interesting information.
I am currently separating the Asset Allocation logic into its own
Python package, for direct use (cli) and potential library reuse
between GnuCash Portfolio and an Android app (perhaps an add-on for
MoneyManagerEx or who knows where it leads).
In
He he
Thanks a lot for the tips. I'm in touch with Sebastien in order to
polish the ledger export script. It is available either directly
(pc-export has been renamed to export.py) or through piecash cli
("piecash ledger" is the command if I remember well).
Hopefully over the
Thanks, David. I'm refraining from deleting any text unless it is
glaringly obvious that it is wrong.
What I'm trying to do is to link various related pieces of information
together. As you say, sometimes it can be contradictory because one
side is quite outdated. I believe that,
In my quest to call GnuCash functions from Python (or C#), I ran across
Boost.Python
(http://www.boost.org/doc/libs/1_66_0/libs/python/doc/html/index.html).
What are the chances that this would work with GnuCash .dlls on
Windows? Has anyone had any experience and willing to share?
lt;geert.gnuc...@kobaltwit.be>
To: gnucash-devel@gnucash.org
Cc: "Alen Siljak" <alen.sil...@gmx.com>
Subject: Re: Beyond 2.8 - some design thoughts
I do agree up to some point. I consider the scheme I propose to be
mostly a
simplified form of the semantic versio
To me, as an outsider and an occassional tester, Semantic Versioning
would make much more sense than any other custom versioning system.
Simply because it is getting common across various software packages
and libraries. It might work for the GUI application as well, when
referring
To get back to Sebastien's question: this does seem like a breaking
change at this stage. Going back to 2.6.19 with the database where a
few transactions have been entered in 2.7.2 shows the dates as
1970-01-01.
>Alen,
>
>Oh yeah, SQLite3. That doesn’t have a date type so the
u work on improving the
GnuCash python bindings and use those.
Regards,
John Ralls
\On Dec 20, 2017, at 12:37 PM, Alen Siljak <[1]alen.sil...@gmx.com>
wrote:
John,
With 2.7.2, the datetime field in sqlite3 database has increased to
19
chars, as Sebastien reported. Th
John,
With 2.7.2, the datetime field in sqlite3 database has increased to 19
chars, as Sebastien reported. The new format is -mm-dd HH:MM:ss
instead of mmddHHMMss.
It appears that the application can read both formats in a book and
that part is not a problem.
23 matches
Mail list logo