Guider binning

Jasem Mutlaq mutlaqja at ikarustech.com
Wed Jun 3 21:33:23 BST 2020


Hi Eric,

Are these tied to the equipment profile? or does the user have to go to
each module and load the settings every time?

--
Best Regards,
Jasem Mutlaq



On Wed, Jun 3, 2020 at 12:03 PM Eric Dejouhanet <eric.dejouhanet at gmail.com>
wrote:

> Hello,
>
>
>
> Sorry for taking so long to get the mailing list account back.
>
>
>
> I’d like to step in to tell what I pondered to implement for the Focus
> module.
>
>
>
> I believe each Ekos module should be able to save and load its settings to
> files. This comes in addition to the regular Options mechanism, which are
> the “current” settings. We already have this for the Capture module as Ekos
> Sequence .esq files, and for the Scheduler module as Ekos Schedule .esl
> files.
>
>
>
> My proposal is therefore to have Ekos Focus, Align, Guide and Observatory
> settings serialized like Capture and Schedule. Because that would make that
> much file extensions, I propose to embed the type of settings inside the
> serialized file. Additionally, I propose to disconnect the format of the
> file from the actual content, so that a « settings list » suitable for a
> particular module could be stored as XML, or JSON, or whatever
> serialization plug-in we may add to Ekos.
>
>
>
> On the settings themselves, Qt has a generic Model/View Framework using
> QAbstractTableModel. I propose to implement a ModuleSettings class above
> the table specialization of this framework. This will offer a low-cost
> generic view of Module settings that can be included as a summary in each
> module, read-only but eventually with modification features.
>
>
>
> Then each Module can declare its settings, connect them to UI elements,
> and gain automatic serialization. This will help separating the view and
> the data in our architecture (it really needs that).
>
>
>
> My original idea was to store all Module settings in Scheduler settings
> (tree+table model), and forward them when initiating observation steps. In
> the preliminaries I worked out, I could also redesign the Scheduler UI into
> a (relatively ugly) tree view that I showed last year in the forum (or was
> it even before?).
>
>
>
> -Eric
>
>
>
> - eric.dejouhanet at gmail.comhttps://astronomy.dejouha.net
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20200603/414bfc24/attachment.htm>


More information about the Kstars-devel mailing list