https://bugs.kde.org/show_bug.cgi?id=515589
--- Comment #3 from Ralf Habacker <[email protected]> --- (In reply to Mark Neugebauer from comment #2) > +1 > > Only drawback I can come up with is that this would exclude Windows users, > correct? That depends on where you get the binaries from. The binaries you can get from https://kmymoney.org/snapshots.php include DBus support and qdbus. > And probably those features would be a little harder to discover See this example how it would work: $ kmymoney -n $ qdbus $(qdbus | grep kmymoney) /KMymoney open file:///tmp/input.xml $ qdbus $(qdbus | grep kmymoney) /KMymoney saveAs file:///tmp/output.xml $ qdbus $(qdbus | grep kmymoney) /KMymoney saveAs sql://user@localhost/tmp/output.sqlite?driver=QSQLCIPHER > than just some command line parameters (at least from my personal level of > expertise). The D-Bus interface is already in place and has been tested, but I don't know if the other approach is as straightforward. > I would be perfectly happy with this solution. At this point, I would like to mention a utility program that is currently available with kmymoney installations. It is used to export reports in csv, xml, and html format. If you do not need the entire database, but rather the required data in report form, this could be an alternative. LANG=C ../kmymoney-master-build/bin/kmmreport-export --help Usage: ../kmymoney-master-build/bin/kmmreport-export [options] url Export KMyMoney reports Options: -h, --help Displays help on commandline options. --help-all Displays help including Qt specific options. -v, --version Displays version information. --csv Export in csv format (default) --html Export in HTML format --xml Export in xml format --reference Create reference file from output --infotable Use info table for exporting --pivottable Use pivot table for exporting --querytable Use query table for exporting (default) --list List all custom reports --output <output> Filename for generated output --report <report> Process a specific report Arguments: url file to open -- You are receiving this mail because: You are the assignee for the bug.
