Page 1 of 1

CSPro Open Source roadmap and minimal Developer Guidelines

Posted: May 21st, 2025, 11:57 pm
by htuser
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:
  • 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
Hope to receive some guidelines and ideas on How to? , from the CSPro Developer Team!

Re: CSPro Open Source roadmap and minimal Developer Guidelines

Posted: May 23rd, 2025, 1:22 pm
by Gregory Martin
I saw all of the issues that you logged on GitHub the other day, and I started working on A yesterday. I was working on some Leaflet mapping issues anyway, as I realized that some mapping functions support HTML (like Map.setMarkerText), but when we added Windows mapping, we didn't add that support on Leaflet. So I added that, and then yesterday started work on allowing Leaflet mapping on Android. I've wanted that feature as well, so that users can have a similar experience on both Android and Windows. Also, because the Leaflet mapping code is available in html/mapping/logic-map.html, people can add new features or modify the look of the map. So this will go out in 8.1.

I'll talk to Savy about E. It would be nice to have some consistency across all our systems.

One of my top priorities is to modify CSPro to eliminate the requirement to have fixed-width dictionary items, so that you can declare items as numeric/string without having to specify a width.

Of course, we have a long list of features that would make CSPro much more useful ... if only we had a bigger development team (and a certain future)!

Re: CSPro Open Source roadmap and minimal Developer Guidelines

Posted: May 23rd, 2025, 2:02 pm
by htuser
Thanks Greg for your dedication to CSProusers. Last year another CSProuser stated, you are working with your heart. From my own experience with you, I know this is true!
I'm waiting the day where CSProusers around the world can give you the first Gold Medal!

Thanks for giving us Leaflet also as an optional engine for CSEntry Android. Hope you are using Leaflet 2.0 because most JS developers are more prone to work with modern JS modules.
One of my top priorities is to modify CSPro to eliminate the requirement to have fixed-width dictionary items, so that you can declare items as numeric/string without having to specify a width.
I don't know why you want to eliminate this because, personally, I like when we can define items width... It's why I requested from Savy to have the questionnaire viewer as UI for Android because it use item's width to define HTML form input width.
Of course, we have a long list of features that would make CSPro much more useful ... if only we had a bigger development team (and a certain future)!
I continue to believe that, when CSPro support CAWI (if ever...) it will attract more NSO, universities etc. And more skilled developers will contribute to the project. I also read (https://github.com/CSProDevelopment/csp ... a8fb5f07c4) you are working on some kind of CSPro modules concepts. This will fulfill my dream of "ready to use packages/libs" and grow the CSPro ecosystem with a lot of open source packages that will enrich CSProusers.