A brief search through list did not bring any results, so I decided to
start a new one.
First of all: no offence but most gnucash reports are poorly implemented.
It's not because they useless or looks not pretty (most of them are useful
and good, calm down :)) . The reason is that a model (i.e. da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Dimity,
we discussed that at the german mailinglist more than once ;-)
I have made solution wirth python-bindings and latex for my invoices and
the output is much better.
https://github.com/mwellnitz/gnucash-latex/
https://github.com/mwellnitz
On Wednesday 24 December 2014 12:22:46 Dmitry Pavlov wrote:
> A brief search through list did not bring any results, so I decided to
> start a new one.
>
> First of all: no offence but most gnucash reports are poorly
> implemented. It's not because they useless or looks not pretty (most
> of them
Geert, thank you for a very detailed comments.
I did't know that situation with python bindings is so complicated on
Windows and OSX, and that can be a real show stopper.
For the details of implementations my idea was slightly different: options
can be preserved for guile, as options definitions
On Wed, Dec 24, 2014 at 12:25:23PM +0100, Geert Janssens wrote:
> If I understand you correctly you want to separate the options from the
> report generating code ?
> So your wrapper script would be responsible for displaying the options to the
> user and the
> actual report script only gets th
Can you send link to your git repo with that changes?
24 дек. 2014 г. 18:39 пользователь "David Osguthorpe" <
david.osgutho...@gmail.com> написал:
> On Wed, Dec 24, 2014 at 12:25:23PM +0100, Geert Janssens wrote:
> > If I understand you correctly you want to separate the options from the
> report
On Wed, Dec 24, 2014 at 08:07:45PM +0400, Dmitry Pavlov wrote:
>Can you send link to your git repo with that changes?
>
Supposedly this is it
https://github.com/davidjo/gnucash_python.git
David
___
gnucash-devel mailing list
gnucash-devel@gnucash.
> On Dec 24, 2014, at 7:38 AM, David Osguthorpe
> wrote:
>
> (By the way note that GnuCash is multithreaded because Gtk is multi-threaded
> - in the initial
> implementation attempts I had issues with python GIL crashes but these
> dissappeared when I started
> using proper pygobject based im
> On Dec 24, 2014, at 12:22 AM, Dmitry Pavlov wrote:
>
> A brief search through list did not bring any results, so I decided to
> start a new one.
>
> First of all: no offence but most gnucash reports are poorly implemented.
> It's not because they useless or looks not pretty (most of them are
Personally, i'm still on file storage so based on that maybe it's a good
time now to look at sql one and try migrate to it and gain advantage of sql.
24 дек. 2014 г. 19:54 пользователь "John Ralls"
написал:
>
> > On Dec 24, 2014, at 12:22 AM, Dmitry Pavlov wrote:
> >
> > A brief search through l
On Wed, Dec 24, 2014 at 08:38:06AM -0800, John Ralls wrote:
>
> > On Dec 24, 2014, at 7:38 AM, David Osguthorpe
> > wrote:
> >
> > (By the way note that GnuCash is multithreaded because Gtk is
> > multi-threaded - in the initial
> > implementation attempts I had issues with python GIL crashes
Not sure if this should be under the other emails, but I'm unable to get
this to work for the last little bit, the error is similar. I've tried
to use "git clean -fdx" and then even wiped it all and started again,
but still having the same error..
-
Using built
Not sure if this should be under the other emails, but I'm unable to get
this to work for the last little bit, the error is similar. I've tried
to use "git clean -fdx" and then even wiped it all and started again,
but still having the same error..
-
Using built
> On Dec 24, 2014, at 6:12 PM, GnuCash wrote:
>
> Not sure if this should be under the other emails, but I'm unable to get
> this to work for the last little bit, the error is similar. I've tried
> to use "git clean -fdx" and then even wiped it all and started again,
> but still having the sam
14 matches
Mail list logo
