MitkChartWidget was developed to display charts in MITK.
It's not suitable to have two widgets doing the same in MITK. Insert deprecation macro in QmitkPlotWidget and lead to QmitkChartWidget
Description
Event Timeline
Having no possibilities for error bars / variance indicator / or what so ever (T23384) is a real show stopper for getting everything using MITKChart. I know several (reasonable) requests for plotting some kind of range/error in line plots (see e.g. CEST, Perfusion, ...).
I think on mid term we have find a solution, either getting it run with C3 or skipping C3 (or even D3) and use some thing else (e.g. plotly.js; see https://blog.sicara.com/compare-best-javascript-chart-libraries-2017-89fbe8cb112d).
@kleina we could do an analysis if skipping C3js is an option (plotly.js seems to have everything we need).
We just took a look at plotly.js. In contrast to C3, it supports error-bars and is still under development (see guithub stats).
To use plotly.js with MITK chart we think, that no fundamental changes on C++ side are necessary. Just the JS stuff needs to be rewritten.
Easy example:
<p> Here's a simple Plotly plot - <a href="http://bit.ly/1Or9igj">plotly.js documentation</a> </p> <head> <!-- Plotly.js --> <script src="https://cdn.plot.ly/plotly-latest.min.js"></script> </head> <!-- Plots go in blank <div> elements. You can size them in the plot layout, or give the div a size as shown here. --> <div id="tester" style="width:600px;height:250px;"></div>
TESTER = document.getElementById('tester'); Plotly.plot( TESTER, [{ x: [1, 2, 3, 4, 5], y: [1, 2, 4, 8, 16], type:'bar', error_y: { type: 'data', array: [1, 1, 1, 1, 5], visible: true }, }], { margin: { t: 0 } } ); /* Current Plotly.js version */ console.log( Plotly.BUILD );
Thanks. So It would be greate to make a test ballon task for another CD to switch from D3 to plotly.js? Wouldn't it?
@hentsch / @kislinsk : Shouldn't we already set QmitkPlotDialog/QmitkPlotWidget/QtHistogram to deprecated then. To give us sooner then later the posibilite to realy remove the code from the codebase. If I see it correctly, that would also gives us the possibility to reomive Qwt as a third party package from MITK. What do you think?
This would be favorable. However, if we deprecate the QmitkPlotDialog/QmitkPlotWidget/QtHistogram classes, this leads to warnings (and errors because of warnings-as-errors).
@kislinsk do you see a possibility?
Hi there! 🙂
This task was auto-closed according to our Task Lifecycle Management.
Please follow this link for more information and don't forget that you are encouraged to reasonable re-open tasks to revive them. 🚑
Best wishes,
The MITK devs