> > It would also be good if this could be built in modular fashion so we can > use it as a library for beancount scripting, a cli and as a fava plugin > (should fava-investor be beancount-investor, with a fava plugin?) >
I very much agree with the philosophy of library/cli/fava. That's exactly how I designed my tax loss harvestor <https://github.com/redstreet/fava_tax_loss_harvester> (there's libtlh.py, tlh.py, and the fava extension). That is the ideal design for fava-investor too, IMHO. However, I find that for investing reports and tools, interactivity and visualization are key. This is the reason I'd like to build this primarily as a fava extension, and have the focus and main efforts be on fava. Ideally, this could even become a standard part of fava. Hence the naming. (I considered naming it beancount_fava_investor to tip my hat to beancount for being what makes this work, but that is too long and confusing). On Sunday, March 22, 2020 at 9:50:41 PM UTC-7, Dave The Happy Singer wrote: > > I've added some comments here: > https://github.com/beancount/fava/issues/1082#issuecomment-602310904 > > Let us know if you want to continue the conversation here, on fava or on > fava-investor! > > Dave > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/c37936c4-092f-403f-a2e0-cc6a40b737b2%40googlegroups.com.
