[Kstars-devel] Integrating KStars Lite in KStars
Artem Fedoskin
afedoskin3 at gmail.com
Sat Apr 30 16:52:22 UTC 2016
>> This is because creating a separate project for kstars-lite would make
it obsolete and out of date very soon with the main branch.
That is exactly the reason why I want to use #ifdef. It would be hard to
maintain separate project.
Thank you!
Regards,
Artem
2016-04-30 18:51 GMT+02:00 Artem Fedoskin <afedoskin3 at gmail.com>:
> >> This is because creating a separate project for kstars-lite would make
> it obsolete and out of date very soon with the main branch.
> That is exactly the reason why I want to use #ifdef. It would be hard to
> maintain separate project.
>
> Thank you!
>
> Regards,
> Artem
>
> 2016-04-30 18:42 GMT+02:00 Jasem Mutlaq <mutlaqja at ikarustech.com>:
>
>> Hi Artem,
>>
>> 1. I think the #ifdef while would make the code uglier but it is the way
>> to go. This is because creating a separate project for kstars-lite would
>> make it obsolete and out of date very soon with the main branch.
>> 2. The updatePlanets is to update all solar system bodies including
>> computation of their current JNow coordinates and Equatorial to Horizontal
>> conversion. This happens on a faster update cycle than regular 'update'
>> which is called once every solar minute. I renamed the function and added
>> some documentation so it becomes clearer.
>>
>> Good luck and keep us posted with your progress!
>>
>> Regards,
>> Jasem
>>
>>
>> On Sat, Apr 30, 2016 at 7:01 PM, Artem Fedoskin <afedoskin3 at gmail.com>
>> wrote:
>>
>>> Dear KStars team
>>>
>>> I'm currently investigating the way of integrating KStars Lite in KStars
>>> and have a bunch of questions:
>>>
>>> 1.I decided to write from scratch KStars class, as it is a subclass of
>>> KXmlGuiWindow, which won't be used in Lite version, SkyMap class and
>>> everything related to old SkyMap. However, I will just add new code and
>>> block the old one in such classes like KStarsData and derivatives of
>>> SkyComponent/SkyComposite with #ifdef KSTARS_LITE macros, like it is
>>> already done with INDI and OpenGL support. Is it ok?
>>> 2. What is the difference in, for example, SolarSystemSingleComponent
>>> between update() and updatePlanets() functions? The latter recomputes
>>> position of planet with new KSNumbers value, right?
>>>
>>> I will start by creating new KStarsLite class, add all stuff related to
>>> loading QML files and then begin working with SkyMap. For now I will use my
>>> UI prototype, that I showed in proposal, but later I will change it with
>>> the new one, which will be probably based on Kirigami framework.
>>>
>>> _______________________________________________
>>> Kstars-devel mailing list
>>> Kstars-devel at kde.org
>>> https://mail.kde.org/mailman/listinfo/kstars-devel
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Jasem Mutlaq
>>
>>
>> _______________________________________________
>> Kstars-devel mailing list
>> Kstars-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/kstars-devel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kstars-devel/attachments/20160430/c1cdaa51/attachment.html>
More information about the Kstars-devel
mailing list