Re: queries on mysql
Op 24-11-10 20:28, Derek Atkins schreef: Fred, Fred Verschueren writes: Frank et al, I'm coming from MS Money and use gnucash now for a month and I'm happy but I want to totally reorganise my data which I transferred from Money. To avoid I need to do this by hand I want to write a program/script (preferable in python). Are you trying to reorganize the account structure or change how transactions got placed into accounts? It might make sense, considering it's only been a month, to start over, re-import your old data and this time organize it more appropriately. I have an assets:bankaccount:bank with payments for electricity, telecom, gas, aso to expense:XX. I want electricity to go to expense:electricity, telecom to expense:telecom, gas to expense:gas, aso This are monthly payments for more than 10 years. So, a way to automate this would be very welcome. Fred. I had a look at the documentation on the API but this was not clear to me. Can I get some hint / examples how to start with this? Does a python wrapper for gnucash exists? In 2.3.x, yes. I do not believe there is a python wrapper in 2.2.x Thanks in advance. Fred -derek Op 23-11-10 03:25, Frank H. Ellenberger schreef: Fred, Am Montag, 22. November 2010 um 19:15:47 schrieb Fred Verschueren: : 3. You mention an alternative by writing a (python) program using the API. Where can I find documentation on this API? If you do not have the sources on your machine, where you could run make doc, you can use http://svn.gnucash.org/docs/HEAD/ @Derek, they show Rev, 2.3.0. Are they not built every night? Frank ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Documentation in pdf format
I've experimented a little with the pdf image size issue and I've found a solution. Fop is printing-oriented so it doesn't consider the image size but the pixel-per-inch (ppi) attribute. So if the image has a ppi of 72 (as normally is when saving an image file) and a width of 510pixel it will be printed with a width of 510/72*2,5=17,7cm. At this point I figured out a simple way to convert all the images ppi in a run with Imagemagik:. From the figures folder issue the following two commands: ls *.png > list for i in `cat list`; do convert -units PixelsPerInch -density 130 "$i" "$i"; done The best would be to have the ppi changed or (checked) automatically when "make pdf" is issued (I don't know how to do this). If the check is on user-side there will be the need of a new dependency (imagemagick) so I think it would be better to have a check upstream. So we need only to choose in what dimension print images in PDF and set a ppi to all figures. NOTE: the ppi attribute is not influent on image size but only in it's printed size (on paper) and not in video. So changing this attribute is like not changing it at all if you display the Manual on your monitor. Il 24/11/2010 15:18, Geert Janssens ha scritto: On Wednesday 24 November 2010, Cristian Marchi wrote: I tested it right now and works well; the result is very good! I see problems with images (some are overscaled) and with some help tables where the last column is probably too large and is drawn in a new page. Regards Cristian Thinking some more on the image sizes. It looks as if the resolution stored in the images has something to do with this. The images that get oversized were saved in 72dpi, images that look good had higher resolutions. For example, the image basic_AccountsSampleQIF.png in "Putting it all together" in concepts guide chapter 2 is 72dpi and gets overscaled. On the other hand image basic_EmptyAccounts.png in the same section has 126dpi and looks much better in pdf. If we want to have nice looking pdfs, we will have to be careful how we save our images. Note that docbook also allows to define multiple imageobjects inside one mediaobject. This could help us in some cases to provide different resolution images for html and pdf. Geert . ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: queries on mysql
Fred-- I don't know how you have your accounting set up in Money. When I used Quicken, though, I had categories for Electricity, Gas, and Telecom, and these imported into Gnucash as separate accounts. Perhaps you could rearrange your accounts in Money to use categories (or whatever they are in Money), using a find and replace, export to QIF, and then import the QIF into Gnucash. David --- On Thu, 11/25/10, Fred Verschueren wrote: > From: Fred Verschueren > Subject: Re: queries on mysql > To: "Derek Atkins" > Cc: gnucash-devel@gnucash.org > Date: Thursday, November 25, 2010, 1:20 AM > > I have an assets:bankaccount:bank with payments for > electricity, > telecom, gas, aso to expense:XX. > I want electricity to go to expense:electricity, telecom to > > expense:telecom, gas to expense:gas, aso > This are monthly payments for more than 10 years. > So, a way to automate this would be very welcome. > > Fred. > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: postgres database lock cancelling on closing gnucash
On Nov 24, 2010, at 11:21 AM, Johann Wöckinger wrote: > Hello, > > since Version 2.3.16RC1, I notice the following message popup on starting > gnucash: > > GnuCash could not get exclusive write permission to postgres://. > > with some explaination for reasons for that. > > It seems, that gnucash does not delete the lock entry in the database (table: > gnclock) when closing the application (I found the lock entry still in the > database table after closing gnucash), so it comes up with this warning on > startup, which can be overridden on selecting "open" - but its somewhat > annoying. > > This behaviour was not observed in former releases of the 2.3.x series. > > Would be nice to have the former behavior. Have you seen this with 2.3.17? It sounds like a duplicate of https://bugzilla.gnome.org/show_bug.cgi?id=634392, which was fixed for 2.3.17. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: postgres database lock cancelling on closing gnucash
On Nov 25, 2010, at 1:44 PM, Johann Wöckinger wrote: > Yes, it's also in 2.3.17. > > Am 2010-11-25 21:28, schrieb John Ralls: >> On Nov 24, 2010, at 11:21 AM, Johann Wöckinger wrote: >> >> >>> Hello, >>> >>> since Version 2.3.16RC1, I notice the following message popup on starting >>> gnucash: >>> >>> GnuCash could not get exclusive write permission to postgres://. >>> >>> with some explaination for reasons for that. >>> >>> It seems, that gnucash does not delete the lock entry in the database >>> (table: gnclock) when closing the application (I found the lock entry still >>> in the database table after closing gnucash), so it comes up with this >>> warning on startup, which can be overridden on selecting "open" - but its >>> somewhat annoying. >>> >>> This behaviour was not observed in former releases of the 2.3.x series. >>> >>> Would be nice to have the former behavior. >>> >> Have you seen this with 2.3.17? It sounds like a duplicate of >> https://bugzilla.gnome.org/show_bug.cgi?id=634392, which was fixed for >> 2.3.17. Well, that's annoying, because I don't see the problem on my development system. Are you connecting to a local (on the same machine) or network psql server? On what OS are you running Gnucash? If you're connecting to psql on a different machine, what OS is it running? What version of psql? Please start gnucash and find its PID and the hostname of the machine running Gnucash. Then quit Gnucash and, from psql, do "select * from gnclock". Are the hostnames and PIDs the same? At the end of gnucash.trace is there a warning about not finding the lock? Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
