Agreed on the subject of settings. I've got yet another code branch on my computer that provides settings serialization for all tabs, that is, saving and loading tab settings to XML files. Not complete yet, no...
However, we need to keep the amount of tabs minimal. Right now we have:
- Manager, responsible for editing profiles, and starting the INDI server and drivers.
- Scheduler, responsible for orchestrating observation sessions.
- Mount, responsible for pointing and monitoring the telescope movement.
- Capture, responsible for exposing one, eventually filtered, optical sensor.
- Focus, responsible for moving the sensor to the optimal focus plane.
- Align, responsible for resolving the position of the telescope.
- Guide, responsible for keeping sensor pixels illuminated by the same sky spatial angle.
- Observatory, responsible for ensuring safe operation of the observation setup.
The next tabs that could appear are a log analyzer and a storage manager. Whatever feature we create, we need to find the best location where to insert it: if a collimation helper is created, then its best location is clearly the Focus module currently.
When development progresses and that helper takes so many settings that it doesn't fit the Focus tab anymore, then, agreed, it should move out. Frankly, right now, most of the features are already covered by Focus.
Unless we get much help, Ekos cannot achieve the same level of specialization as SkyGuide or CCD Inspector. But some neat things can be done.
That's why I listed the steps of the procedure that best fits the OP requirement, in order to find where elements should be fixed, improved or automated. I understand that:
- altering settings with no way to return to stable values is a BIG problem for many of us.
- the cross-hairs overlay should be configurable, and/or should fit star properties detected in the sub-frame.
- process automation would be desirable, in the same way as the polar alignment tool.
Any other ideas?