Initializing the (ecliptic) longitude of perihelion of the earth.
Data is from: http://nssdc.gsfc.nasa.gov/planetary/factsheet/earthfact.html
Hopefully, we can believe the GSFC :)

The aberration computation relies on this, because the aberration
ellipse (as I understand it) is a downscaled "copy" of the earth's
orbit. Seemingly, this was never initialized, so the orientation of
the ellipse was off by 103 degrees!

Currently, we set it to the constant value from J2000.0, but it does
change with time, mostly because of perturbations from the gravity of
other planets (most notably Jupiter) and slightly because of general
relativity.

According to Wikipedia:
https://en.wikipedia.org/wiki/Apsidal_precession#Long-term_climate
the perihelion completes one revolution in 112,000 years, which leads to a value of 11.6 arcseconds / year.
So the orientation of the aberration ellipse is off by about 11.6 arcseconds a year. This is 5.6e-5 radians.

Accordint to Wikipedia on aberration:
https://en.wikipedia.org/wiki/Aberration_of_light and according to
ksnumbers.cpp:157, the constant of aberration is about 20.5
arcseconds, and Wikipedia explains that this is the "radius" of the
approximate circle traced by the stars.

The annual correction to the coordinates of a star due to the
precession of earth's perihelion would be, in the worst case (assuming
linear term in a Taylor expansion of the trigonometry involved), about
(5.6e-5)*0.0167*20.5 arcseconds / year = 1.83e-5 arcseconds/year.
(The 0.0167 is the eccentricity of the earth. Any corrections should
be in the worst-case linear in the eccentricity.)

If we want to be accurate for 10,000 years, we may still get away
without accounting for this, but if our order of magnitude estimate
above is incorrect over those longer timescales, it may be comparable
to typical atmospheric seeing.

But this should be fine for now! Unless we can find the algorithm for
this... :D

Should be backported to 4.10 and cherry-picked into master.

CCMAIL: kstars-devel@kde.org
Cosmetic changes. Some useful comments. Removal of trailing
whitespace.
PM in RA and Dec are essentially derivatives of the RA and Dec taken
in the J2000.0 reference frame (hopefully). Even otherwise, the
difference should be small (and "second order"). One must however be
aware that this kind of a difference does accumulate over time, but it
should still be okay.

However, sometimes, this method is called before dec() is actually
computed! So, replacing dec() by dec0().

Should backport to 4.10, master.

CCMAIL: kstars-devel@kde.org
Initialize dms to NaN, and not zero. This unearthed the last two bugs
that were fixed, but there could be many more yet undiscovered bugs,
and bugs introduced by this change as well.

So watch out for NaNsense in the results of a computation!

CCMAIL: kstars-devel@kde.org
KStars shall do us developers a favour by aborting if there are NaNs
spotted after a coordinate update, or during projection.
Renaming Magnitude -> sortMagnitude internally. Nothing has changed
externally.

+ Cosmetics.
Use NaN magnitudes when it exceeds bounds.
+ Adding a bunch of fields for Deep-Sky and generic objects.

+ Changing the way magnitudes are interpreted. The old "Magnitude"
  field is now the sortingMagnitude, which is used for determining
  whether the object is visible or not, etc. It need not be scientific
  / accurate / reliable data. We could, in principle, use some
  "handwavy" guesses for this field. (eg: if the blue magnitude is
  available, we may "guess" the visual sorting magnitude by guessing
  an appropriate B-V color index. See, eg DeepStarComponent)

  The real Magnitudes are now stored in a Hash. Those are the values
  that are fit for real display.

The question of StarObject:

StarObject already has support for B and V magnitudes separately. The
question is, should we migrate that to the hash? We have many stars --
not sure if it is optimal to migrate the star magnitudes into the
magnitude hash. Besides, stars are replicated using the placement new
operator, so I'm unsure whether that would lead to any additional
complications.

Any ideas from the list?

We could just override mag( band ) in StarObject if necessary.

CCMAIL: kstars-devel@kde.org
Adding forgotten nan.h file. Sorry about the mistake.
Reorganizing and "optimizing" the KSNumbers::updateValues code.

Initially, I made the mistake of thinking that this rather suboptimal
code was in the innermost loop. By the time it dawned on me that it
was kind-of immaterial, I'd already improved it. Anyway, this is more
clean in many other ways too.

Hopefully, it doesn't introduce any bugs. I did check the code twice
just to make sure.
Added more TODO items
SVN_SILENT made messages (.desktop file)
SVN_SILENT made messages (.desktop file)
more NGC/IC names
SVN_SILENT made messages (.desktop file)
Fix for english term: use word "duration" for duration of pulses instead word "length"
Improving capture UI to fit on widescreens and laptops
MAXINDINAME is already defined in libindi
Fix ISR_NOFMANY bug, now checkboxes behavior is correct
Fix bug with out of range index in ST4