Re^2: (OT) Perl Open Source accounting packages?

[tphyahoo]

Rir, this sounds very interesting. I have been done some research looking for open source accounting packages that could be adopted to the wild ideas described in ledgerism, or in various utopian community currency and bartering schemes, such as my scrawled-on-a-napkin idea nbarter. The idea I am most interested in is a scheme called community wizard that would empower groups of people to better understand the flow of money in their neighborhoods.

Total vaporware as of now.

But I wanted to see what already existed in open source that could be scavenged, to implement this. The first thing that would be needed is a multi user general ledger with a web interface.

For candidates I wound up with just sql-ledger, which is unfortunately is not the most robust code, and Compiere, which runs on java and requires oracle.

Neither of these sounded real appealing. I did like the rich/reach (windows widget/web) idea of Compiere, but it runs reeeal slow and has too much overhead to factor just the general ledger stuff out of it. (Even if I knew java, which I don't.)

Martin Bramwell is putting together an open source package he calls CACH (Community Automated Clearing House), which I am also very interested in. He said he was aiming to release in March, but unfortunately until then there's no public information about it online.

I don't know if your work would be helpful in this regard, but I would be interested in learning more about what you are doing, and maybe beta testing it if you need anyone.

[rir]

Thanks for your interest. Life changes have pulled me away from my accounting system work. I am just getting back into it and am grappling with the user interface.

That interface is to be in Tk, but I am trying to keep a separation of concerns.

The working name is Rbks. It is a fairly simple and flexible double entry bookkeeping system. As it stands now I have the General Journal backend code fairly squared away. Which is to say a Gj_entry posts itself correctly.

Ledger and journal reports don't concern me much. These seem to be straight forward SQL reports. I haven't found any strong justification to have reporting be part of the objects. I am open to argument and think the design is flexible enough to add this.

I have looked at the ledgerism reference. For practical purposes I have a distrust of such all encompassing models. The other links you give don't work for me.

I am researching scaffold code for basic database Find/Prev/Next/Add/Update/Delete interface screens. If I don't find anything soon I'll be posting a long SOPW.

I'd rather have an interface before releasing code, but I am willing to share the overview info. Be well,
rir