On Tue, 8 Jan 2019 16:18:46 +0100 Markus Elfring <Markus.Elfring@web.de> wrote:
It's a special purpose humidity logger.
Have you got any influence on the data format for specific fields by this software?
No
I'm not considering development, I'm trying to use already developed systems.
You are also in the process of selecting appropriate tools for some tasks.
I wish you'd leave more context when replying. I hate having to refer back to other messages. For that matter, I'm not clear what the point of this discussion is. Are you trying to help me, or am I trying to help you?
Those systems should have considered efficient performance for sure,
This aspect was checked to some degree.
but it seems that LO didn't bother.
I imagine that there are also special software design constraints involved.
A program like “LibreOffice Calc” can mostly be used as a convenient graphical user interface including the presentation of charts. These diagrams need to transform the provided input data into structures for more efficient processing. Would you like to change any software limitations in this area?
I don't think it does provide a convenient interface for charting, especially apparently for time-series, but also in terms of abilities to change the view: expand time, simplify the display etc.
The data size growth will trigger to reconsider analysis approaches, won't it?
I don't know what you mean. LO is very slow, so LO should consider improving its performance, IMHO.
I guess that we observe scalability difficulties.
I know of other software that is faster,
Such a fact is also good to know, isn't it?
Will any other chart modules become quicker, too?
I have no idea.
so I may be forced to build an interface and use that instead.
Do you interpret this as another interesting challenge?
I hope it will be interesting, but it's a nuisance rather than a challenge. I have other things I'd rather do than build a bit of special software interface glue.
I don't think so, I just want to be able to temprarily hide some of the lines representing individual data sets.
Would you like to explain corresponding constraints?
Again, I don't understand what you mean.
How do you think about to clarify the challenges around the mentioned data selections a bit more?
I don't see any challenges. In emoncms, for example, I just click on the legend for a line, to temporarily remove that line from the display. Another click restores it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org