- 1 What this page is about
- 2 Keeping track of Development
- 3 The Tasks
- 3.1 1. Complete the Sky Calendar
- 3.2 2. Debug the Conjunction tool
- 3.3 3. Fix the angular distance ruler crash
- 3.4 4. Fix all those translation bugs
- 3.5 5. Generalize JupiterMoons, SaturnMoons
- 3.6 6. Generalize the Jupiter's Moons Tool
- 3.7 7. Comets that looks like comets!
- 3.8 8. Fix those inconsistencies with comets
- 3.9 9. Merge NGC data from the SAC catalog
- 4 Ideas are welcome!
What this page is about
This page is intended to list out some small jobs that, if completed, would help KStars become better and more usable. There are both easy ones and hard ones.
If you are interested in contributing to KStars, but don't know where to start, this is probably the best place.
Keeping track of Development
If you prefer IRC, we hang out on #kde-edu on irc.freenode.org
We keep track of bugs and wishlists on The KDE bugzilla
Please do not hesitate to ask if you need help with contributing! We're always looking out for contributors and will be happy to help you out.
1. Complete the Sky Calendar
There's an unfinished tool out there in Tools -> Sky Calendar, that looks like just a bunch of curved lines strewn over some weird shaped region with a bunch of months labeled. As you can clearly see, that tool requires labels for those lines and a lot of love. Here's the commit that started the tool which describes the author's vision for the tool. It's now unmaintained, and it would be nice if someone could add those labels that those lines really deserve and make this tool a complete usable thing.
2. Debug the Conjunction tool
The Conjunction tool, for some reason, doesn't seem to be predicting solar eclipses correctly. There are some bugs on our bugzilla related to this as well. It would be useful if the Conjunction tool were made completely bug-free
3. Fix the angular distance ruler crash
There's an irritating crash condition on our bugzilla where trying to measure angular distances hangs KStars under some conditions. The backtrace is right there. It will be useful if this is fixed.
4. Fix all those translation bugs
Now, this is a big task.
SkyObject classes (see skyobject.h under kstars/skyobjects) should have some standard way of storing names. Currently, some SkyObjects store untranslated names and some store translated names, leading to a big mess. SkyObject should probably store untranslated name strings internally, and return untranslated names upon calling name(). The objectNames() hashes should ideally have untranslated names as well.
So how do we find by translated name? The best way, probably is to have a "reverse translation hash". Since very few objects have translated names, it might be easy to maintain a global hash of translated names vs. untranslated names in some convenient place (probably as a static member of SkyComposite) and do searches for translated names through this.
Implementing this will fix a whole lot of translation-related bugs that are on our bugzilla, and make life for people who use localized versions easier.
5. Generalize JupiterMoons, SaturnMoons
This was originally a GSoC idea, but I thought it was a bit too "small" for a whole summer. The idea is to implement a class that handles moons of planets in the solar system in KStars.
Currently, we have JupiterMoons and SaturnMoons (thanks, Vipul!) classes. What should be done now, is to pack all the machinery that goes into these two classes into one generic class (probably called 'SolarSystemMoons'), various instances of which, could represent the moons of Jupiter, Saturn, Mars...
All our class would need to do, to assume the form of say, JupiterMoons, would be to read off data corresponding to JupiterMoons from some file, say "solarsystemmoons.dat"!
Now, the next question...
6. Generalize the Jupiter's Moons Tool
See Tools -> Jupiter's Moons. What if I could do this in general with SolarSystemMoons? [See earlier task for details]
7. Comets that looks like comets!
Comets in KStars are currently drawn as dull green circles (at least in the default color scheme). That's not what they look like, in reality!
The machinery required to estimate nucleus and coma sizes, and tail lengths of comets are all there in KSComet and KSPlanetBase. What needs to be done, is to provide a proper representation of a comet based on these data on the Sky Map.
Remember that a comet's tail points away from the Sun! You can use this to fix the direction of the tail - so you have all information required to draw the comet.
Re-implement CometsComponent::draw() to draw better comets.
8. Fix those inconsistencies with comets
Jeamy Lee, a KStars user and contributor, notices that our Sun-Comet distances are wrong! This makes all calculated parameters come out incorrectly. Find his mail with some details here.
The aim of this task is to compare some more data against other software, step through the code, and find out where we are going wrong. You could use Jeamy's MPC Reader site to download the latest comet elements in KStars' format.
9. Merge NGC data from the SAC catalog
The Saguaro Astronomy Club catalog* is an amazing catalog with a lot of deep-sky objects within the reach of amateur astronomers. It has data for most (all?) of the NGC objects, but not for all IC objects. Our current NGC/IC catalog which you can find in data/ngcic.dat is far from accurate, but has data for all NGC/IC objects. Merging the SAC catalog and KStars' NGC/IC catalog would help a lot of our users.
[*We have obtained permission to use it with KStars]
Ideas are welcome!
If you are a user of KStars and have some cool, simple ideas that would make your experience with KStars better, you are welcome to add them to the list above, or discuss them on the kstars-devel mailing list (or post them as wishlists / bug reports on the bugzilla).