gmane.comp.kde.devel.kstars

Re: GSoC 2012: Project Introduction: Logs and Data

Aleksey Khudyakov — 2012-05-02T10:03:41

First and obvious problem is then nor name, nor name and HD index are
good identifier for sky object. First most faint stars are nameless, and most of
faint stars even do not have HD index (if we add USNO catalog). And to make
things worse names depend on current language. I think it already caused bugs

So some robust identifier is needed. There is uid method which is remnant of
unsuccessful attempt of creating such id. It's buggy and fairly
bitrotten but can use
it as starting point. There were few discussions about it on the list.

Re: GSoC 2012: Project Introduction: Logs and Data

Rishab Arora — 2012-05-01T14:37:42

Apologies for the late reply.
Very short version: http://blog.rishab.in/the-log-viewer/

Yes, I plan to separate the storage of observation logs from SkyObject.
From my current understanding, KStars currently writes the user log to a
file as well as stores it in "userlog.dat" when it needs to save data.
During initialization, the log is read from the text files and stored with
the SkyObject.

In my proposal, I plan to make a separate database in which I will (along
with all required information like seeing, equipment etc) store an
identifier for the star. This identifier could be the 'name' as is being
used currently, but I plan to use the HD index instead so that the logs
aren't limited to a set number of stars. Similarly, a unique identifier
(which will be assigned when I port the DSO catalog to SQLite) will be
used.

Using the name will make it work for all the objects it currently supports
at least.

When the detail dialog will display the log tab, I plan to query the
database and populate a list of logs in a UI similar to this.
http://blog.rishab.in/wp-content/uploads/2012/04/mockup.png


"""
From UI point. it's very bad to force user to fill in _all_ fields.
Users are lazy and always have strange ideas. It's better to avoid
annoying constraints like: «you'll have to explicitly state all
information».
"""

I agree, but what I was pointing out was that in the current log
implementation, one needs to write these fields if he/she needs them.
In the new implementation, all this will already be filled.

There's a very rough diagram for the user database at
http://blog.rishab.in/wp-content/uploads/2012/04/user.jpeg . Though not all
fields are represented here, it should show how I plan to store the logs,
and how I plan to retrieve redundant information from KStars instead of
needing the user to type.

I would appreciate any advice/suggestions you have. It's better to get
things reviewed before I implement something that is wrong.

Thanks for taking the time to read through this. :)

Rishab Arora
(spacetime)
< at >spacetime29 <https://twitter.com/#%21/spacetime29>
Find me on Google+ <https://plus.google.com/118197889888669218025/posts>




On Sun, Apr 29, 2012 at 11:00 PM, Aleksey Khudyakov <
alexey.skladnoy< at >gmail.com> wrote:

_______________________________________________
Kstars-devel mailing list
Kstars-devel< at >kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

Fwd: Re: GSoC 2012: Project Introduction: Logs and Data

Aleksey Khudyakov — 2012-04-30T09:26:56

Forgot to CC list

-------- Original Message --------
Subject: Re: [Kstars-devel] GSoC 2012: Project Introduction: Logs and Data
Date: Sun, 29 Apr 2012 21:30:58 +0400
From: Aleksey Khudyakov <alexey.skladnoy< at >gmail.com>
To: Rishab Arora <ra.rishab< at >gmail.com>

On 26.04.2012 20:44, Rishab Arora wrote:
There is a problem. Current implementation stores logs and some other
info in the SkyObject. This approach is problematic for following
reasons: is object is destroyed all data is lost. At the moment only
faint star are loaded and unloaded to/from memory on demand.
Galaxies are very numerous too so at some point we may want to unload
them too. Also there is no easy way to get all observation logs etc.

It sounds like you want to store observation log separately from
sky object. So how do you plan link them?

 From UI point. it's very bad to force user to fill in _all_ fields.
Users are lazy and always have strange ideas. It's better to avoid
annoying constraints like: «you'll have to explicitly state all
information».

Re: GSoC 2012: Project Introduction: Logs and Data

Rishab Arora — 2012-04-26T16:44:56

Hey Aleksey!

I'll maintain communication using the mailing list for sure.

Regarding the observation logs, currently we have a feature which lets us
save a plain text entry for named objects (accessed by right clicking ->
logs). So if you wish to store what you saw while observing, say Saturn,
you'll have to explicitly state all information like the equipment you've
used, date, time etc which is already available to KStars.
I plan to replace this view with a new interface linked with a database.
Hence, when you right click and select Logs in the proposed implementation,
you'll get a list of all previous entries. And the option to add new
entries. And to export these entries (as OAL files, hopefully)



On Thu, Apr 26, 2012 at 6:23 PM, Aleksey Khudyakov <
alexey.skladnoy< at >gmail.com> wrote:

_______________________________________________
Kstars-devel mailing list
Kstars-devel< at >kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

Re: GSoC 2012: Project Introduction: Logs and Data

Aleksey Khudyakov — 2012-04-26T12:53:27

Could you elaborate this, In particular what are observation logs and how do
you plan to store them? There are some feature which is vaguely simalar,
although it doesn't seem to be very usable.


Yes. Currently text files are parsed in very ad hoc way. We had few crash
bugs because parsers didn't check for all cases. It will be useful by itself.




Please keep you email communication on the mailing list. Probably
I and others will have something to say as well

GSoC 2012: Project Introduction: Logs and Data

Rishab Arora — 2012-04-25T21:24:57

Hello everyone! :)

I'm Rishab, and as Samikshan mentioned, one of the two students accepted
for KStars this year! Needless to say, I'm really excited to work on KStars
this summer :)

I am relatively new to the community, so I'll take a moment to introduce
myself. I'm Rishab Arora (idling on IRC as 'spacetime'), an undergraduate
student of Information Technology from New Delhi, India. Currently in my
third year of college, I take particular interest in handling large amounts
of data. I'm an amateur astronomer and have a habit of naming devices,
heuristics and algorithms (or anything I can name) after heavenly bodies,
so I think I should fit right in. ;)

I'll start with a small description of what I've be aiming for this summer.
My proposal "Improving Data Storage, Logs and adding DSO catalogs to
KStars" involves
a. building a log viewer which will enable users to 'store' observation
logs in an internal database
b. improving the way data files handled, specifically the parsing of text
files. I'll be making it more robust and extensible.
c. storing Deep Sky Objects in a database to solve some problems we're
facing now that KStars is expanding the its datastore
d. Using the new database structure, add catalogs to KStars


Out of these, I feel adding the ability for the user to regularly store and
manage observation logs inside KStars itself would turn out to be quite
useful. Akarsh is my mentor for this project and I'm already getting a
glimpse of all the excitement (and lots of work! ) awaiting me. :) I'll be
blogging about the project and my experiences at blog.rishab.in regularly.
I'll add more details as they are discussed on the blog itself.

Although most of my interaction regarding KStars has been with Samikshan,
Akarsh and Rafal, I've worked with KStar's code so I am only familiar with
the work of other contributors. It would be great if I could get to know
everyone here! :)

Cheers!
Rishab Arora
_______________________________________________
Kstars-devel mailing list
Kstars-devel< at >kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

GSoC 2012 Project Introduction: More beginnerfriendly KStars

Samikshan Bairagya — 2012-04-25T17:29:00

Hi Everybody!

My project proposal for Google Summer of Code, 2012, with the idea -
"Make KStars more usable for beginner astronomers by adding
'What's Interesting...' feature to KStars and by making 'Star Hopping'
feature user-configurable" - has been accepted. It is really exciting
and I am confident that this would be a rewarding experience for me,
the community and the users of KStars.

Through these features KStars will become more friendly and usable for
beginner and intermediate level astronomers.

Anyway, even though I am not new to this list and have posted here in the
past, I would like to introduce myself here in brief. I am an undergraduate
student of Computer Science and Engineering at National Institute of
Technology in Durgapur, India. I have made contributions to KStars as a
part of Season of KDE, 2011 and afterwards.

To know more about me, my project proposal and previous work you can
take a look at my blog at http://samxan.wordpress.com/ . I will regularly
be posting there about my work progress, thoughts and ideas.

Also it is wonderful that KStars has been allotted 2 slots for GSoC this
year. I am looking forward to working alongside Rishab Arora who'll be
working on "Improving Data Storage, Logs and adding DSO catalogs to
KStars".

Currently I am a bit occupied with my college examinations. Unfortunately,
this phase will continue till the 1st week of May. Can't wait to start work
after that.

Cheers,
Samikshan Bairagya.
_______________________________________________
Kstars-devel mailing list
Kstars-devel< at >kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

Re: [kstars] kstars: Hmm, we shouldn't have a KStars-standard gitignore. Let users define

Rafal Kulaga — 2012-04-25T07:50:54

Of course, what entries do we want to have in .gitignore is a
different story ;-)



2012/4/25 Rafal Kulaga <rl.kulaga< at >gmail.com>:

Re: [kstars] kstars: Hmm, we shouldn't have a KStars-standard gitignore. Let users define

Rafal Kulaga — 2012-04-25T07:41:47

Hi Akarsh!

It's not unusual for the repo to have its .gitignore. Even the kernel
repo has one :-) I'd leave it.

Cheers,
Rafal


2012/4/25 Akarsh Simha <akarshsimha< at >gmail.com>:

Re: Errors in StarBlockFactory / StarBlockList

Aleksey Khudyakov — 2012-04-21T16:47:43

I don't know how things work but what about checking checking
invariants after every modificication of whatever gets modified.
Programm will be slow but you'll find exact moment of breakage

Errors in StarBlockFactory / StarBlockList

Akarsh Simha — 2012-04-18T07:46:24

I keep getting this and other similar output on the terminal:

kstars(30667) StarBlockFactory::markNext: WARNING: Marking block with faint mag = 12.79 after block with faint mag 15.26 in trixel 32606

This is something very bad, because if this is real, then half the
stars are not going to be drawn. Looking through the code, I can't
tell why this is happening. I ran a check on my catalog for incorrect
magnitude order, but the tester (data/tools/nomadbinfiletester)
reported no errors.

This was very likely introduced after Akademy 2008 (August 2008),
because I'm almost certain that I weeded out most of the bugs before
that, and something like this would have almost certainly caught my
attention. However, these bugs are also hard to find because they
could happen only for specific regions of the sky. In this case, the
output on my terminal shows this happening for trixels 32606 and 32607
which seem to lie around M 34 in Perseus.

Alexey introduced some changes in this code, but looking through them,
I don't see anything that can cause this. The StarBlock constructor
sets the faintmag of StarBlocks to -5.

If anyone has some ideas, I'd appreciate them. I'll probably give it a
bit of my time today.

Also, if all goes well, I'm going to be at the Texas Star Party this
weekend. I'm trying to use the Observation Planner feature in KStars,
both because it's very convenient (I've tried it before on the
field). There are several bugs / usability issues, though, and I'm
trying to fix some of them in the interest of improving KStars and
making my observation sessions smoother at the same time. :). I'll let
you know how the "field test of KStars" goes ;-)

Regards
Akarsh

Re: GSoC slots

Rafal Kulaga — 2012-04-16T06:47:43

Hi everybody,

+1 to this. I would also like to add that we have received 3 proposals
based on the same project idea (WUT & star hopping) and they are all
really good. It was hard to pick the best one.

Cheers,
Rafal



2012/4/11 Akarsh Simha <akarshsimha< at >gmail.com>:

USNO NOMAD catalog artefacts near bright stars

Akarsh Simha — 2012-04-15T21:22:47

The USNO NOMAD catalog seems to have artefacts near bright stars. I'm
guessing that these owe their existence to diffraction spikes and
glare, as is seen in the POSS plates. AFAIK, NOMAD uses the POSS
plates to find stars.

For comparison, consider the query on NOMAD here:
http://www.nofs.navy.mil/tmp/fchTdJ3EC_fch.html

The same field, with the same central star in the POSS [Blue] plates:
http://archive.stsci.edu/cgi-bin/dss_search?v=poss2ukstu_blue&r=18+12+24&d=-07+17+44&e=J2000&h=15.0&w=15.0&f=gif

Notice how some stars are spurious and some magnitudes are
over-estimated in NOMAD, possibly due to the diffraction spikes.

The same artefacts are found in KStars -- all bright stars usually
have a string of stars flanking them, that are usually aligned
approximately with the north-south direction. I guess these artefacts
are the result of diffraction spikes. It is therefore unlikely that
these disagreements with DSS images are bugs in KStars -- they are
more likely catalog artefacts.

Regards
Akarsh

Re: Some observations regarding USNO NOMAD in KStars

Akarsh Simha — 2012-04-15T08:40:52

This is embarrassing -- I didn't know revision hashes change when
rebasing. Here's the correct revision number:

3c6204ab85ad7c010bd03f647196def875f9d7f4 (currently HEAD)

Regards
Akarsh

Re: Some observations regarding USNO NOMAD in KStars

Akarsh Simha — 2012-04-15T08:34:58

Hi,

Here's a tarball containing a bunch of plots of the region around
trixel 12310. The x-axis is right ascension in hours and the y-axis is
declination in degrees.

http://www.ph.utexas.edu/~asimha/KStars-NOMAD-Tests.tar.bz2

Test 1: Shows that there are sizable differences between data dumps of
     USNO NOMAD made with different criteria.

Test 2: Shows the effect of precession computed by KStars, between
     J2000.0 and 2012.3

Test 3: The precessed coordinates of Test 2 were shifted by constant
     RA and Dec shifts to make them coincide with the unprecessed
     J2000.0 coordinates. Note the existence of spuriously
     introduced precessed stars (green crosses that are not
     coincident with a red plus). Note also the existence of
     outliers that did not have precessed counterparts (red plusses
     that are not coincident with green crosses). Note also that
     these red outliers form a nearly right-angled triangle on the
     top right of the image. Hmmm...

Test 4: The red outliers from the previous figure are all from Trixel
        12310 for some strange reason, and not the neighbouring trixel
        -- they all coincide with a blue asterisk from Trixel 12310.

Test 5: Note that some stars that were existant in trixel 12310 never
     got JITUpdate()-ed despite making magnitude limits for trixel
     12310 as high as 30 (red plusses without coinciding green
     crosses). The reasons could be legitimate (i.e. some other
     check failed; not checked yet). These could be the same stars
     that were the red outliers in Test 3 (not checked).

Finally, attached is a diff containing the extremely ugly edits that I
used to do the debugging. I'm attaching them mostly for reference and
not so much for future re-use. They are applied against
29ef0d11f906963ce4d0d066df781b483a6a0ca0, which I will push into
master in a few minutes.

Regards
Akarsh_______________________________________________
Kstars-devel mailing list
Kstars-devel< at >kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

Some observations regarding USNO NOMAD in KStars

Akarsh Simha — 2012-04-15T07:54:33

Hi

I did some tests on the USNO NOMAD catalog machinery in KStars
today. I'm sending a copy of these to the mailing list both for
documentation / archival purposes and so that others can look it up
when required.

This was prompted because I noticed that the star field in Trixel
12310 (of the "deep" level 6 SkyMesh) did not seem to match with the
DSS image of the same region. This could involve precession and might
be related / a bug introduced by the short-circuiting of precession,
nutation and aberration computations when the simulation time elapsed
since the last such calculation is less than about a minute (see
revision 832469e64f222e6d1cc9da77a7b4587db20c05ba). Or it could just
be that the catalog (with the search criteria used to limit down to a
100 million stars in KStars) disagrees with the POSS plates.

The following are the results of some checks done against trixel 12310
/ a rectangular patch in (RA, Dec) around trixel 12310:

1. (ra, dec) seems to be recomputed when the simulation clock is
   sufficiently slewed.

2. (ra0, dec0) of stars in KStars as dumped from JITUpdate() in a
   rectangular patch near Trixel 12310 agree with the dump of trixel
   12310 from USNO NOMAD 1e8.dat

3. (ra, dec) computed from (ra0, dec0) by accounting for precession
   looks locally like a shift in RA and Dec for the most part, which
   it should. However, there were some outliers observed! This needs
   investigation!

