[Openledger-developer] Impl. of "general ledger transaction"
Brought to you by:
klavs
From: Klavs K. <kl...@vs...> - 2005-03-02 18:16:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, I'm looking at SL code -and I think I'll build the API "transaction" function from SL/GL.pm transaction function - and replace the $form element with a transaction object. Unfortunately there's absolutely NO comments in the code (great ;) so there's a lot of things it does - that I'm not certain off (digging through the $form element will probably help there). One of you talked about having recorded which SQL queries were done for the different actions - I could use a list of SQL queries it runs, when posting a new general ledger transaction - to doublecheck. I'd be happy to hear if any of you have any design ideas? or if you just like my idea :) Also - if we could identify some tasks that we each would like to work on (usually because we need to use them ourselves) - that way we can create a list of tasks, and who they are assigned to? - -- Regards, Klavs Klavsen, GSEC - kl...@vs... - http://www.vsen.dk PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62 "Those who do not understand Unix are condemned to reinvent it, poorly." ~ --Henry Spencer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCJgMLPToLeX4GPGIRAt8aAJ4plm1jepE7/Ej2zePb6+ZisikU5gCfeOo6 ZkuoXNhX2d5VLAwX5bOFa0I= =DTaZ -----END PGP SIGNATURE----- |