CSPro Open Source roadmap and minimal Developer Guidelines
Posted: May 21st, 2025, 11:57 pm
Dear CSPro Developer Team,
I will not posting feature request anymore, but what I would like to work on in the future.
Unfortunately, the last time I coded C/C++ was in 2002 and it was for an university programming course project. It was a tic tac toe with GUI using Borland compiler.., This should be different if CSPro was open source 20 years ago. I discovered it in 2004 and learned it 100% by myself until 2011 when I discovered that the CSPro Developer Team can help.
Now, what I need is some kind of How to? because I started to think in object programming only in 2024... and trying to come back to C/C++ only this year...
In the next few years, as contributions, I would like to work on:
I will not posting feature request anymore, but what I would like to work on in the future.
Unfortunately, the last time I coded C/C++ was in 2002 and it was for an university programming course project. It was a tic tac toe with GUI using Borland compiler.., This should be different if CSPro was open source 20 years ago. I discovered it in 2004 and learned it 100% by myself until 2011 when I discovered that the CSPro Developer Team can help.
Now, what I need is some kind of How to? because I started to think in object programming only in 2024... and trying to come back to C/C++ only this year...
In the next few years, as contributions, I would like to work on:
- a) Using Leaflet also for Android mapping engine. Thanks to Leaflet 2.0 release as modern ESM and the CSPro 8.1 support of ES module. This will facilitate me a lot. I already started something here a few years ago: https://github.com/gregvolny/CSPro-Demos/issues/1
- b) Allow CSPro to support multiple levels (more than three) for any dictionary (main or external). And give a way to CSPro applications developers to define data flow between levels. https://github.com/csprousers/cspro/issues/2
- c) Allow CSPro to tabulate data stored in list, hashmap and array. I always use SQL and SPSS to tabulate data in my life until I discovered CSPro data tabulation last year... As I mentioned to Savy a few years ago, the first component of CSPro that should be wrapped as ES module using WASM is the tabulation feature. It is because I think it can be simpler than R tabulation, but only if CSPro can tabulate data stored in list/hashmap/array objects. https://github.com/csprousers/cspro/issues/4
- d) A very long ago request: Allow any user defined functions (CSPro logic or JS) to support dictionary symbol that are unknow until the runtime :https://github.com/csprousers/cspro/issues/3;
- e) Give users a way to choose between having a string/longtext parsed relational database (as is it now: viewtopic.php?p=18147) and the same data structure we have in the CSDB/E https://github.com/csprousers/csweb/issues/1.