On Sept 27, 17:19:42 EDT 2026, John Ralls wrote:
That’s too general a question so here’s too general an answer:
If you’re contemplating a large or complex change, sketch out your design
here for discussion before you begin coding. With only a couple of
5.x releases left anything that isn’t trivial or a bug fix should be
based on the future branch for GnuCash 6.0.
3. See https:/wiki.gnucash.org/wiki/CodingStandard <https://
wiki.gnucash.org/wiki/CodingStandard> for style rules and design
suggestions, particularly about migrating C to C++.
If you’re thinking of changes to F::Q you need to discuss them with Bruce
Schuck.
Kalpesh,
Before you start, remember I'm a big fan of the KISS principle and also
backwards compatibility. Unless there's a *VERY* good reason, changes to
GnuCash should not force an upgrade to F::Q. Maybe more importantly,
changes to F::Q should not force a user to upgrade to newer version of
GNC. Example would be GNC users perhaps on Ubuntu 20.04, or 22.04 and
are using whatever version of GNC is in the normal repositories. I think
for 22.04, it is a 4.x release. These users may not be ready for an OS
update, and do not want to use a flatpak or compile GNC themselves.
Some time ago, Vincent L was working on changes that would eliminate
requiring the F::Q methods to be hard-coded in GNC. Great idea, but I
believe implementing his changes in F::Q and GNC would have required
users to update both simultaneously. He abandoned his effort when I was
being stubborn about backwards compatibility.
F::Q is a simple API. Give it a source method and a list of symbols, and
it returns JSON with the latest/current price for those symbols.
Bruce S
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel