By the poetic tone of my commit messages, I presume it is quite clear
that I am very sleepy, which is why not a single of these FIXMEs have
been attended to today. Hopefully, some day...

There is a bug which induces a crash when writing the observing wish
list, and ends up truncating the wish list. This can be very
frustrating because of the loss of the wishlist.

Although the bug still needs to be found and fixed, this change in
code at least prevents the wishlist from being truncated upon crash.

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

CCMAIL: mutlaqja@ikarustech.com

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Checking for timeout in both Ekos starting phase and when connecting INDI devices. Better fail than wait forever

BUGS:370061

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

KSDssDownloader commits suicide, so code like:

KSDssDownloader *foo = new KSDssDownloader( ... );
connect( foo, ... );

has potential to fail.

N.B. The better and more correct fix would be to make the one-shot
use-case of KSDssDownloader a static method, just like the one-shot
QTimer. It can internally create a class instance and safely handle
its destruction.

Must use deleteLater() as there may still be events to process

This seems to fix the crash (at least I cannot reproduce it as easily
any more)

It seems more natural to provide more vertical real estate for the
Table View objects, since the list spans a fairly long length in
typical cases. Just showing 4 rows is not very useful, but showing as
few as 2 columns should still be useful (it takes less scrolling to
scroll through the small number of columns).

However, we would want to make the first column, the one with the
names of objects, always visible irrespective of how we scroll
horizontally. To this end, there is a solution in the form of a Qt
example which we can use in KStars with minimal modification:

http://doc.qt.io/qt-5/qtwidgets-itemviews-frozencolumn-example.html

N.B. The BSD License used in the example is GPL-compatible.

Other improvements necessary are:

1. Put the list on the left -- feels more natural.

2. Move the time schedule option in the Session View below the table
   view.

3. Gray out the date box in WishList mode to indicate its irrelevance?
   It is technically not irrelevant since the RA/Dec shown are
   apparent coords! Maybe this should change.

4. Show some vital info about the object in a label

5. Make sure buttons don't expand if we resize -- only the table view
   must expand to fill up as much real estate as possible.

6. Allow the user to hide / show columns in the TableView.

7. Make sure the "Minify" option works well.

8. Would be nice if we could "minimize" the observing list to an icon
   in the bottom-right of the main window.

Since the FindDialog now uses objectLists to search through the
catalogs, custom catalogs must add object names to the objectLists
data structure even in regular version of KStars, not just in
KStarsLite.

QDateTime::currentDateTimeUtc() is different from
QDateTime::currentDateTime().

Q: Why aren't the date time's timezone-independent in their internal
representation of time? After all, JD is not location-specific?

We need some tests for KStarsDateTime and some refactoring so as to
make it more robust and intuitive.

Fixes a bug where the (RA, Dec) for simulation clock epoch was
identical to the J2000 coordinates in the details dialog, if the
object was not rendered on the screen. This is relevant, for example,
when invoking the details dialog from places other than the sky map
such as the Observation Planner.

The corrections are as follows:

1. Call updateCoords() on the Sky Object with the current update
   KSNumbers.

2. Set the epoch from the coordinates that we are actually displaying,
   i.e. using lastPrecessJD.

CCMAIL: mutlaqja@ikarustech.com

BUG:

Robert Lancaster authored Oct 02, 2016 and Jasem Mutlaq committed Oct 02, 2016

 themes using the fromTheme method like OS X, Windows, and some Linux Distros.
  If there is no system theme, it tries to set the theme to one of the bundled
 themes if possible, but also adds the fallback method for loading icons
 without a theme to each icon if that doesn't work.   Added an icons directory
 to keep the theme icons and toolbar icons separate from the other data.
 Included two bundled custom themes, based on breeze and oxygen.  Also fixed
 the call to the "geographic" icon and the "edit indi profile" icon since they
 may have been referencing the wrong icons.

CCMAIL:kstars-devel@kde.org

Adding a new workflow in the Observation Planner that helps find
objects for observation without having to prepare a session plan with
assigned times.

1. Add all objects that you want to observe to the Wish List

2. On the observing field, sort by the "Current Altitude" column in
   descending order. The column contains the percentage of the maximum
   altitude currently achieved by the object. The altitude uses the
   geographic location set in the observation planner, but _ignores_
   the date field -- so it is really current in system clock time.

3. The list is automatically updated and dynamically sorted every 2
   minutes, so you can always observe the objects at the top of the
   list. As objects rise and set, they move up/down the list.

Improvements needed:

1. Support multiple wishlists, save wishlist, load wishlist etc.

   [ Or alternatively, move the feature to the session plan, although
   the session plan file format is more complicated]

2. Make the workflow more obvious

   (Any pointers on how to do this will be very helpful)

3. Support demotion of objects after "checking them off"

4. Have an option to demote objects that are in the Dobsonian hole.

FEATURE:
GUI:
CCMAIL: kstars-devel@kde.org

Add two convenience methods to SkyPoint that return the maximum and
minimum altitude of an object for a given location (latitude).

Jasem, could you please look at the guide.h self-include and make sure
I didn't do anything bad?

CCMAIL: mutlaqja@ikarustech.com