It's so interesting to see how much of a commodity charting/graphing has become. When we started building Deltagraph in late 1988, what we made become a kind of standard since we targeted Postscript and Illustrator output, and included almost every kind of chart we could find with ridiculous options for everything, so people used it world wide, especially if targeting print. In the mid-90's, it was sold by the publisher (we just did the dev), and it spent the next 25 years at various owners before dying during the pandemic, all still based on the original source code (C) I started. I can't imagine how bad the code looked by then...
Sure ggplot, for example, is finicky, and you need to fuss over it to get the look you are wanting, but then again, it is very flexible. Most of these solutions get frustrating as soon as you want to do, for example, spaghetti plots of within subject repeated measures using age (not time-point) of accelerated longitudinal design data, with fixed effect plots on top. e.g. this plot of mine [1]
[1] https://imgur.com/a/gw2vV7w
Obviously there is a lot of work here, but I am a bit confused. If you already have lab code in Julia, Matlab, R, Python, Excel, etc., what is the motivation to use this tool? Is this hot in a specific community?
I'm in potentially the target demographic for this. I regularly bounce between R, Python, Maxima, and occasionally MATLAB/Octave. Passing data between these is usually done using the lowest common denominator: CSV. Having four completely different interfaces to these tools is a hassle. I'm also not a big fan of Jupyter and if this feels better for me it might be a decent Jupyter replacement even without the cross-language stuff.
I suppose this is a FOSS solution for the roughly same space occupied by commercial tools like Origin, that are very popular in some scientific communities.
They can be useful if you have other tools (e.g. measurement software) that already produces the data you want, and you just want a GUI tool to create plots, and maybe do some simple things like least squares curve fitting etc.
If you already do a lot of data wrangling in something with a programming language and plotting libraries accessible from said language, like the ones you mention, yeah, this is not the tool for you.
It is! I remember using this (or SciDavis, a related project) a couple of years back in college. It was not as powerful as Origin 10 years ago, but it ran on Linux.
This is great for people who don't know nor want to learn to program.
Unfortunately the only database it supports is SQLite, I really wanted to hook this up directly to a database or REST API. Going back and forth between exporting files and importing them into LabPlot is just too much work...
It's so interesting to see how much of a commodity charting/graphing has become. When we started building Deltagraph in late 1988, what we made become a kind of standard since we targeted Postscript and Illustrator output, and included almost every kind of chart we could find with ridiculous options for everything, so people used it world wide, especially if targeting print. In the mid-90's, it was sold by the publisher (we just did the dev), and it spent the next 25 years at various owners before dying during the pandemic, all still based on the original source code (C) I started. I can't imagine how bad the code looked by then...
Sure ggplot, for example, is finicky, and you need to fuss over it to get the look you are wanting, but then again, it is very flexible. Most of these solutions get frustrating as soon as you want to do, for example, spaghetti plots of within subject repeated measures using age (not time-point) of accelerated longitudinal design data, with fixed effect plots on top. e.g. this plot of mine [1] [1] https://imgur.com/a/gw2vV7w
Obviously there is a lot of work here, but I am a bit confused. If you already have lab code in Julia, Matlab, R, Python, Excel, etc., what is the motivation to use this tool? Is this hot in a specific community?
I'm in potentially the target demographic for this. I regularly bounce between R, Python, Maxima, and occasionally MATLAB/Octave. Passing data between these is usually done using the lowest common denominator: CSV. Having four completely different interfaces to these tools is a hassle. I'm also not a big fan of Jupyter and if this feels better for me it might be a decent Jupyter replacement even without the cross-language stuff.
I suppose this is a FOSS solution for the roughly same space occupied by commercial tools like Origin, that are very popular in some scientific communities.
They can be useful if you have other tools (e.g. measurement software) that already produces the data you want, and you just want a GUI tool to create plots, and maybe do some simple things like least squares curve fitting etc.
If you already do a lot of data wrangling in something with a programming language and plotting libraries accessible from said language, like the ones you mention, yeah, this is not the tool for you.
It is! I remember using this (or SciDavis, a related project) a couple of years back in college. It was not as powerful as Origin 10 years ago, but it ran on Linux.
This is great for people who don't know nor want to learn to program.
Pretty sure this is the project github:
https://github.com/KDE/labplot
I think that's just a GitHub mirror, the actual development is happening over at the KDE GitLab
https://invent.kde.org/education/labplot
Yep, thanks. It was down when I posted that.
HN hug of death?
Unfortunately the only database it supports is SQLite, I really wanted to hook this up directly to a database or REST API. Going back and forth between exporting files and importing them into LabPlot is just too much work...
The manual says otherwise:
https://docs.labplot.org/en/import_export/import_export_sql....
https://doc.qt.io/archives/qt-5.15/sql-driver.html
Are you talking about something else?
I installed it and the only choice I got for selecting a database was SQLite
SQLite is great and there are a few 3rd party REST API solutions available. What's the problem?
Are you serious? "Why don't you copy your data into a new database just to visualize it?"
I can't tell what license is applicable.
On https://labplot.org/frequently-asked-questions/ , under "Under what license is LabPlot released?", it says this:
> LabPlot is licensed under GNU General Public License, version 2.0 or later, so to put it in a few sentences:
> You are free to use LabPlot, for any purpose
> You are free to distribute LabPlot
> You can study how LabPlot works and change it
> You can distribute changed versions of LabPlot
> In the last case you have the obligation to also publish the changed source code as GPL.