tagging xtuple for release 4.0.0Beta2

git-svn-id: http://svn.code.sf.net/p/postbooks/code/xtuple/tags/R4_0_0BETA2@13824 ea1a15ef-c238-0410-93cb-fa28e9f07733
create branch to work on numerics changes based on R4_0_0BETA2

git-svn-id: http://svn.code.sf.net/p/postbooks/code/xtuple/branches/revise_numerics_400b2@13867 ea1a15ef-c238-0410-93cb-fa28e9f07733
numerics wip - too much going on to risk losing it if my machine dies.
monetary values (money, salesp, cost, purchp) are composite types of amount & currency
while most non-monetary numerics (qty, qtyper, percent, etc) are postgresql domains.
the goals are (1) differentiate between different kinds of numeric value
to make it easier in the future to isolate behaviors specific to different kinds
of numeric (e.g. percentages are presented to the user as x * 100 but stored as x)
(2) drop the constraint of fixed numeric field widths so people who want to store
costs to 8 decimal places can do so
(3) constrain storage and handling of monetary values to well-understood rules.

re: configuration interface - precisions don't really belong in the locales so
this has been moved to a separate setup subwindow.
currently most of the ui shows monetary values as 0.00.

git-svn-id: http://svn.code.sf.net/p/postbooks/code/xtuple/branches/revise_numerics_400b2@13871 ea1a15ef-c238-0410-93cb-fa28e9f07733
add xmoney file missed in previous commit

git-svn-id: http://svn.code.sf.net/p/postbooks/code/xtuple/branches/revise_numerics_400b2@13873 ea1a15ef-c238-0410-93cb-fa28e9f07733
make g/l transactions report share metasql with display

git-svn-id: http://svn.code.sf.net/p/postbooks/code/xtuple/branches/revise_numerics_400b2@13874 ea1a15ef-c238-0410-93cb-fa28e9f07733