<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Verdana, Geneva, sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
Hi,</div>
<div style="font-family: Verdana, Geneva, sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Verdana, Geneva, sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
I was wondering, do the documentation/user manual (docbooks) need updating with the AH feature?</div>
<div style="font-family: Verdana, Geneva, sans-serif; font-size: 10pt; color: rgb(0, 0, 0);">
Since you are alsmost done, you can update the documentation too while it is still fresh in your memory.</div>
<div>
<div id="appendonsend"></div>
<div style="font-family:Verdana,Geneva,sans-serif; font-size:10pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Verdana,Geneva,sans-serif; font-size:10pt; color:rgb(0,0,0)">
Regards,</div>
<div style="font-family:Verdana,Geneva,sans-serif; font-size:10pt; color:rgb(0,0,0)">
Patrick</div>
<div style="font-family:Verdana,Geneva,sans-serif; font-size:10pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr">Date: Tue, 6 Apr 2021 11:27:59 -0700<br>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">From: Hy Murveit <murveit@gmail.com><br>
To: Wolfgang Reissenberger <sterne-jaeger@openfuture.de><br>
Cc: Eric Dejouhanet <eric.dejouhanet@gmail.com>, Hy Murveit<br>
<hy@murveit.com>, KStars Development Mailing List<br>
<kstars-devel@kde.org><br>
Subject: Re: Artificial Horizon<br>
Message-ID:<br>
<CA+B1P8vxdM3eUyy1Lp5icat-V6_KRAspzkKx2QwwL5aXqP2AyQ@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Eric, Wolfgang, et al,<br>
<br>
I fully support your efforts to add testing to KStars. To that end, I have<br>
done a few things related to my MR<br>
<a href="https://invent.kde.org/education/kstars/-/merge_requests/263">https://invent.kde.org/education/kstars/-/merge_requests/263</a><br>
<br>
1) I added a full UI test to the MR. Check it out! It's my first UI test,<br>
and as far as I can tell, the first one that's not Ekos related. Of course,<br>
let me know if there's some way to improve the test.<br>
<br>
2) I removed the scheduler changes from the Artificial Horizon MR. The AH<br>
feature and the Scheduler are two separate things, and combining them in<br>
this MR will only delay the artificial horizon code unnecessarily, and make<br>
the changes less modular etc.<br>
<br>
I believe that my artificial horizon MR is ready for integration (pending<br>
review).<br>
<br>
I hope to soon propose minimal changes to the scheduler to take advantage<br>
of the Artificial Horizon feature, similar to what I showed up above. I<br>
agree that any such changes need to be supported by testing, and I will<br>
look into ways to do that. Of course, I don't want to step on any toes, or<br>
mess up any scheduler work you two have planned. It's my hope that<br>
computing job schedules could be Unit Tested, as opposed to UI Tested, and<br>
avoid some of the thorny issues in the scheduler related to starting and<br>
stopping of jobs. In any event, stay tuned, and I'll let you know my future<br>
proposals when they're more clear to me. If they interfere with your ideas,<br>
just let me know.<br>
<br>
Hy<br>
<br>
</div>
</span></font></div>
</div>
</body>
</html>