https://bugs.documentfoundation.org/show_bug.cgi?id=70399
Wolfgang Jäger <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Wolfgang Jäger <[email protected]> --- (In reply to Todor Balabanov from comment #2) > Are there any performance measurements about NLPSolver efficiency? > > I am not sure that rewriting from Java to C++ will provide dramatically > speed-up. The issue isn't only/mainly concerning efficiency. There is tdf#38948 e.g open since 2011, and requests to get a way to save solver settings to documnents are posted once in a while in an ask/discourse question. See https://ask.libreoffice.org/t/is-there-any-way-to-save-a-solver-model-in-calc-again/77249/8 . I don't remember one of those posts complaining about lack of efficiency. It's about the workflow. It seems the NLP solvers are insufficiently embedded via the current API: set-/get methods for stuctured(object properties don't exist, and the PropertyBag service also doesn't work properly. I would assume this is in consequence of a broken bridge to the implementation in java. If the mentioned problems were fixed, any interested user could easily(?) write a workaround in Basig e.g. -- You are receiving this mail because: You are the assignee for the bug.
