knro wrote: What do you suggest? I'm all open for it. KStars IS a complex project. Maybe create a list of simple tasks to get started?


Based on my experience what could help both on Ekos and INDI development is:
- More tutorials: there are indeed tutorials available both for driver and client development, but they are covering basic topics only (that's the list of simple tasks that you mentioned above I guess).
- Coaching / mentoring: having a senior developer investing time coaching new developers.
- Interactive online session where questions could be asked.

The APIs are well documented but I struggle to understand the lifecycle of a request and the workflow in general. Using the debugger helps but still the whole picture is missing: I wrote a couple of INDI drivers, they do work but still I do not understand the class hierarchy nor how the methods are related.
Here an overview of the architecture and a list of the main classes / methods could help.

As you said, Kstars is complex as a project. And beside its functional complexity, you have to learn C++ and QT; consider that most developers are now used to Python and Java or JS.
Any language can be learnt but having limited time and with no previous knowledge of C++, even manipulating numbers is hard.

To me if Ekos could support PyQT (don't know if bridging is even possible) would be a great help.
QT is great and I don't know if there are better alternatives but the 'everything is an object' approach is nice but sometimes slows things down.

I really appreciate that you are open to suggestions Jasem and hope that others can contribute to this discussion.

ferrante

Read More...