4. The subset of the USNO NOMAD catalog we have was made with the
   following search criteria:
   (is a 2MASS star) AND ( V <= 16.5 OR R <= 16.0 OR B <= 16.0)

   (See http://markmail.org/message/dz7g3wnzl2wmfyyk for more)

   There are noticable differences when different bands of magnitude
   are used to filter between 12 and 16th mag using USNO's NOMAD
   search facility:
   http://www.usno.navy.mil/USNO/astrometry/optical-IR-prod/icas/fchpix

   This could explain the difference between the POSS plates and
   KStars rendition of the same star field. Another possibility is
   that there are NOMAD catalog artefacts. In either case, it looks
   like the fault is not within KStars. Trixel 12310 raised my
   suspiscion because it seems to have a rich band of stars, but that
   artefact exists in the catalog as well, as is verified from the
   plots generated by USNO's website.

5. Despite setting magnitude limits to 30 on trixel 12310, some stars
   that were present in trixel 12310 were never displayed -- or at
   least JITUpdate() was never called on them. But these were very few
   in number.

Puzzles:

1. Some stars seem to have a wildly off value for (ra, dec) - (ra0,
   dec0) from the rest of the stars. It is unlikely that the cause of
   this is proper motion since faint stars have little proper motion
   owing to their distance from the earth. Looks like precession is
   not being applied uniformly to all stars.

2. Heisenberg stars: Some stars seem to suddenly disappear / change
   their positions when you try to zoom in on them. After a couple of
   tries, it usually reaches a "steady state" (an eigenstate :P). This
   will probably not show on my analysis since I dump every star
   that's JITUpdate()-ed, and not those that survive in the "steady
   state"
   I think this strongly suggests that StarBlockFactory's marking and
   block-disposal / reallotment scheme is the culprit.

3. Imprecise precession: More tests need to be done until the
   short-circuiting of precession is verified to work. Puzzle #1 may
   be related to short-circuiting of precession.

Maybe it is a good idea to permit the precession short-circuiting to
be something we can turn on/off from the advanced options.

I'll hopefully have some figures coming up.

Regards
Akarsh

[kstars] kstars: 1. Rename the 'Backends' tab under 'Advanced' options to 'General' and

Akarsh Simha — 2012-04-14T12:41:54

Git commit 624f0c5faba1daf3558159bcd1eff7fe35c0e4cb by Akarsh Simha.
Committed on 14/04/2012 at 14:37.
Pushed by asimha into branch 'master'.

1. Rename the 'Backends' tab under 'Advanced' options to 'General' and
   add a "DSS Imagery" group in it.

2. DSS Image default size / padding is now configurable.

CCMAIL: kstars-devel< at >kde.org

M  +13   -0    kstars/kstars.kcfg
M  +4    -3    kstars/ksutils.cpp
M  +152  -47   kstars/options/opsadvanced.ui
M  +1    -1    kstars/tools/observinglist.cpp

http://commits.kde.org/kstars/624f0c5faba1daf3558159bcd1eff7fe35c0e4cb

diff --git a/kstars/kstars.kcfg b/kstars/kstars.kcfg
index 633c4d4..258d0f6 100644
--- a/kstars/kstars.kcfg
+++ b/kstars/kstars.kcfg
< at >< at > -1130,4 +1130,17 < at >< at >
       <whatsthis>List of selected satellites.</whatsthis>
     </entry>
   </group>
+  <group name="General">
+    <entry name="DefaultDSSImageSize" type="Double">
+      <label>Default size for DSS images</label>
+      <whatsthis>The default size for DSS images downloaded from the internet.</whatsthis>
+      <default>15.0</default>
+    </entry>
+    <entry name="DSSPadding" type="Double">
+      <label>Additional padding around DSS Images of deep-sky objects</label>
+      <whatsthis>To include parts of the star field, we add some extra padding around DSS images of deep-sky objects. This option configures the total (both sides) padding added to either dimension of the field.</whatsthis>
+      <default>10.0</default>
+    </entry>
+  </group>
+
 </kcfg>
diff --git a/kstars/ksutils.cpp b/kstars/ksutils.cpp
index 631d9dd..b39edf9 100644
--- a/kstars/ksutils.cpp
+++ b/kstars/ksutils.cpp
< at >< at > -19,6 +19,7 < at >< at >
 
 #include "deepskyobject.h"
 #include "skyobject.h"
+#include "Options.h"
 
 #include <QFile>
 
< at >< at > -41,8 +42,8 < at >< at > QString KSUtils::getDSSURL( const SkyPoint * const p ) {
         dms ra(0.0), dec(0.0);
         double height, width;
 
-        const double dss_default_size = 15.0; // TODO: Make this user-configurable
-        const double dss_padding = 10.0; // TODO: Make this user-configurable
+        double dss_default_size = Options::defaultDSSImageSize();
+        double dss_padding = Options::dSSPadding();
 
         Q_ASSERT( p );
         Q_ASSERT( dss_default_size > 0.0 && dss_padding >= 0.0 );
< at >< at > -93,7 +94,7 < at >< at > QString KSUtils::getDSSURL( const SkyPoint * const p ) {
 QString KSUtils::getDSSURL( const dms &ra, const dms &dec, float width, float height ) {
     const QString URLprefix( "http://archive.stsci.edu/cgi-bin/dss_search?v=1" );
     const QString URLsuffix( "&e=J2000&f=gif&c=none&fov=NONE" );
-    const double dss_default_size = 15.0; // Duplicate. TODO: Make this user-configurable
+    const double dss_default_size = Options::defaultDSSImageSize();
 
     char decsgn = ( dec.Degrees() < 0.0 ) ? '-' : '+';
     int dd = abs( dec.degree() );
diff --git a/kstars/options/opsadvanced.ui b/kstars/options/opsadvanced.ui
index 2b236c6..edf504b 100644
--- a/kstars/options/opsadvanced.ui
+++ b/kstars/options/opsadvanced.ui
< at >< at > -20,8 +20,159 < at >< at >
    <item>
     <widget class="QTabWidget" name="AdvancedOptionsTabWidget">
      <property name="currentIndex">
-      <number>2</number>
+      <number>0</number>
      </property>
+     <widget class="QWidget" name="tab">
+      <attribute name="title">
+       <string>&amp;General</string>
+      </attribute>
+      <layout class="QVBoxLayout" name="verticalLayout">
+       <item>
+        <widget class="QGroupBox" name="BackendsGroupBox">
+         <property name="title">
+          <string>Backends</string>
+         </property>
+         <layout class="QVBoxLayout" name="verticalLayout_4">
+          <item>
+           <widget class="QCheckBox" name="kcfg_UseRefraction">
+            <property name="toolTip">
+             <string>Correct coordinates of objects for the effects of the atmosphere</string>
+            </property>
+            <property name="whatsThis">
+             <string>The atmosphere bends light passing through it, like a lens.  If this item is checked, this &quot;atmospheric refraction&quot; will be simulated in the sky map.  Note that this correction is only applied when using the Horizontal coordinate system.</string>
+            </property>
+            <property name="text">
+             <string>Correct for atmospheric refraction</string>
+            </property>
+           </widget>
+          </item>
+          <item>
+           <widget class="QCheckBox" name="kcfg_UseRelativistic">
+            <property name="toolTip">
+             <string>Correct for the effect of sun's gravity on star positions, as predicted by General Relativity, and verified by Eddington's experiment.</string>
+            </property>
+            <property name="text">
+             <string>General Relativity effects near the sun</string>
+            </property>
+           </widget>
+          </item>
+         </layout>
+        </widget>
+       </item>
+       <item>
+        <widget class="QGroupBox" name="ImageryGroupBox">
+         <property name="title">
+          <string>DSS Imagery</string>
+         </property>
+         <layout class="QGridLayout" name="gridLayout">
+          <item row="0" column="0">
+           <widget class="QLabel" name="label">
+            <property name="text">
+             <string>Default DSS Image Size: </string>
+            </property>
+           </widget>
+          </item>
+          <item row="0" column="1">
+           <widget class="QDoubleSpinBox" name="kcfg_DefaultDSSImageSize">
+            <property name="sizePolicy">
+             <sizepolicy hsizetype="Minimum" vsizetype="Fixed">
+              <horstretch>0</horstretch>
+              <verstretch>0</verstretch>
+             </sizepolicy>
+            </property>
+            <property name="minimumSize">
+             <size>
+              <width>75</width>
+              <height>0</height>
+             </size>
+            </property>
+            <property name="decimals">
+             <number>1</number>
+            </property>
+            <property name="minimum">
+             <double>1.000000000000000</double>
+            </property>
+            <property name="maximum">
+             <double>75.000000000000000</double>
+            </property>
+            <property name="value">
+             <double>15.000000000000000</double>
+            </property>
+           </widget>
+          </item>
+          <item row="0" column="3">
+           <widget class="QLabel" name="DefaultDSSImageSizeUnitLabel">
+            <property name="sizePolicy">
+             <sizepolicy hsizetype="Expanding" vsizetype="Preferred">
+              <horstretch>0</horstretch>
+              <verstretch>0</verstretch>
+             </sizepolicy>
+            </property>
+            <property name="text">
+             <string>arcminutes</string>
+            </property>
+           </widget>
+          </item>
+          <item row="1" column="0">
+           <widget class="QLabel" name="label_3">
+            <property name="text">
+             <string>Padding around Deep Sky Objects:</string>
+            </property>
+           </widget>
+          </item>
+          <item row="1" column="1">
+           <widget class="QDoubleSpinBox" name="kcfg_DSSPadding">
+            <property name="minimumSize">
+             <size>
+              <width>75</width>
+              <height>0</height>
+             </size>
+            </property>
+            <property name="decimals">
+             <number>1</number>
+            </property>
+            <property name="minimum">
+             <double>1.000000000000000</double>
+            </property>
+            <property name="maximum">
+             <double>75.000000000000000</double>
+            </property>
+            <property name="value">
+             <double>10.000000000000000</double>
+            </property>
+           </widget>
+          </item>
+          <item row="1" column="2" colspan="2">
+           <widget class="QLabel" name="DSSPaddingUnitLabel">
+            <property name="sizePolicy">
+             <sizepolicy hsizetype="Expanding" vsizetype="Preferred">
+              <horstretch>0</horstretch>
+              <verstretch>0</verstretch>
+             </sizepolicy>
+            </property>
+            <property name="text">
+             <string>arcminutes</string>
+            </property>
+           </widget>
+          </item>
+         </layout>
+        </widget>
+       </item>
+       <item>
+        <spacer name="GeneralTabSpacer">
+         <property name="orientation">
+          <enum>Qt::Vertical</enum>
+         </property>
+         <property name="sizeHint" stdset="0">
+          <size>
+           <width>20</width>
+           <height>40</height>
+          </size>
+         </property>
+        </spacer>
+       </item>
+      </layout>
+     </widget>
      <widget class="QWidget" name="tab_3">
       <attribute name="title">
        <string>Look and &amp;Feel</string>
< at >< at > -350,52 +501,6 < at >< at >
         </spacer>
        </item>
       </layout>
-      <zorder>textLabelHideTimeStep</zorder>
-      <zorder>verticalLayoutWidget_3</zorder>
-      <zorder>verticalLayoutWidget_2</zorder>
-     </widget>
-     <widget class="QWidget" name="tab">
-      <attribute name="title">
-       <string>&amp;Backends</string>
-      </attribute>
-      <layout class="QVBoxLayout" name="verticalLayout">
-       <item>
-        <widget class="QCheckBox" name="kcfg_UseRefraction">
-         <property name="toolTip">
-          <string>Correct coordinates of objects for the effects of the atmosphere</string>
-         </property>
-         <property name="whatsThis">
-          <string>The atmosphere bends light passing through it, like a lens.  If this item is checked, this &quot;atmospheric refraction&quot; will be simulated in the sky map.  Note that this correction is only applied when using the Horizontal coordinate system.</string>
-         </property>
-         <property name="text">
-          <string>Correct for atmospheric refraction</string>
-         </property>
-        </widget>
-       </item>
-       <item>
-        <widget class="QCheckBox" name="kcfg_UseRelativistic">
-         <property name="toolTip">
-          <string>Correct for the effect of sun's gravity on star positions, as predicted by General Relativity, and verified by Eddington's experiment.</string>
-         </property>
-         <property name="text">
-          <string>General Relativity effects near the sun</string>
-         </property>
-        </widget>
-       </item>
-       <item>
-        <spacer name="verticalSpacer_3">
-         <property name="orientation">
-          <enum>Qt::Vertical</enum>
-         </property>
-         <property name="sizeHint" stdset="0">
-          <size>
-           <width>20</width>
-           <height>537</height>
-          </size>
-         </property>
-        </spacer>
-       </item>
-      </layout>
      </widget>
      <widget class="QWidget" name="tab_2">
       <attribute name="title">
diff --git a/kstars/tools/observinglist.cpp b/kstars/tools/observinglist.cpp
index 25ff29a..1a76a2f 100644
--- a/kstars/tools/observinglist.cpp
+++ b/kstars/tools/observinglist.cpp
< at >< at > -1192,7 +1192,7 < at >< at > bool ObservingList::eventFilter( QObject *obj, QEvent *event ) {
     if( obj == ui->ImagePreview ) {
         if( event->type() == QEvent::MouseButtonRelease ) {
             if( currentObject() ) {
-                if( ( ( QFile( CurrentImagePath ).size() < 13000 ) && (  QFile( CurrentTempPath ).size() < 13000 ) ) ) {
+                if( ( ( QFile( CurrentImagePath ).size() < 13000 ) && (  QFile( CurrentTempPath ).size() < 13000 ) ) ) { // FIXME: This size estimate is unreliable.
                     if( ! currentObject()->isSolarSystem() )
                         slotGetImage( Options::obsListPreferDSS() );
                     else

[kstars] kstars: Lots of changes that were tightlycoupled:

Akarsh Simha — 2012-04-14T11:55:34

Git commit c1f1f8e133248d319d6523c9c6ea6dd5156aa3ad by Akarsh Simha.
Committed on 14/04/2012 at 13:50.
Pushed by asimha into branch 'master'.

Lots of changes that were tightly coupled:

1. Reorganize options related to Observing List in kstars.kcfg under a
   new group.

2. Revamp the design of the "Advanced" options section to introduce a
   Tab Widget [I need feedback on this decision]. This is so that we
   can put all the advanced options in there without any clutter. [Q:
   Does observing list belong there?]

3. Remove the hackish DSS vs. SDSS preference option in the Observing
   List view and introduce the setting in the Advanced options under
   Observing List.

CCMAIL: kstars-devel< at >kde.org

M  +27   -16   kstars/kstars.kcfg
M  +502  -469  kstars/options/opsadvanced.ui
M  +2    -2    kstars/tools/observinglist.cpp
M  +0    -7    kstars/tools/observinglist.ui

http://commits.kde.org/kstars/c1f1f8e133248d319d6523c9c6ea6dd5156aa3ad

diff --git a/kstars/kstars.kcfg b/kstars/kstars.kcfg
index b8c8714..8724478 100644
--- a/kstars/kstars.kcfg
+++ b/kstars/kstars.kcfg
< at >< at > -603,21 +603,6 < at >< at >
 <whatsthis>Toggle whether the object under the mouse cursor gets a transient name label.</whatsthis>
 <default>true</default>
 </entry>
-<entry name="ObsListSymbol" type="Bool">
-<label>Use symbols to label observing list objects</label>
-<whatsthis>Objects in the observing list will be highlighted with a symbol in the map.</whatsthis>
-<default>true</default>
-</entry>
-<entry name="ObsListText" type="Bool">
-<label>Use text to label observing list objects</label>
-<whatsthis>Objects in the observing list will be highlighted with a colored name label in the map.</whatsthis>
-<default>false</default>
-</entry>
-        <entry name="ObsListSaveImage" type="Bool">
-            <label>Save the DSS/SDSS images to disk</label>
-            <whatisthis>The images of objects in the obseving list will be autosaved if you download them</whatisthis>
-            <default>false</default>
-        </entry>
 <entry name="UseRefraction" type="Bool">
 <label>Correct positions for atmospheric refraction?</label>
 <whatsthis>Toggle whether object positions are corrected for the effects of atmospheric refraction (only applies when horizontal coordinates are used).</whatsthis>
< at >< at > -715,7 +700,33 < at >< at >
             <default>true</default>
         </entry>
 </group>
-
+<group name="ObservingList">
+  <entry name="ObsListSymbol" type="Bool">
+<label>Use symbols to label observing list objects</label>
+<whatsthis>Objects in the observing list will be highlighted with a symbol in the map.</whatsthis>
+<default>true</default>
+</entry>
+<entry name="ObsListText" type="Bool">
+<label>Use text to label observing list objects</label>
+<whatsthis>Objects in the observing list will be highlighted with a colored name label in the map.</whatsthis>
+<default>false</default>
+</entry>
+        <entry name="ObsListSaveImage" type="Bool">
+            <label>Save the DSS/SDSS images to disk</label>
+            <whatisthis>The images of objects in the obseving list will be autosaved if you download them</whatisthis>
+            <default>false</default>
+        </entry>
+<entry name="ObsListPreferDSS" type="Bool">
+  <label>Prefer Digitized Sky Survey imagery in the observing list</label>
+<whatsthis>The observing list will prefer DSS imagery while downloading imagery.</whatsthis>
+<default>true</default>
+</entry>
+<entry name="ObsListPreferSDSS" type="Bool">
+<label>Prefer Sloan Digital Sky Survey imagery in the observing list</label>
+<whatsthis>The observing list will prefer SDSS imagery while downloading imagery.</whatsthis>
+<default>false</default>
+</entry>
+      </group>
 <group name="Colors">
 <entry name="ColorSchemeFile" type="String">
     <label>The name of the color scheme</label>
diff --git a/kstars/options/opsadvanced.ui b/kstars/options/opsadvanced.ui
index 9321edd..2b236c6 100644
--- a/kstars/options/opsadvanced.ui
+++ b/kstars/options/opsadvanced.ui
< at >< at > -1,485 +1,522 < at >< at >
-<ui version="4.0" >
+<?xml version="1.0" encoding="UTF-8"?>
+<ui version="4.0">
  <class>OpsAdvanced</class>
- <widget class="QWidget" name="OpsAdvanced" >
-  <property name="geometry" >
+ <widget class="QWidget" name="OpsAdvanced">
+  <property name="geometry">
    <rect>
     <x>0</x>
     <y>0</y>
-    <width>484</width>
-    <height>582</height>
+    <width>583</width>
+    <height>636</height>
    </rect>
   </property>
-  <layout class="QVBoxLayout" >
-   <property name="spacing" >
+  <layout class="QVBoxLayout">
+   <property name="spacing">
     <number>6</number>
    </property>
-   <property name="leftMargin" >
+   <property name="margin">
     <number>8</number>
    </property>
-   <property name="topMargin" >
-    <number>8</number>
-   </property>
-   <property name="rightMargin" >
-    <number>8</number>
-   </property>
-   <property name="bottomMargin" >
-    <number>8</number>
-   </property>
-   <item>
-    <widget class="QCheckBox" name="kcfg_UseRefraction" >
-     <property name="toolTip" >
-      <string>Correct coordinates of objects for the effects of the atmosphere</string>
-     </property>
-     <property name="whatsThis" >
-      <string>The atmosphere bends light passing through it, like a lens.  If this item is checked, this "atmospheric refraction" will be simulated in the sky map.  Note that this correction is only applied when using the Horizontal coordinate system.</string>
-     </property>
-     <property name="text" >
-      <string>Correct for atmospheric refraction</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QCheckBox" name="kcfg_UseRelativistic" >
-     <property name="toolTip" >
-      <string>Correct for the effect of sun's gravity on star positions, as predicted by General Relativity, and verified by Eddington's experiment.</string>
-     </property>
-     <property name="text" >
-      <string>General Relativity effects near the sun</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QCheckBox" name="kcfg_UseAnimatedSlewing" >
-     <property name="toolTip" >
-      <string>Show slewing motion when focus changes?</string>
-     </property>
-     <property name="whatsThis" >
-      <string>If checked, changing the focus position will result in a visible animated "slew" to the new position.  Otherwise, the display will center on the new position instantaneously.</string>
-     </property>
-     <property name="text" >
-      <string>Use animated slewing</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QCheckBox" name="kcfg_UseAutoLabel" >
-     <property name="toolTip" >
-      <string>Show name label of centered object?</string>
-     </property>
-     <property name="whatsThis" >
-      <string>If checked, a name label will be temporarily attached to an object while it is centered in the display.  You can attach a more persistent label to any object using the right-click popup menu.</string>
-     </property>
-     <property name="text" >
-      <string>Attach label to centered object</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QCheckBox" name="kcfg_UseHoverLabel" >
-     <property name="toolTip" >
-      <string>Show name label of centered object?</string>
-     </property>
-     <property name="whatsThis" >
-      <string>If checked, a name label will be temporarily attached to an object while it is centered in the display.  You can attach a more persistent label to any object using the right-click popup menu.</string>
-     </property>
-     <property name="text" >
-      <string>Attach temporary label when hovering mouse</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QCheckBox" name="kcfg_UseAntialias" >
-     <property name="toolTip" >
-      <string>Select this for smoother (but slower) graphics</string>
-     </property>
-     <property name="text" >
-      <string>Use antialiased drawing</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QGroupBox" name="ObsListOptions" >
-     <property name="title" >
-      <string>Observing List Labels</string>
-     </property>
-     <layout class="QHBoxLayout" >
-      <property name="spacing" >
-       <number>6</number>
-      </property>
-      <property name="leftMargin" >
-       <number>8</number>
-      </property>
-      <property name="topMargin" >
-       <number>8</number>
-      </property>
-      <property name="rightMargin" >
-       <number>8</number>
-      </property>
-      <property name="bottomMargin" >
-       <number>8</number>
-      </property>
-      <item>
-       <widget class="QRadioButton" name="kcfg_ObsListSymbol" >
-        <property name="text" >
-         <string>Symbol</string>
-        </property>
-        <property name="checked" >
-         <bool>true</bool>
-        </property>
-       </widget>
-      </item>
-      <item>
-       <widget class="QRadioButton" name="kcfg_ObsListText" >
-        <property name="text" >
-         <string>Text</string>
-        </property>
-       </widget>
-      </item>
-     </layout>
-    </widget>
-   </item>
-   <item>
-    <spacer>
-     <property name="orientation" >
-      <enum>Qt::Vertical</enum>
-     </property>
-     <property name="sizeType" >
-      <enum>QSizePolicy::Fixed</enum>
-     </property>
-     <property name="sizeHint" >
-      <size>
-       <width>20</width>
-       <height>20</height>
-      </size>
-     </property>
-    </spacer>
-   </item>
-   <item>
-     <widget class="QCheckBox" name="kcfg_ObsListSaveImage" >
-     <property name="toolTip" >
-      <string>Save the downloaded DSS/SDSS images?</string>
-     </property>
-     <property name="whatsThis" >
-      <string>Do you want the downloaded DSS/SDSS images to be saved when closing the observing list?</string>
-     </property>
-     <property name="text" >
-      <string>Save downloaded images on exit</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <widget class="QCheckBox" name="kcfg_HideOnSlew" >
-     <property name="toolTip" >
-      <string>Do not draw all objects while the map is moving?</string>
-     </property>
-     <property name="whatsThis" >
-      <string>When the map is in motion, smooth animation is compromised if the program has too many objects to draw on the map; check this item to temporarily hide some of the objects while the display is in motion.</string>
-     </property>
-     <property name="text" >
-      <string>Hide objects while moving</string>
-     </property>
-    </widget>
-   </item>
-   <item>
-    <layout class="QHBoxLayout" >
-     <property name="spacing" >
-      <number>6</number>
-     </property>
-     <property name="leftMargin" >
-      <number>0</number>
-     </property>
-     <property name="topMargin" >
-      <number>0</number>
-     </property>
-     <property name="rightMargin" >
-      <number>0</number>
-     </property>
-     <property name="bottomMargin" >
-      <number>0</number>
-     </property>
-     <item>
-      <widget class="QLabel" name="textLabelHideTimeStep" >
-       <property name="text" >
-        <string>Also hide if time step larger than:</string>
-       </property>
-      </widget>
-     </item>
-     <item>
-      <widget class="TimeStepBox" name="SlewTimeScale" />
-     </item>
-     <item>
-      <spacer>
-       <property name="orientation" >
-        <enum>Qt::Horizontal</enum>
-       </property>
-       <property name="sizeType" >
-        <enum>QSizePolicy::Expanding</enum>
-       </property>
-       <property name="sizeHint" >
-        <size>
-         <width>111</width>
-         <height>20</height>
-        </size>
-       </property>
-      </spacer>
-     </item>
-    </layout>
-   </item>
    <item>
-    <widget class="QGroupBox" name="HideBox" >
-     <property name="title" >
-      <string>Configure Hidden Objects</string>
-     </property>
-     <layout class="QVBoxLayout" >
-      <property name="spacing" >
-       <number>6</number>
-      </property>
-      <property name="leftMargin" >
-       <number>8</number>
-      </property>
-      <property name="topMargin" >
-       <number>8</number>
-      </property>
-      <property name="rightMargin" >
-       <number>8</number>
-      </property>
-      <property name="bottomMargin" >
-       <number>8</number>
-      </property>
-      <item>
-       <layout class="QHBoxLayout" >
-        <property name="spacing" >
-         <number>6</number>
-        </property>
-        <property name="leftMargin" >
-         <number>0</number>
-        </property>
-        <property name="topMargin" >
-         <number>0</number>
-        </property>
-        <property name="rightMargin" >
-         <number>0</number>
-        </property>
-        <property name="bottomMargin" >
-         <number>0</number>
-        </property>
-        <item>
-         <widget class="QCheckBox" name="kcfg_HideStars" >
-          <property name="toolTip" >
-           <string>Hide faint stars while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then fainter stars will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Stars fainter than</string>
-          </property>
-         </widget>
-        </item>
-        <item>
-         <widget class="MagnitudeSpinBox" name="kcfg_MagLimitHideStar" >
-          <property name="minimumSize" >
-           <size>
-            <width>40</width>
-            <height>0</height>
-           </size>
-          </property>
-          <property name="focusPolicy" >
-           <enum>Qt::StrongFocus</enum>
-          </property>
-          <property name="whatsThis" >
-           <string>Stars fainter than this will not be drawn while the map is moving.</string>
-          </property>
-         </widget>
-        </item>
-        <item>
-         <widget class="QLabel" name="textLabelMag1" >
-          <property name="text" >
-           <string>mag</string>
-          </property>
-         </widget>
-        </item>
-        <item>
-         <spacer>
-          <property name="orientation" >
-           <enum>Qt::Horizontal</enum>
-          </property>
-          <property name="sizeType" >
-           <enum>QSizePolicy::Expanding</enum>
-          </property>
-          <property name="sizeHint" >
-           <size>
-            <width>240</width>
-            <height>20</height>
-           </size>
-          </property>
-         </spacer>
-        </item>
-       </layout>
-      </item>
-      <item>
-       <layout class="QGridLayout" >
-        <property name="leftMargin" >
-         <number>0</number>
-        </property>
-        <property name="topMargin" >
-         <number>0</number>
-        </property>
-        <property name="rightMargin" >
-         <number>0</number>
-        </property>
-        <property name="bottomMargin" >
-         <number>0</number>
-        </property>
-        <property name="horizontalSpacing" >
-         <number>6</number>
-        </property>
-        <property name="verticalSpacing" >
-         <number>6</number>
-        </property>
-        <item rowspan="2" row="4" column="0" >
-         <widget class="QCheckBox" name="kcfg_HideIC" >
-          <property name="toolTip" >
-           <string>Hide IC objects while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then objects in the IC catalog will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>IC objects</string>
-          </property>
-         </widget>
-        </item>
-        <item row="0" column="1" >
-         <widget class="QCheckBox" name="kcfg_HideMilkyWay" >
-          <property name="toolTip" >
-           <string>Hide the Milky Way contour while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then the Milky Way contour will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Milky Way</string>
-          </property>
-         </widget>
-        </item>
-        <item row="0" column="0" >
-         <widget class="QCheckBox" name="kcfg_HidePlanets" >
-          <property name="toolTip" >
-           <string>Hide solar system bodies while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then all solar system bodies will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Solar system</string>
-          </property>
-         </widget>
-        </item>
-        <item row="5" column="1" >
-         <widget class="QCheckBox" name="kcfg_HideCBounds" >
-          <property name="text" >
-           <string>Constellation boundaries</string>
-          </property>
-         </widget>
-        </item>
-        <item row="1" column="0" >
-         <widget class="QCheckBox" name="kcfg_HideMessier" >
-          <property name="toolTip" >
-           <string>Hide Messier objects when moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then objects in the Messier catalog will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Messier objects</string>
-          </property>
-         </widget>
-        </item>
-        <item row="6" column="1" >
-         <widget class="QCheckBox" name="kcfg_HideGrids" >
-          <property name="toolTip" >
-           <string>Hide coordinate grids while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then the coordinate grids will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Coordinate grids</string>
-          </property>
-         </widget>
-        </item>
-        <item rowspan="2" row="2" column="0" >
-         <widget class="QCheckBox" name="kcfg_HideNGC" >
-          <property name="toolTip" >
-           <string>Hide NGC objects while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then objects in the NGC catalog will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>NGC objects</string>
-          </property>
-         </widget>
-        </item>
-        <item rowspan="2" row="3" column="1" >
-         <widget class="QCheckBox" name="kcfg_HideCLines" >
-          <property name="toolTip" >
-           <string>Hide constellation lines while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then constellation lines will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Constellation lines</string>
-          </property>
-         </widget>
-        </item>
-        <item rowspan="2" row="1" column="1" >
-         <widget class="QCheckBox" name="kcfg_HideCNames" >
-          <property name="toolTip" >
-           <string>Hide constellation names while moving?</string>
-          </property>
-          <property name="whatsThis" >
-           <string>If checked, then constellation names will be hidden when the map is in motion.</string>
-          </property>
-          <property name="text" >
-           <string>Constellation names</string>
-          </property>
-         </widget>
-        </item>
-        <item row="6" column="0" >
-         <widget class="QCheckBox" name="kcfg_HideLabels" >
-          <property name="text" >
-           <string>Object labels</string>
-          </property>
-         </widget>
-        </item>
-       </layout>
-      </item>
-     </layout>
+    <widget class="QTabWidget" name="AdvancedOptionsTabWidget">
+     <property name="currentIndex">
+      <number>2</number>
+     </property>
+     <widget class="QWidget" name="tab_3">
+      <attribute name="title">
+       <string>Look and &amp;Feel</string>
+      </attribute>
+      <layout class="QVBoxLayout" name="verticalLayout_3">
+       <item>
+        <widget class="QCheckBox" name="kcfg_UseAnimatedSlewing">
+         <property name="toolTip">
+          <string>Show slewing motion when focus changes?</string>
+         </property>
+         <property name="whatsThis">
+          <string>If checked, changing the focus position will result in a visible animated &quot;slew&quot; to the new position.  Otherwise, the display will center on the new position instantaneously.</string>
+         </property>
+         <property name="text">
+          <string>Use animated slewing</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <widget class="QCheckBox" name="kcfg_UseAutoLabel">
+         <property name="toolTip">
+          <string>Show name label of centered object?</string>
+         </property>
+         <property name="whatsThis">
+          <string>If checked, a name label will be temporarily attached to an object while it is centered in the display.  You can attach a more persistent label to any object using the right-click popup menu.</string>
+         </property>
+         <property name="text">
+          <string>Attach label to centered object</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <widget class="QCheckBox" name="kcfg_UseHoverLabel">
+         <property name="toolTip">
+          <string>Show name label of centered object?</string>
+         </property>
+         <property name="whatsThis">
+          <string>If checked, a name label will be temporarily attached to an object while it is centered in the display.  You can attach a more persistent label to any object using the right-click popup menu.</string>
+         </property>
+         <property name="text">
+          <string>Attach temporary label when hovering mouse</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <widget class="QCheckBox" name="kcfg_UseAntialias">
+         <property name="toolTip">
+          <string>Select this for smoother (but slower) graphics</string>
+         </property>
+         <property name="text">
+          <string>Use antialiased drawing</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <widget class="QCheckBox" name="kcfg_HideOnSlew">
+         <property name="toolTip">
+          <string>Do not draw all objects while the map is moving?</string>
+         </property>
+         <property name="whatsThis">
+          <string>When the map is in motion, smooth animation is compromised if the program has too many objects to draw on the map; check this item to temporarily hide some of the objects while the display is in motion.</string>
+         </property>
+         <property name="text">
+          <string>Hide objects while moving</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <layout class="QHBoxLayout">
+         <property name="spacing">
+          <number>6</number>
+         </property>
+         <property name="margin">
+          <number>0</number>
+         </property>
+         <item>
+          <widget class="QLabel" name="textLabelHideTimeStep">
+           <property name="text">
+            <string>Also hide if time step larger than:</string>
+           </property>
+          </widget>
+         </item>
+         <item>
+          <widget class="TimeStepBox" name="SlewTimeScale"/>
+         </item>
+         <item>
+          <spacer>
+           <property name="orientation">
+            <enum>Qt::Horizontal</enum>
+           </property>
+           <property name="sizeType">
+            <enum>QSizePolicy::Expanding</enum>
+           </property>
+           <property name="sizeHint" stdset="0">
+            <size>
+             <width>111</width>
+             <height>20</height>
+            </size>
+           </property>
+          </spacer>
+         </item>
+        </layout>
+       </item>
+       <item>
+        <widget class="QGroupBox" name="HideBox">
+         <property name="sizePolicy">
+          <sizepolicy hsizetype="Expanding" vsizetype="Preferred">
+           <horstretch>0</horstretch>
+           <verstretch>0</verstretch>
+          </sizepolicy>
+         </property>
+         <property name="title">
+          <string>Configure Hidden Objects</string>
+         </property>
+         <layout class="QVBoxLayout">
+          <property name="spacing">
+           <number>6</number>
+          </property>
+          <property name="margin">
+           <number>8</number>
+          </property>
+          <item>
+           <layout class="QHBoxLayout">
+            <property name="spacing">
+             <number>6</number>
+            </property>
+            <property name="margin">
+             <number>0</number>
+            </property>
+            <item>
+             <widget class="QCheckBox" name="kcfg_HideStars">
+              <property name="toolTip">
+               <string>Hide faint stars while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then fainter stars will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Stars fainter than</string>
+              </property>
+             </widget>
+            </item>
+            <item>
+             <widget class="MagnitudeSpinBox" name="kcfg_MagLimitHideStar">
+              <property name="minimumSize">
+               <size>
+                <width>40</width>
+                <height>0</height>
+               </size>
+              </property>
+              <property name="focusPolicy">
+               <enum>Qt::StrongFocus</enum>
+              </property>
+              <property name="whatsThis">
+               <string>Stars fainter than this will not be drawn while the map is moving.</string>
+              </property>
+             </widget>
+            </item>
+            <item>
+             <widget class="QLabel" name="textLabelMag1">
+              <property name="text">
+               <string>mag</string>
+              </property>
+             </widget>
+            </item>
+            <item>
+             <spacer>
+              <property name="orientation">
+               <enum>Qt::Horizontal</enum>
+              </property>
+              <property name="sizeType">
+               <enum>QSizePolicy::Expanding</enum>
+              </property>
+              <property name="sizeHint" stdset="0">
+               <size>
+                <width>240</width>
+                <height>20</height>
+               </size>
+              </property>
+             </spacer>
+            </item>
+           </layout>
+          </item>
+          <item>
+           <layout class="QGridLayout">
+            <property name="margin">
+             <number>0</number>
+            </property>
+            <property name="spacing">
+             <number>6</number>
+            </property>
+            <item row="4" column="0" rowspan="2">
+             <widget class="QCheckBox" name="kcfg_HideIC">
+              <property name="toolTip">
+               <string>Hide IC objects while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then objects in the IC catalog will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>IC objects</string>
+              </property>
+             </widget>
+            </item>
+            <item row="0" column="1">
+             <widget class="QCheckBox" name="kcfg_HideMilkyWay">
+              <property name="toolTip">
+               <string>Hide the Milky Way contour while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then the Milky Way contour will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Milky Way</string>
+              </property>
+             </widget>
+            </item>
+            <item row="0" column="0">
+             <widget class="QCheckBox" name="kcfg_HidePlanets">
+              <property name="toolTip">
+               <string>Hide solar system bodies while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then all solar system bodies will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Solar system</string>
+              </property>
+             </widget>
+            </item>
+            <item row="5" column="1">
+             <widget class="QCheckBox" name="kcfg_HideCBounds">
+              <property name="text">
+               <string>Constellation boundaries</string>
+              </property>
+             </widget>
+            </item>
+            <item row="1" column="0">
+             <widget class="QCheckBox" name="kcfg_HideMessier">
+              <property name="toolTip">
+               <string>Hide Messier objects when moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then objects in the Messier catalog will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Messier objects</string>
+              </property>
+             </widget>
+            </item>
+            <item row="6" column="1">
+             <widget class="QCheckBox" name="kcfg_HideGrids">
+              <property name="toolTip">
+               <string>Hide coordinate grids while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then the coordinate grids will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Coordinate grids</string>
+              </property>
+             </widget>
+            </item>
+            <item row="2" column="0" rowspan="2">
+             <widget class="QCheckBox" name="kcfg_HideNGC">
+              <property name="toolTip">
+               <string>Hide NGC objects while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then objects in the NGC catalog will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>NGC objects</string>
+              </property>
+             </widget>
+            </item>
+            <item row="3" column="1" rowspan="2">
+             <widget class="QCheckBox" name="kcfg_HideCLines">
+              <property name="toolTip">
+               <string>Hide constellation lines while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then constellation lines will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Constellation lines</string>
+              </property>
+             </widget>
+            </item>
+            <item row="1" column="1" rowspan="2">
+             <widget class="QCheckBox" name="kcfg_HideCNames">
+              <property name="toolTip">
+               <string>Hide constellation names while moving?</string>
+              </property>
+              <property name="whatsThis">
+               <string>If checked, then constellation names will be hidden when the map is in motion.</string>
+              </property>
+              <property name="text">
+               <string>Constellation names</string>
+              </property>
+             </widget>
+            </item>
+            <item row="6" column="0">
+             <widget class="QCheckBox" name="kcfg_HideLabels">
+              <property name="text">
+               <string>Object labels</string>
+              </property>
+             </widget>
+            </item>
+           </layout>
+          </item>
+         </layout>
+        </widget>
+       </item>
+       <item>
+        <spacer name="verticalSpacer">
+         <property name="orientation">
+          <enum>Qt::Vertical</enum>
+         </property>
+         <property name="sizeHint" stdset="0">
+          <size>
+           <width>20</width>
+           <height>211</height>
+          </size>
+         </property>
+        </spacer>
+       </item>
+      </layout>
+      <zorder>textLabelHideTimeStep</zorder>
+      <zorder>verticalLayoutWidget_3</zorder>
+      <zorder>verticalLayoutWidget_2</zorder>
+     </widget>
+     <widget class="QWidget" name="tab">
+      <attribute name="title">
+       <string>&amp;Backends</string>
+      </attribute>
+      <layout class="QVBoxLayout" name="verticalLayout">
+       <item>
+        <widget class="QCheckBox" name="kcfg_UseRefraction">
+         <property name="toolTip">
+          <string>Correct coordinates of objects for the effects of the atmosphere</string>
+         </property>
+         <property name="whatsThis">
+          <string>The atmosphere bends light passing through it, like a lens.  If this item is checked, this &quot;atmospheric refraction&quot; will be simulated in the sky map.  Note that this correction is only applied when using the Horizontal coordinate system.</string>
+         </property>
+         <property name="text">
+          <string>Correct for atmospheric refraction</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <widget class="QCheckBox" name="kcfg_UseRelativistic">
+         <property name="toolTip">
+          <string>Correct for the effect of sun's gravity on star positions, as predicted by General Relativity, and verified by Eddington's experiment.</string>
+         </property>
+         <property name="text">
+          <string>General Relativity effects near the sun</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <spacer name="verticalSpacer_3">
+         <property name="orientation">
+          <enum>Qt::Vertical</enum>
+         </property>
+         <property name="sizeHint" stdset="0">
+          <size>
+           <width>20</width>
+           <height>537</height>
+          </size>
+         </property>
+        </spacer>
+       </item>
+      </layout>
+     </widget>
+     <widget class="QWidget" name="tab_2">
+      <attribute name="title">
+       <string>Observing &amp;List</string>
+      </attribute>
+      <layout class="QVBoxLayout" name="verticalLayout_2">
+       <item>
+        <widget class="QGroupBox" name="ObsListOptions">
+         <property name="sizePolicy">
+          <sizepolicy hsizetype="Expanding" vsizetype="Preferred">
+           <horstretch>0</horstretch>
+           <verstretch>0</verstretch>
+          </sizepolicy>
+         </property>
+         <property name="title">
+          <string>Observing List Labels</string>
+         </property>
+         <layout class="QHBoxLayout">
+          <property name="spacing">
+           <number>6</number>
+          </property>
+          <property name="margin">
+           <number>8</number>
+          </property>
+          <item>
+           <widget class="QRadioButton" name="kcfg_ObsListSymbol">
+            <property name="text">
+             <string>Symbol</string>
+            </property>
+            <property name="checked">
+             <bool>true</bool>
+            </property>
+           </widget>
+          </item>
+          <item>
+           <widget class="QRadioButton" name="kcfg_ObsListText">
+            <property name="text">
+             <string>Text</string>
+            </property>
+           </widget>
+          </item>
+         </layout>
+        </widget>
+       </item>
+       <item>
+        <widget class="QCheckBox" name="kcfg_ObsListSaveImage">
+         <property name="toolTip">
+          <string>Save the downloaded DSS/SDSS images?</string>
+         </property>
+         <property name="whatsThis">
+          <string>Do you want the downloaded DSS/SDSS images to be saved when closing the observing list?</string>
+         </property>
+         <property name="text">
+          <string>Save downloaded images on exit</string>
+         </property>
+        </widget>
+       </item>
+       <item>
+        <widget class="QGroupBox" name="ObsListImageryOptions">
+         <property name="sizePolicy">
+          <sizepolicy hsizetype="Expanding" vsizetype="Preferred">
+           <horstretch>0</horstretch>
+           <verstretch>0</verstretch>
+          </sizepolicy>
+         </property>
+         <property name="title">
+          <string>Preferred Imagery</string>
+         </property>
+         <layout class="QHBoxLayout" name="_3">
+          <property name="spacing">
+           <number>6</number>
+          </property>
+          <property name="margin">
+           <number>8</number>
+          </property>
+          <item>
+           <widget class="QRadioButton" name="kcfg_ObsListPreferDSS">
+            <property name="text">
+             <string>&amp;Digitized Sky Survey (DSS)</string>
+            </property>
+            <property name="checked">
+             <bool>true</bool>
+            </property>
+           </widget>
+          </item>
+          <item>
+           <widget class="QRadioButton" name="kcfg_ObsListPreferSDSS">
+            <property name="text">
+             <string>&amp;Sloan Digital Sky Survey (SDSS)</string>
+            </property>
+           </widget>
+          </item>
+         </layout>
+        </widget>
+       </item>
+       <item>
+        <spacer name="verticalSpacer_2">
+         <property name="orientation">
+          <enum>Qt::Vertical</enum>
+         </property>
+         <property name="sizeHint" stdset="0">
+          <size>
+           <width>20</width>
+           <height>417</height>
+          </size>
+         </property>
+        </spacer>
+       </item>
+      </layout>
+     </widget>
     </widget>
    </item>
-   <item>
-    <spacer>
-     <property name="orientation" >
-      <enum>Qt::Vertical</enum>
-     </property>
-     <property name="sizeType" >
-      <enum>QSizePolicy::Expanding</enum>
-     </property>
-     <property name="sizeHint" >
-      <size>
-       <width>468</width>
-       <height>16</height>
-      </size>
-     </property>
-    </spacer>
-   </item>
   </layout>
  </widget>
  <customwidgets>
   <customwidget>
+   <class>KDoubleNumInput</class>
+   <extends>QWidget</extends>
+   <header>knuminput.h</header>
+  </customwidget>
+  <customwidget>
    <class>MagnitudeSpinBox</class>
    <extends>KDoubleNumInput</extends>
    <header>widgets/magnitudespinbox.h</header>
< at >< at > -491,10 +528,6 < at >< at >
   </customwidget>
  </customwidgets>
  <tabstops>
-  <tabstop>kcfg_UseRefraction</tabstop>
-  <tabstop>kcfg_UseAnimatedSlewing</tabstop>
-  <tabstop>kcfg_UseAutoLabel</tabstop>
-  <tabstop>kcfg_HideOnSlew</tabstop>
   <tabstop>kcfg_HideStars</tabstop>
   <tabstop>kcfg_MagLimitHideStar</tabstop>
   <tabstop>kcfg_HidePlanets</tabstop>
diff --git a/kstars/tools/observinglist.cpp b/kstars/tools/observinglist.cpp
index 0dfa3cd..25ff29a 100644
--- a/kstars/tools/observinglist.cpp
+++ b/kstars/tools/observinglist.cpp
< at >< at > -1118,7 +1118,7 < at >< at > void ObservingList::slotSaveAllImages() {
     foreach( SkyObject *o, currList ) {
         setCurrentImage( o );
         QString img( CurrentImagePath  );
-        KUrl url( ( ui->preferDSS->isChecked() ) ? DSSUrl : SDSSUrl );
+        KUrl url( ( Options::obsListPreferDSS() ) ? DSSUrl : SDSSUrl );
         if( ! o->isSolarSystem() )//TODO find a way for adding support for solar system images
             saveImage( url, img );
     }
< at >< at > -1194,7 +1194,7 < at >< at > bool ObservingList::eventFilter( QObject *obj, QEvent *event ) {
             if( currentObject() ) {
                 if( ( ( QFile( CurrentImagePath ).size() < 13000 ) && (  QFile( CurrentTempPath ).size() < 13000 ) ) ) {
                     if( ! currentObject()->isSolarSystem() )
-                        slotGetImage( ui->preferDSS->isChecked() );
+                        slotGetImage( Options::obsListPreferDSS() );
                     else
                         slotGoogleImage();
                 }
diff --git a/kstars/tools/observinglist.ui b/kstars/tools/observinglist.ui
index f06421e..af749b3 100644
--- a/kstars/tools/observinglist.ui
+++ b/kstars/tools/observinglist.ui
< at >< at > -301,13 +301,6 < at >< at >
       </widget>
      </item>
      <item>
-      <widget class="QCheckBox" name="preferDSS">
-       <property name="text">
-        <string> Prefer DSS</string>
-       </property>
-      </widget>
-     </item>
-     <item>
       <spacer name="horizontalSpacer_2">
        <property name="orientation">
         <enum>Qt::Horizontal</enum>

GSoC slots

Akarsh Simha — 2012-04-11T06:23:39

Hi

I suppose all you students are on this mailing list. This is that part
of the timeline when the Google distributes its limited slots to open
source projects, and large open source projects distribute those even
more limited precious slots to various proposals in KDE. While
students owe their "allegiance" only to the project and their summer
job, mentors have to see the interest of both KDE and the open source
community at large, and the students at the same time. It's hard to be
completely fair to one party without doing some injustice to the
other. That's part of the reason I usually recommend that students
apply to multiple projects (despite that not being in the interest of
the organization), because you shouldn't lose out just because of
other factors.

Let us hope that all turns out well at the end of the day, but I'm
just writing this to prepare us all in advance and point out to you
that if we didn't pick you, it doesn't mean that you weren't good
enough to do a GSoC. It's just that there are too many factors
involved in picking a proposal -- not merit alone. I hope y'all will
understand this. We'll be happy to have all of you contribute to
KStars / KDE in general and I'm sure there will be a lot of people in
every KDE project willing to invest a whole lot of time in making you
a contributor, irrespective of whether you were given one of those
precious GSoC slots or not.

I feel bad for it even before any decision is taken by Google, even as
we build up our list of proposals ordered by desirability (which
usually amounts to many factors -- KDE's overall good, proposals'
merit, conflicting proposals, number of slots we can expect,
mentor-power that we have), which is why I felt I should send this
mail out. Please do not assume that our selection implies anything
about your abilities.

This year has been amongst the better ones in terms of good proposals.

Regards
Akarsh

Dead code removal

Aleksey Khudyakov — 2012-04-08T20:36:40

Hi!

I've just pushed commits which remove a bunch of dead code
from KStars. I've used callcatcher to find it[1].

If you think that some of the code should be kept despite being unused 
then revert relevant changeset.


[1] http://www.skynet.ie/~caolan/Packages/callcatcher.html

Re: Bug with inline image display

Rafal Kulaga — 2012-04-05T12:34:53

Hi Manfred!

Thanks for your report. I'll take a look at this.

Cheers,
Rafal



2012/3/31 Manfred G Kitzbichler <manfred.kitzbichler< at >gmail.com>: