--------------4F07D9624B15D68574AF862D
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Robert Graham Merkel wrote:
> Richard -Gilligan- Uschold writes:
> >
> >
> > This submission is an update to the "Tax" report. It includes new
> > reports: "Export .TXF", which exports a file that can be read by tax
> > programs such as TaxCut and TurboTax, and "Hierarchical", which gives a
> > hierarchical total of selected accounts down to 15 sub account levels.
> > (I just through this in as it changed only a few dozen lines)
> >
> > This patch is against v1.4.8, as it is unclear when a stable version of
> > latest will be available.
> >
> > I have two options for the patch against the latest:
> >
> > 1. Make a few minor changes and submit in a few days.
> >
> > 2. More fully integrate the tax fields in the account structure, which
> > would take longer. (currently, the tax fields are stored in the notes
> > field, which works, but is not ideal)
> >
> > I would prefer choice 2, but I'll do 1, if you prefer, it's no big deal.
>
> 2 is definitely the way to go. Have a look at the new capabilities of
> the engine and see if you can figure how how best to implement the tax
> report. However, it may well require adding things in the UI.
Great. Ya, the "Edit Account" dialog should change, and the "Txf Export Init"
page in the report "Parameters" dialog should probably be somewhere else,
probably under the "Settings" menu?
> Be aware that in the not-too-distant future, the Query API will be
> fully wrapped, and we'd like the reports to use that to find the
> information they need.
I've read a bit about this on this list, but, I'm not sure how this affects
me. I'm currently using a dozen or so of the calls documented in
"/usr/share/gnucash/doc/gnc.html", such as "gnc:account-get-xx",
"gnc:get-current-accounts", "gnc:group-get-xx", "gnc:split-get-xx",
"gnc:transaction-get-xx". Are these going to be depreciated?
> Finally, there was some discussion about handling transaction taxes on
> -devel. I think it's mostly orthogonal to your tax report, but you
> might just want to check it out and see what you think.
I saw this, but it didn't seem relevant to what I'm doing.
> ------------------------------------------------------------
> Robert Merkel rgmerk@mira.net
>
> "We are excited and optimistic about its usage going
> forward and, yes, we can teach penguins the military
> close-order drill", Mark Norton, US Department of Defense.
> ------------------------------------------------------------
--
Gilligan | __o .oooO
/| _ \<,_ ( )
/p|\ (_)/ (_) \ ( Oooo.
/ | \ ------------ \_) ( )
======== ) /
======== gilligan@mpinet.net (_/
~~~~~~~~~~~~~~~~ uschold@cs.ucf.edu
--------------4F07D9624B15D68574AF862D
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
Robert Graham Merkel wrote:
Richard -Gilligan- Uschold writes:
>
>
> This submission is an update to the "Tax" report. It
includes new
> reports: "Export .TXF", which exports a file that can be read
by tax
> programs such as TaxCut and TurboTax, and "Hierarchical", which
gives a
> hierarchical total of selected accounts down to 15 sub account
levels.
> (I just through this in as it changed only a few dozen lines)
>
> This patch is against v1.4.8, as it is unclear when a stable
version of
> latest will be available.
>
> I have two options for the patch against the latest:
>
> 1. Make a few minor changes and submit in a few days.
>
> 2. More fully integrate the tax fields in the account structure,
which
> would take longer. (currently, the tax fields are stored in
the notes
> field, which works, but is not ideal)
>
> I would prefer choice 2, but I'll do 1, if you prefer, it's
no big deal.
2 is definitely the way to go. Have a look at the new capabilities
of
the engine and see if you can figure how how best to implement the
tax
report. However, it may well require adding things in the UI.
Great. Ya, the "Edit Account" dialog should change, and the "Txf
Export Init" page in the report "Parameters" dialog should probably be
somewhere else, probably under the "Settings" menu?
Be aware that in the not-too-distant future, the
Query API will be
fully wrapped, and we'd like the reports to use that to find the
information they need.
I've read a bit about this on this list, but, I'm not sure how this affects
me. I'm currently using a dozen or so of the calls documented in
"/usr/share/gnucash/doc/gnc.html", such as "gnc:account-get-xx", "gnc:get-current-accounts",
"gnc:group-get-xx", "gnc:split-get-xx", "gnc:transaction-get-xx".
Are these going to be depreciated?
Finally, there was some discussion about handling
transaction taxes on
-devel. I think it's mostly orthogonal to your tax report, but
you
might just want to check it out and see what you think.
I saw this, but it didn't seem relevant to what I'm doing.
------------------------------------------------------------
Robert Merkel
rgmerk@mira.net
"We are excited and optimistic about its usage going
forward and, yes, we can teach penguins the military
close-order drill", Mark Norton, US Department of Defense.
------------------------------------------------------------
--
Gilligan | __o .oooO
/| _ \<,_ ( )
/p|\ (_)/ (_) \ ( Oooo.
/ | \ ------------ \_) ( )
======== ) /
======== gilligan@mpinet.net (_/
~~~~~~~~~~~~~~~~ uschold@cs.ucf.edu