I’m curently using Coda, but I’m testing Fibery right now after following it for a long time.
The question of the moment is: why different sets of functions between calculations and formulas? What is the rationality behind that choice?
I understand the need for a complete set of functions in the report context (calculations), but why are they not also present in the database context (formulas)?
Hi, this is historical. Reports are based on a separate product with own calculations, so when we integrated it into Fibery we kept them as is. It is for sure not good, but at least you have some reasoning why it happened
Ok, it make sense. Not in a logical way but related to the dev history of the product. Thanks for the honesty and the quick reply, that’s part of what attracted me to Fibery .
And your explanation makes me wonder if that calculation part of Fibery with its functions and UI (list of functions on the left, the small editor with line wrap and indentation) could be applied one day to the formulas part of Fibery?