Thanks for the encouraging words, Scott.

I'll take a stab at it when I find the time, continuing the discussion on GitHub when I'm there.

Benjamin


On 3/12/26 8:02 PM, Scott wrote:
@Benjamin -- Fava has been a great tool for me, and I appreciate the idea of wanting to make a contribution that is useful beyond your personal case.  In my mind, fava-dashboards has been a huge asset and really opened up the possibilities of what I can easily be do with fava.  I think in that spirit, the idea of generalizing and exposing fava's account view is possibly a very valuable contribution, and one I have been thinking about as well.  Specifically, I think there is a gap in that (1) fava only exposes account views based on the account tree and only exposes a few customized reports; and (2) fava-dashboards is very useful for integrating graphing and BQL; but there seems to be a gap in that the account views and reports that are native to fava aren't easily created (AFIK) through BQL queries.  I think exposing the elements of fava account/report pages so they can be easily modified ala fava-dashboards would be great

-Scott

On Thursday, March 12, 2026 at 5:34:08 AM UTC-7 Benjamin Debeerst wrote:

    Hi all,

    Chary, thank you for the suggestion, the screenshots from your
    Notebook
    look interesting indeed and I'd be curious for a share of that as
    well.
    TIL about Marimo as well.

    In my case, my partner is also looking at the reports, so having
    them on
    the Fava instance running in our home network and which is being used
    already would be preferable over installing/running/switching to yet
    another, separate tool. The upside of remaining in Fava is also
    that one
    can deep link and investigate: "Wait, why did groceries shopping
    go up
    so much last month?" --> Click through to the journal --> "ah sure, I
    made that massive purchase for the party" --> "let me add a note
    to the
    journal about that".

    Finally though, trying to bring the thread a bit back to it's
    original
    topic: While it is certainly more technically involved to hack on the
    Fava source code to produce reports adapted to my personal needs,
    I was
    hoping to contribute back and make the improvement accessible to a
    wider
    group, also the less technically savvy. Sure I can hack and do
    whatever
    I want for me personally and maintain/run a fork. But the intent
    of my
    post here on the list was to be able to make something that has a
    perspective of being merged into mainline beancount/fava. Curious to
    hear your thoughts about that.

    Best regards,
    Benjamin

--
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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/beancount/8552d9ca-3f0e-4419-8342-66c84b5447f8n%40googlegroups.com <https://groups.google.com/d/msgid/beancount/8552d9ca-3f0e-4419-8342-66c84b5447f8n%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/beancount/4fe6ead6-cc7f-4ac3-8122-75ff2971ee63%40posteo.de.

Reply via email to