Re: Lot transfers
Dear Peter, I think the fact that there was no reply concerning your ideas and technical details means there currently isn't any interested developer available for working in this field. Given the nature of this volunteer project, unfortunately this means there is only very little chance for you to get this implemented in the near future. Occasionally, there are developers around who are available for paid work on features they don't need personally, but this would involve significantly higher rates that what you mentioned, so it probably won't help you here either. But in general development happens here only if there is at least one developer with a personal interest in the actual feature, which unfortunately doesn't seem to be the case here. Sorry for this not-so-encouraging reply from me. Best Regards, Christian Am Donnerstag, 21. Februar 2013, 23:21:08 schrieb Peter Dey: Just thought I'd followup on this -- I didn't receive any replies. Any idea about the technical complexity involved in implementing this functionality/modification? Thanks, Peter On Wed, Jan 23, 2013 at 10:52:03PM +1100, Peter Dey wrote: Hi all, I've got a bit over AU$100 credit leftover at a freelance developer site called freelancer.com. I'd like to create a project on the site to fund the implementation of the lot transfer functionality described here: http://wiki.gnucash.org/wiki/Concept_of_Lots Since I know very little about GnuCash's internal architecture, I was hoping someone here would be willing to help me write the specification to ensure it's done in a way suitable to be merged into the mainline, for everyone to benefit from it. As far as I can tell, it would involve: 1. Addition of a checkbox to the New/Edit account screens to mark an account as a lot account 2. A hook somewhere auto-create a new lot when there's a new entry. Code could probably be borrowed from the scrubber? 3. (personal preference, not on the wiki) add a column to lot accounts to show the lot title against every split 4. Assume LIFO like the scrubber does -- add a hook to auto-assign (and close) lots on outgoing transactions. Again,. probably could be borrowed from the lot scrubber. 5. The most complicated: alter the data structure to remove the tie between lots and accounts (i.e., guid only). This will probably need changes in other places that make an assumption or have a dependency that lot guids lie in a single account. I can only think of the lot scrubber at the moment? 6. Assuming it would go into a future release of GnuCash, presumably some logic to upgrade the data file/database schema Any and all help appreciated... Cheers, Peter ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Lot transfers
On Sat, Feb 23, 2013 at 04:46:24PM +0100, Christian Stimming wrote: But in general development happens here only if there is at least one developer with a personal interest in the actual feature, which unfortunately doesn't seem to be the case here. Sorry for this not-so-encouraging reply from me. Thanks for the reply, Christian. I kind of expected this would be the case anyway, but figured it was worth a try! Cheers, Peter ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Lot transfers
Just thought I'd followup on this -- I didn't receive any replies. Any idea about the technical complexity involved in implementing this functionality/modification? Thanks, Peter On Wed, Jan 23, 2013 at 10:52:03PM +1100, Peter Dey wrote: Hi all, I've got a bit over AU$100 credit leftover at a freelance developer site called freelancer.com. I'd like to create a project on the site to fund the implementation of the lot transfer functionality described here: http://wiki.gnucash.org/wiki/Concept_of_Lots Since I know very little about GnuCash's internal architecture, I was hoping someone here would be willing to help me write the specification to ensure it's done in a way suitable to be merged into the mainline, for everyone to benefit from it. As far as I can tell, it would involve: 1. Addition of a checkbox to the New/Edit account screens to mark an account as a lot account 2. A hook somewhere auto-create a new lot when there's a new entry. Code could probably be borrowed from the scrubber? 3. (personal preference, not on the wiki) add a column to lot accounts to show the lot title against every split 4. Assume LIFO like the scrubber does -- add a hook to auto-assign (and close) lots on outgoing transactions. Again,. probably could be borrowed from the lot scrubber. 5. The most complicated: alter the data structure to remove the tie between lots and accounts (i.e., guid only). This will probably need changes in other places that make an assumption or have a dependency that lot guids lie in a single account. I can only think of the lot scrubber at the moment? 6. Assuming it would go into a future release of GnuCash, presumably some logic to upgrade the data file/database schema Any and all help appreciated... Cheers, Peter ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Lot transfers
IRS allows FIFO, LIFO, etc you get to select once On Thu, Feb 21, 2013 at 4:21 AM, Peter Dey gnuc...@realmtech.net wrote: Just thought I'd followup on this -- I didn't receive any replies. Any idea about the technical complexity involved in implementing this functionality/modification? Thanks, Peter On Wed, Jan 23, 2013 at 10:52:03PM +1100, Peter Dey wrote: Hi all, I've got a bit over AU$100 credit leftover at a freelance developer site called freelancer.com. I'd like to create a project on the site to fund the implementation of the lot transfer functionality described here: http://wiki.gnucash.org/wiki/Concept_of_Lots Since I know very little about GnuCash's internal architecture, I was hoping someone here would be willing to help me write the specification to ensure it's done in a way suitable to be merged into the mainline, for everyone to benefit from it. As far as I can tell, it would involve: 1. Addition of a checkbox to the New/Edit account screens to mark an account as a lot account 2. A hook somewhere auto-create a new lot when there's a new entry. Code could probably be borrowed from the scrubber? 3. (personal preference, not on the wiki) add a column to lot accounts to show the lot title against every split 4. Assume LIFO like the scrubber does -- add a hook to auto-assign (and close) lots on outgoing transactions. Again,. probably could be borrowed from the lot scrubber. 5. The most complicated: alter the data structure to remove the tie between lots and accounts (i.e., guid only). This will probably need changes in other places that make an assumption or have a dependency that lot guids lie in a single account. I can only think of the lot scrubber at the moment? 6. Assuming it would go into a future release of GnuCash, presumably some logic to upgrade the data file/database schema Any and all help appreciated... Cheers, Peter ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Lot transfers
Hi all, I've got a bit over AU$100 credit leftover at a freelance developer site called freelancer.com. I'd like to create a project on the site to fund the implementation of the lot transfer functionality described here: http://wiki.gnucash.org/wiki/Concept_of_Lots Since I know very little about GnuCash's internal architecture, I was hoping someone here would be willing to help me write the specification to ensure it's done in a way suitable to be merged into the mainline, for everyone to benefit from it. As far as I can tell, it would involve: 1. Addition of a checkbox to the New/Edit account screens to mark an account as a lot account 2. A hook somewhere auto-create a new lot when there's a new entry. Code could probably be borrowed from the scrubber? 3. (personal preference, not on the wiki) add a column to lot accounts to show the lot title against every split 4. Assume LIFO like the scrubber does -- add a hook to auto-assign (and close) lots on outgoing transactions. Again,. probably could be borrowed from the lot scrubber. 5. The most complicated: alter the data structure to remove the tie between lots and accounts (i.e., guid only). This will probably need changes in other places that make an assumption or have a dependency that lot guids lie in a single account. I can only think of the lot scrubber at the moment? 6. Assuming it would go into a future release of GnuCash, presumably some logic to upgrade the data file/database schema Any and all help appreciated... Cheers, Peter ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
