This would also probably eliminate the need to place restrictions on object/column names. Wherever possible, consistency should be checked at compile-time. Revise some internal APIs that use undocumented protocols for the strings that get passed around.
Add generic plug-in support, support for implementing extensions in Python, a full-featured multi-level undo/redo framework (-> visitor pattern).
Unify naming of some methods and variables with class names. For example, ideally it should be possible to implement new plot or marker types without modifying existing classes (think of plug-ins here). Make QtiPlot easier to extend and maintain by modularizing it. Qt, Qwt (5.0.0), QwtPlot3D, GSL, muParser, zlib (1.2.3), and liborigin. All suggestions and contributions are most welcome! If you want to contribute code, please read the notes on coding style first. QtiPlot is still far from this goal, but there's a "wish to" list we are constantly working on. The purpose of this project is to develop a free (open source), platform independent alternative to Origin. For Windows systems there is a well known and widely used software called Origin, which is not free, of course. Scientists often need to use data analysis and plotting software. \ mainpage QtiPlot - Data analysis and scientific plotting - API documentation
0 kommentar(er)
