From victor.carbune at gmail.com  Wed Dec  1 14:30:52 2010
From: victor.carbune at gmail.com (Victor Carbune)
Date: Wed,  1 Dec 2010 14:30:52 +0100 (CET)
Subject: [Kstars-devel]  branches/kstars/code-in/kstars/kstars
Message-ID: <20101201133052.99C34AC8A4@svn.kde.org>

SVN commit 1202586 by vcarbune:

Nice feature done by Valery Kharitonov as a Google Code-in task.

He added a generic widget KSHelpLabel which can be used to create help
label, that points to our AstroInfo documentation within KHelpCenter.

This way we connect astronomical terms (declination, right ascension etc.)
with all the documentation available within the AstroInfo project.

Thanks, Valery and hope to see you contributing again to our project!

CCMAIL: kstars-devel at kde.org, kharvd at gmail.com



 M  +1 -0      CMakeLists.txt  
 M  +1 -0      dialogs/detaildialog.cpp  
 M  +14 -2     dialogs/details_data.ui  
 M  +80 -46    dialogs/details_position.ui  


http://websvn.kde.org/?view=rev&revision=1202586

From victor.carbune at gmail.com  Wed Dec  1 14:34:41 2010
From: victor.carbune at gmail.com (Victor Carbune)
Date: Wed,  1 Dec 2010 14:34:41 +0100 (CET)
Subject: [Kstars-devel]  branches/kstars/code-in/kstars/kstars/widgets
Message-ID: <20101201133441.6374EAC8A3@svn.kde.org>

SVN commit 1202587 by vcarbune:

Fixed last commit: added the KSHelpLabel class.

CCMAIL: kstars-devel at kde.org, kharvd at gmail.com



 A             kshelplabel.cpp   [License: UNKNOWN]
 A             kshelplabel.h   [License: UNKNOWN]



From victor.carbune at gmail.com  Wed Dec  1 14:42:42 2010
From: victor.carbune at gmail.com (Victor Carbune)
Date: Wed,  1 Dec 2010 14:42:42 +0100 (CET)
Subject: [Kstars-devel]  branches/kstars/code-in/kstars/kstars/widgets
Message-ID: <20101201134242.4AE06AC8A3@svn.kde.org>

SVN commit 1202590 by vcarbune:

Added license information.
Hope there isn't anything else I forgot.

CCMAIL: kstars-devel at kde.org, kharvd at gmail.com


 M  +19 -1     kshelplabel.cpp  
 M  +17 -0     kshelplabel.h  


--- branches/kstars/code-in/kstars/kstars/widgets/kshelplabel.cpp #1202589:1202590
@@ -1,3 +1,20 @@
+/***************************************************************************
+            kshelplabel.cpp - Help label used to document astronomical terms
+                             -------------------
+    begin                : Wed 1 Dec 2010
+    copyright            : (C) 2010 by Valery Kharitonov
+    email                : kharvd at gmail.com
+ ***************************************************************************/
+
+/***************************************************************************
+ *                                                                         *
+ *   This program is free software; you can redistribute it and/or modify  *
+ *   it under the terms of the GNU General Public License as published by  *
+ *   the Free Software Foundation; either version 2 of the License, or     *
+ *   (at your option) any later version.                                   *
+ *                                                                         *
+ ***************************************************************************/
+
 #include "kshelplabel.h"
 #include <ktoolinvocation.h>
 #include <QtGui/QMessageBox>
@@ -31,4 +48,5 @@
 void KSHelpLabel::setText(const QString& txt) {
     m_cleanText = txt;
     QLabel::setText("<a href=\"ai-" + m_anchor + "\">" + m_cleanText + "</a>");
-}
\ No newline at end of file
+}
+
--- branches/kstars/code-in/kstars/kstars/widgets/kshelplabel.h #1202589:1202590
@@ -1,3 +1,20 @@
+/***************************************************************************
+            kshelplabel.h - Help label used to document astronomical terms
+                             -------------------
+    begin                : Wed 1 Dec 2010
+    copyright            : (C) 2010 by Valery Kharitonov
+    email                : kharvd at gmail.com
+ ***************************************************************************/
+
+/***************************************************************************
+ *                                                                         *
+ *   This program is free software; you can redistribute it and/or modify  *
+ *   it under the terms of the GNU General Public License as published by  *
+ *   the Free Software Foundation; either version 2 of the License, or     *
+ *   (at your option) any later version.                                   *
+ *                                                                         *
+ ***************************************************************************/
+
 #ifndef KSHELPLABEL_H
 #define KSHELPLABEL_H
 

From gorlin at telia.com  Fri Dec  3 14:57:39 2010
From: gorlin at telia.com (H-G Lindberg)
Date: Fri, 03 Dec 2010 14:57:39 +0100
Subject: [Kstars-devel]  Variable star
Message-ID: <4CF8F753.20208@telia.com>

I am new to KStar, just now try to download the USNO NOMAD Cat, but it 
seems to take hours, now it have run for 3 hours but nothing is happed, 
yes its a big file, but looks that the server is very slow?

I am a variable star observer is it any way to add the GCVS- cat and 
NSV-cat in to KStar?

The software looks great but need some variable stars.

Regards
h-g

From victor.carbune at gmail.com  Sun Dec  5 09:45:49 2010
From: victor.carbune at gmail.com (Victor Carbune)
Date: Sun,  5 Dec 2010 09:45:49 +0100 (CET)
Subject: [Kstars-devel]  KDE/kdeedu/kstars/kstars
Message-ID: <20101205084549.AAEE9AC8A4@svn.kde.org>

SVN commit 1203704 by vcarbune:

A second Google Code-in task by Valery Kharitonov: removes KDE/Qt 3 support libs
dependency from KStars and implicitly from KDE Edu. Yay!

No bugs, clean code, but would be great everyone to further test this change.

CCMAIL: kstars-devel at kde.org, kharvd at gmail.com



 M  +0 -3      CMakeLists.txt  
 M  +14 -15    dialogs/locationdialog.cpp  
 M  +1 -6      dialogs/locationdialog.ui  
 M  +1 -6      dialogs/wizlocation.ui  
 M  +10 -9     kswizard.cpp  
 M  +1 -10     tools/argloadcolorscheme.ui  
 M  +8 -8      tools/scriptbuilder.cpp  


--- trunk/KDE/kdeedu/kstars/kstars/CMakeLists.txt #1203703:1203704
@@ -69,8 +69,6 @@
     ${OPENGL_INCLUDE_DIRS}
 )
 
-add_definitions (-DQT3_SUPPORT -DQT3_SUPPORT_WARNINGS)
-
 ########### next target ###############
 set(libkstarstools_SRCS 
 	tools/altvstime.cpp
@@ -363,7 +361,6 @@
 target_link_libraries(kstars
     ${KDE4_KDECORE_LIBS}
 	${KDE4_KNEWSTUFF3_LIBS}
-	${KDE4_KDE3SUPPORT_LIBS}
 	SatLib
 	htmesh
 	${ZLIB_LIBRARIES}
--- trunk/KDE/kdeedu/kstars/kstars/dialogs/locationdialog.cpp #1203703:1203704
@@ -62,7 +62,7 @@
     connect( ui->NewLat, SIGNAL( textChanged( const QString & ) ), this, SLOT( dataChanged() ) );
     connect( ui->TZBox, SIGNAL( activated(int) ), this, SLOT( dataChanged() ) );
     connect( ui->DSTRuleBox, SIGNAL( activated(int) ), this, SLOT( dataChanged() ) );
-    connect( ui->GeoBox, SIGNAL( selectionChanged() ), this, SLOT( changeCity() ) );
+    connect( ui->GeoBox, SIGNAL( itemSelectionChanged () ), this, SLOT( changeCity() ) );
     connect( ui->AddCityButton, SIGNAL( clicked() ), this, SLOT( addCity() ) );
     connect( ui->ClearFieldsButton, SIGNAL( clicked() ), this, SLOT( clearFields() ) );
 
@@ -94,7 +94,7 @@
     KStarsData* data = KStarsData::Instance();
     foreach ( GeoLocation *loc, data->getGeoList() )
     {
-        ui->GeoBox->insertItem( loc->fullName() );
+        ui->GeoBox->addItem( loc->fullName() );
         filteredCityList.append( loc );
 
         //If TZ is not an even integer value, add it to listbox
@@ -109,7 +109,7 @@
     }
 
     //Sort the list of Cities alphabetically...note that filteredCityList may now have a different ordering!
-    ui->GeoBox->sort();
+    ui->GeoBox->sortItems();
 
     ui->CountLabel->setText( i18np("One city matches search criteria","%1 cities match search criteria", ui->GeoBox->count()) );
 
@@ -117,7 +117,7 @@
     ui->GeoBox->setCurrentItem( 0 );
     for( uint i=0; i < ui->GeoBox->count(); i++ ) {
         if ( ui->GeoBox->item(i)->text() == data->geo()->fullName() ) {
-            ui->GeoBox->setCurrentItem( i );
+            ui->GeoBox->setCurrentRow( i );
             break;
         }
     }
@@ -134,7 +134,6 @@
     timer->start( 500 );
 }
 
-
 void LocationDialog::filterCity() {
     KStarsData* data = KStarsData::Instance();
     ui->GeoBox->clear();
@@ -157,17 +156,17 @@
                 sp.toLower().startsWith( ui->ProvinceFilter->text().toLower() ) &&
                 ss.toLower().startsWith( ui->CountryFilter->text().toLower() ) ) {
 
-            ui->GeoBox->insertItem( loc->fullName() );
+            ui->GeoBox->addItem( loc->fullName() );
             filteredCityList.append( loc );
         }
     }
 
-    ui->GeoBox->sort();
+    ui->GeoBox->sortItems();
 
     ui->CountLabel->setText( i18np("One city matches search criteria","%1 cities match search criteria", ui->GeoBox->count()) );
 
-    if ( ui->GeoBox->firstItem() )		// set first item in list as selected
-        ui->GeoBox->setCurrentItem( ui->GeoBox->firstItem() );
+    if ( ui->GeoBox->count() > 0 )		// set first item in list as selected
+        ui->GeoBox->setCurrentItem( ui->GeoBox->item(0) );
 
     ui->MapView->repaint();
 }
@@ -179,7 +178,7 @@
     if ( ui->GeoBox->currentItem() >= 0 ) {
         for ( int i=0; i < filteredCityList.size(); ++i ) {
             GeoLocation *loc = filteredCityList.at(i);
-            if ( loc->fullName() == ui->GeoBox->currentText() ) {
+            if ( loc->fullName() == ui->GeoBox->currentItem()->text()) {
                 SelectedCity = loc;
                 break;
             }
@@ -295,7 +294,7 @@
             if ( ui->GeoBox->count() ) {
                 for ( uint i=0; i<ui->GeoBox->count(); i++ ) {
                     if ( ui->GeoBox->item(i)->text() == g->fullName() ) {
-                        ui->GeoBox->setCurrentItem( i );
+                        ui->GeoBox->setCurrentRow( i );
                         break;
                     }
                 }
@@ -317,16 +316,16 @@
         if ( ( abs(	lng - int( loc->lng()->Degrees() ) ) < 3 ) &&
                 ( abs( lat - int( loc->lat()->Degrees() ) ) < 3 ) ) {
 
-            ui->GeoBox->insertItem( loc->fullName() );
+            ui->GeoBox->addItem( loc->fullName() );
             filteredCityList.append( loc );
         }
     }
 
-    ui->GeoBox->sort();
+    ui->GeoBox->sortItems();
     ui->CountLabel->setText( i18np("One city matches search criteria","%1 cities match search criteria", ui->GeoBox->count()) );
 
-    if ( ui->GeoBox->firstItem() )		// set first item in list as selected
-        ui->GeoBox->setCurrentItem( ui->GeoBox->firstItem() );
+    if ( ui->GeoBox->count() > 0 )		// set first item in list as selected
+        ui->GeoBox->setCurrentItem( ui->GeoBox->item(0) );
 
     repaint();
 }
--- trunk/KDE/kdeedu/kstars/kstars/dialogs/locationdialog.ui #1203703:1203704
@@ -124,7 +124,7 @@
        </layout>
       </item>
       <item>
-       <widget class="K3ListBox" native="1" name="GeoBox" />
+       <widget class="QListWidget" native="1" name="GeoBox" />
       </item>
      </layout>
     </widget>
@@ -408,11 +408,6 @@
    <extends>KLineEdit</extends>
    <header>widgets/dmsbox.h</header>
   </customwidget>
-  <customwidget>
-   <class>K3ListBox</class>
-   <extends></extends>
-   <header>k3listbox.h</header>
-  </customwidget>
  </customwidgets>
  <tabstops>
   <tabstop>CityFilter</tabstop>
--- trunk/KDE/kdeedu/kstars/kstars/dialogs/wizlocation.ui #1203703:1203704
@@ -212,7 +212,7 @@
     </layout>
    </item>
    <item>
-    <widget class="K3ListBox" name="CityListBox" native="true">
+    <widget class="QListWidget" name="CityListBox" native="true">
      <property name="minimumSize">
       <size>
        <width>180</width>
@@ -237,11 +237,6 @@
    <extends>KLineEdit</extends>
    <header>widgets/dmsbox.h</header>
   </customwidget>
-  <customwidget>
-   <class>K3ListBox</class>
-   <extends></extends>
-   <header>k3listbox.h</header>
-  </customwidget>
  </customwidgets>
  <tabstops>
   <tabstop>CityFilter</tabstop>
--- trunk/KDE/kdeedu/kstars/kstars/kswizard.cpp #1203703:1203704
@@ -81,7 +81,7 @@
     //connect signals/slots
     connect( this, SIGNAL( user1Clicked() ), this, SLOT( slotNextPage() ) );
     connect( this, SIGNAL( user2Clicked() ), this, SLOT( slotPrevPage() ) );
-    connect( location->CityListBox, SIGNAL( selectionChanged() ), this, SLOT( slotChangeCity() ) );
+    connect( location->CityListBox, SIGNAL( itemSelectionChanged () ), this, SLOT( slotChangeCity() ) );
     connect( location->CityFilter, SIGNAL( textChanged( const QString & ) ), this, SLOT( slotFilterCities() ) );
     connect( location->ProvinceFilter, SIGNAL( textChanged( const QString & ) ), this, SLOT( slotFilterCities() ) );
     connect( location->CountryFilter, SIGNAL( textChanged( const QString & ) ), this, SLOT( slotFilterCities() ) );
@@ -121,7 +121,7 @@
     //Populate the CityListBox
     //flag the ID of the current City
     foreach ( GeoLocation *loc, data->getGeoList() ) {
-        location->CityListBox->insertItem( loc->fullName() );
+        location->CityListBox->addItem( loc->fullName() );
         filteredCityList.append( loc );
         if ( loc->fullName() == data->geo()->fullName() ) {
             Geo = loc;
@@ -129,15 +129,16 @@
     }
 
     //Sort alphabetically
-    location->CityListBox->sort();
+    location->CityListBox->sortItems();
     //preset to current city
-    location->CityListBox->setCurrentItem( location->CityListBox->findItem(QString(data->geo()->fullName()) ) );
+    location->CityListBox->setCurrentItem(location->CityListBox->findItems(QString(data->geo()->fullName()),
+									   Qt::MatchExactly).at(0));
 }
 
 void KSWizard::slotChangeCity() {
     if ( location->CityListBox->currentItem() >= 0 ) {
         for ( int i=0; i < filteredCityList.size(); ++i ) {
-            if ( filteredCityList[i]->fullName() == location->CityListBox->currentText() ) {
+            if ( filteredCityList[i]->fullName() == location->CityListBox->currentItem()->text() ) {
                 Geo = filteredCityList[i];
                 break;
             }
@@ -158,14 +159,14 @@
             hasPrefix( loc->translatedProvince(), location->ProvinceFilter->text()  )
             )
         {
-            location->CityListBox->insertItem( loc->fullName() );
+            location->CityListBox->addItem( loc->fullName() );
             filteredCityList.append( loc );
         }
     }
-    location->CityListBox->sort();
+    location->CityListBox->sortItems();
 
-    if ( location->CityListBox->firstItem() )  // set first item in list as selected
-        location->CityListBox->setCurrentItem( location->CityListBox->firstItem() );
+    if ( location->CityListBox->count() > 0 )  // set first item in list as selected
+        location->CityListBox->setCurrentItem( location->CityListBox->item(0) );
 }
 
 void KSWizard::slotDownload() {
--- trunk/KDE/kdeedu/kstars/kstars/tools/argloadcolorscheme.ui #1203703:1203704
@@ -17,19 +17,10 @@
     <number>6</number>
    </property>
    <item>
-    <widget class="K3ListBox" name="SchemeList" />
+    <widget class="QListWidget" name="SchemeList" />
    </item>
   </layout>
  </widget>
-  <customwidgets>
-  <customwidget>
-   <class>K3ListBox</class>
-   <extends></extends>
-   <header>k3listbox.h</header>
-   <container>0</container>
-   <pixmap></pixmap>
-  </customwidget>
- </customwidgets>
  <resources/>
  <connections/>
 </ui>
--- trunk/KDE/kdeedu/kstars/kstars/tools/scriptbuilder.cpp #1203703:1203704
@@ -471,7 +471,7 @@
     connect( argPrintImage->UseChartColors, SIGNAL( toggled(bool) ), this, SLOT( slotPrintImage() ) );
     connect( argSetColor->ColorName, SIGNAL( activated(const QString &) ), this, SLOT( slotChangeColorName() ) );
     connect( argSetColor->ColorValue, SIGNAL( changed(const QColor &) ), this, SLOT( slotChangeColor() ) );
-    connect( argLoadColorScheme->SchemeList, SIGNAL( clicked( Q3ListBoxItem* ) ), this, SLOT( slotLoadColorScheme() ) );
+    connect( argLoadColorScheme->SchemeList, SIGNAL( itemClicked ( QListWidgetItem * )), this, SLOT( slotLoadColorScheme() ) );
 
     //connect( sb->AppendINDIWait, SIGNAL ( toggled(bool) ), this, SLOT(slotINDIWaitCheck(bool)));
 
@@ -926,10 +926,10 @@
     }
 
     //init list of color scheme names
-    argLoadColorScheme->SchemeList->insertItem( i18nc( "use default color scheme", "Default Colors" ) );
-    argLoadColorScheme->SchemeList->insertItem( i18nc( "use 'star chart' color scheme", "Star Chart" ) );
-    argLoadColorScheme->SchemeList->insertItem( i18nc( "use 'night vision' color scheme", "Night Vision" ) );
-    argLoadColorScheme->SchemeList->insertItem( i18nc( "use 'moonless night' color scheme", "Moonless Night" ) );
+    argLoadColorScheme->SchemeList->addItem( i18nc( "use default color scheme", "Default Colors" ) );
+    argLoadColorScheme->SchemeList->addItem( i18nc( "use 'star chart' color scheme", "Star Chart" ) );
+    argLoadColorScheme->SchemeList->addItem( i18nc( "use 'night vision' color scheme", "Night Vision" ) );
+    argLoadColorScheme->SchemeList->addItem( i18nc( "use 'moonless night' color scheme", "Moonless Night" ) );
 
     QFile file;
     QString line;
@@ -939,7 +939,7 @@
 
         while ( !stream.atEnd() ) {
             line = stream.readLine();
-            argLoadColorScheme->SchemeList->insertItem( line.left( line.indexOf( ':' ) ) );
+            argLoadColorScheme->SchemeList->addItem( line.left( line.indexOf( ':' ) ) );
         }
         file.close();
     }
@@ -1700,7 +1700,7 @@
 
         } else if ( sf->name() == "loadColorScheme" ) {
             sb->ArgStack->setCurrentWidget( argLoadColorScheme );
-            argLoadColorScheme->SchemeList->setCurrentItem( argLoadColorScheme->SchemeList->findItem( sf->argVal(0).remove('\"'), 0 ) );
+            argLoadColorScheme->SchemeList->setCurrentItem( argLoadColorScheme->SchemeList->findItems( sf->argVal(0).remove('\"'), Qt::MatchExactly ).at(0) );
 
         } else if ( sf->name() == "stop" ) {
             sb->ArgStack->setCurrentWidget( argBlank );
@@ -2431,7 +2431,7 @@
     if ( sf->name() == "loadColorScheme" ) {
         setUnsavedChanges( true );
 
-        sf->setArg( 0, '\"' + argLoadColorScheme->SchemeList->currentText() + '\"' );
+        sf->setArg( 0, '\"' + argLoadColorScheme->SchemeList->currentItem()->text() + '\"' );
         sf->setValid( true );
     } else {
         warningMismatch( "loadColorScheme" );

From mutlaqja at ikarustech.com  Sun Dec  5 23:21:25 2010
From: mutlaqja at ikarustech.com (Jasem Mutlaq)
Date: Mon, 6 Dec 2010 01:21:25 +0300
Subject: [Kstars-devel]  Blue KStars!
Message-ID: <AANLkTinq5A+8=E435KZA7M64Jd2WFD8DJBbYHGCFaU05@mail.gmail.com>

Hello,

I'm using KStars from SVN TRUNK, and I'm getting a blue opaque horizon, and
blue stars. The Sun does not only appear as blue, but squarish blue as well.
Anyone working on this? How about infoboxes + openGL? any solution to that?

--
Best Regards,
Jasem Mutlaq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kstars-devel/attachments/20101206/b0f184df/attachment-0001.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blue_kstars.png
Type: image/png
Size: 46670 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kstars-devel/attachments/20101206/b0f184df/attachment-0001.png 

From akarshsimha at gmail.com  Mon Dec  6 00:10:04 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Sun, 5 Dec 2010 17:10:04 -0600
Subject: [Kstars-devel] Re: Blue KStars!
In-Reply-To: <AANLkTinq5A+8=E435KZA7M64Jd2WFD8DJBbYHGCFaU05@mail.gmail.com>
References: <AANLkTinq5A+8=E435KZA7M64Jd2WFD8DJBbYHGCFaU05@mail.gmail.com>
Message-ID: <20101205231003.GA2227@K9>

On Mon, Dec 06, 2010 at 01:21:25AM +0300, Jasem Mutlaq wrote:
>    Hello,
> 
>    I'm using KStars from SVN TRUNK, and I'm getting a blue opaque horizon,
>    and blue stars. The Sun does not only appear as blue, but squarish blue as
>    well. Anyone working on this? How about infoboxes + openGL? any solution
>    to that?

Hi Jasem

Yes, this looks like the infoboxes + openGL problem. I don't know
about all stars being blue. The Sun definitely is squarish blue. But
you should have red stars too...

And yes, I'll be working on it starting December 15th, after my exams
are over. That gives me roughly a month through the Beta and RC
releases, to fix it.

But I'd be glad if someone else could start working on it as well.

My backup plan would be to ship the GL mode as "alpha" or whatever,
disabled by default, but can be turned on by users who want speed over
these conveniences and who want to test and report bugs. But of
course, for this, we must first get runtime switching between OpenGL
and QPainter backends working. I have an idea of how we might go about
doing it -- make the non-drawing parts of SkyMap into a class that's a
QGraphicsView, and depending on the painting backend chosen, we either
paint with a class that draws using GL, or a class that uses the usual
QPainter. I don't see many alternative routes, but I'd be glad to get
some suggestions.

Regards
Akarsh

From lists at faintfuzzies.ca  Mon Dec  6 19:41:14 2010
From: lists at faintfuzzies.ca (DancesWithWords)
Date: Mon, 6 Dec 2010 13:41:14 -0500
Subject: [Kstars-devel]  Printing Observing Plan
Message-ID: <201012061341.14595.lists@faintfuzzies.ca>

Has anyone yet requested have the possibility of print the observing plan?  In 
a format suitable for use in the field?  Like what Skytools does?

===
bruce

-- 
DancesWithWords

From achiestdragon at gmail.com  Mon Dec  6 21:25:58 2010
From: achiestdragon at gmail.com (David Powell)
Date: Mon, 6 Dec 2010 20:25:58 +0000
Subject: [Kstars-devel]  polar view
Message-ID: <AANLkTimj3W87FFOwUKj5fH1r1GCw9AQFD2hTaCHNk0wK@mail.gmail.com>

hi all
 i have a feature request

quick description
is it possible to add a  polar based view as well as the default alt/az
system

longer discription
when using kstars the view is as it would be for a alt az mount   ie
centered on the location with the views rotation
based on the point directly above
if using a polar mount on a telescope connected to it via inid then the
displayed data should  be rotated around the pole

mainly if you set the fov symbol to a rectangle to display the fov of an
attached cam then it is at the wrong rotation for the actual
fov  amongst other things


yours
david
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kstars-devel/attachments/20101206/55ae8697/attachment.htm 

From akarshsimha at gmail.com  Fri Dec 10 09:10:24 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 02:10:24 -0600
Subject: [Kstars-devel] Re: Printing Observing Plan
In-Reply-To: <201012061341.14595.lists@faintfuzzies.ca>
References: <201012061341.14595.lists@faintfuzzies.ca>
Message-ID: <20101210081024.GB2326@K9>

On Mon, Dec 06, 2010 at 01:41:14PM -0500, DancesWithWords wrote:
> Has anyone yet requested have the possibility of print the observing plan?  In 
> a format suitable for use in the field?  Like what Skytools does?

Well, I don't think anyone has requested that yet. Please feel free to
add a wishlist bug on https://bugs.kde.org

Hopefully, I'll be able to spend some time this winter trying to
attend to KStars, but please feel free to nag me till I get this done
:D.

Also, some description on how Skytools does this would help.

Regards
Akarsh

From akarshsimha at gmail.com  Fri Dec 10 09:57:59 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 02:57:59 -0600
Subject: [Kstars-devel]  Fwd: Fwd: star catalog
Message-ID: <20101210085759.GA10264@K9>

Hi

Sorry, I got this reply from Jason pretty long back, but I don't know
why I didn't forward it right away.

Many apologies for my delayed response.

Regards
Akarsh
-------------- next part --------------
An embedded message was scrubbed...
From: Jason Harris <kstars at 30doradus.org>
Subject: Fwd: star catalog
Date: Fri, 12 Nov 2010 09:14:55 -0800
Size: 9181
Url: http://mail.kde.org/pipermail/kstars-devel/attachments/20101210/ad6751a2/attachment.eml 

From envite at rolamasao.org  Fri Dec 10 10:06:18 2010
From: envite at rolamasao.org (Noel David Torres =?iso-8859-15?q?Ta=F1o?=)
Date: Fri, 10 Dec 2010 09:06:18 +0000
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <20101210085759.GA10264@K9>
References: <20101210085759.GA10264@K9>
Message-ID: <201012100906.19178.envite@rolamasao.org>

On Viernes 10 Diciembre 2010 08:57:59 Akarsh Simha escribi?:
> Hi
> 
> Sorry, I got this reply from Jason pretty long back, but I don't know
> why I didn't forward it right away.
> 
> Many apologies for my delayed response.
> 
> Regards
> Akarsh

Do not worry, we are all humans (stars do not write e-mails, even when 
catalogued).

So, it is that both Tycho-2 and NOMAD are PD with citation, isn't it?

Thanks

Noel
er Envite

P.S. I will need you more, soon, since it seems that the Tycho2 Debian package 
is on its way to be accepted, and I will need some extra help doing fancy 
things to the catalogues

From akarshsimha at gmail.com  Fri Dec 10 10:10:01 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 03:10:01 -0600
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <201012100906.19178.envite@rolamasao.org>
References: <20101210085759.GA10264@K9>
	<201012100906.19178.envite@rolamasao.org>
Message-ID: <AANLkTi=8G4Md7hFDvrJr-OeWL7DQG=knoEKO5-G=fASc@mail.gmail.com>

On 10 December 2010 03:06, Noel David Torres Ta?o <envite at rolamasao.org> wrote:
> On Viernes 10 Diciembre 2010 08:57:59 Akarsh Simha escribi?:
>> Hi
>>
>> Sorry, I got this reply from Jason pretty long back, but I don't know
>> why I didn't forward it right away.
>>
>> Many apologies for my delayed response.
>>
>> Regards
>> Akarsh
>
> Do not worry, we are all humans (stars do not write e-mails, even when
> catalogued).
>
> So, it is that both Tycho-2 and NOMAD are PD with citation, isn't it?

Effectively, yes! At least for use with KStars.

From akarshsimha at gmail.com  Fri Dec 10 10:12:30 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 03:12:30 -0600
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <AANLkTi=8G4Md7hFDvrJr-OeWL7DQG=knoEKO5-G=fASc@mail.gmail.com>
References: <20101210085759.GA10264@K9>
	<201012100906.19178.envite@rolamasao.org>
	<AANLkTi=8G4Md7hFDvrJr-OeWL7DQG=knoEKO5-G=fASc@mail.gmail.com>
Message-ID: <AANLkTinkdDt811vVb+FCQzSX4J4GXfDozxnawBmffYSF@mail.gmail.com>

>> So, it is that both Tycho-2 and NOMAD are PD with citation, isn't it?
>
> Effectively, yes! At least for use with KStars.

Actually, that's probably not enough for you. Yes, they are public
domain, according to the citations we have.

The NGC/IC data is partially from the SAC catalog, which I've again
used with permission. The license on the SAC catalog says "This is not
suitable for commercial use", but we are GPL-ed, so I wrote a mail
asking about this. The response was approximately that "This was
stated with the intention that it should not be sold separately. For
use with a program, it's fine.". Let me know if you need that. I think
you probably don't, because that's shipped with KStars by default
anyway!

Thanks a ton! I'm sure this will be very useful to Debian + KStars
users (I'm one of them, although I use trunk! :D)

Regards
Akarsh

From envite at rolamasao.org  Fri Dec 10 10:32:51 2010
From: envite at rolamasao.org (Noel David Torres =?iso-8859-1?q?Ta=F1o?=)
Date: Fri, 10 Dec 2010 09:32:51 +0000
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <AANLkTinkdDt811vVb+FCQzSX4J4GXfDozxnawBmffYSF@mail.gmail.com>
References: <20101210085759.GA10264@K9>
	<AANLkTi=8G4Md7hFDvrJr-OeWL7DQG=knoEKO5-G=fASc@mail.gmail.com>
	<AANLkTinkdDt811vVb+FCQzSX4J4GXfDozxnawBmffYSF@mail.gmail.com>
Message-ID: <201012100932.51784.envite@rolamasao.org>

On Viernes 10 Diciembre 2010 09:12:30 usted escribi?:
> >> So, it is that both Tycho-2 and NOMAD are PD with citation, isn't it?
> > 
> > Effectively, yes! At least for use with KStars.
> 
> Actually, that's probably not enough for you. Yes, they are public
> domain, according to the citations we have.
> 
So, please correct me, the legal state (to Tycho2) is:

Files: deepstars.dat
Copyright: 2008 Akarsh Simha <kstars-devel at kde.org>, Jason Harris <kstars-
devel at kde.org>
License: GPL
X-Original-Data-Copyright: 2000 E. H?g, C. Fabricius, V.V. Makarov, S. Urban, 
T. Corbin, G. Wycoff, U. Bastian, P. Schwekendiek, and A. Wicenec
                           1997 ESA
X-Reference: Astron. Astrophys. 355.2, P L19-L22 (2000) :
             The Tycho-2 Catalogue of the 2.5 Million Brightest Stars.

or must I delete X-Original-Data-Copyright and X-Reference and add something 
like

X-Original-Data-License: Public Domain by USNO

Moreover, the data you used to compile deepstars.dat does come from the 
published Tycho2 catalogue (copyright Erik H?g et al) or directly from raw 
USNO data?

That is, should I cite H?g or ESA or just USNO? I must confess I'm a bit lost, 
since the Tycho2 name suggests citing H?g and ESA.


> The NGC/IC data is partially from the SAC catalog, which I've again
> used with permission. The license on the SAC catalog says "This is not
> suitable for commercial use", but we are GPL-ed, so I wrote a mail
> asking about this. The response was approximately that "This was
> stated with the intention that it should not be sold separately. For
> use with a program, it's fine.". Let me know if you need that. I think
> you probably don't, because that's shipped with KStars by default
> anyway!

That's work for another Debian maintainer ;) but as soon as this is settled 
for Tycho2 I will contact him in order to be sure.
> 
> Thanks a ton! I'm sure this will be very useful to Debian + KStars
> users (I'm one of them, although I use trunk! :D)
> 
> Regards
> Akarsh

No no, thanks to you for your understanding abou how hard this can be

Noel
er Envite

From akarshsimha at gmail.com  Fri Dec 10 11:03:12 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 04:03:12 -0600
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <201012100932.51784.envite@rolamasao.org>
References: <20101210085759.GA10264@K9>
	<AANLkTi=8G4Md7hFDvrJr-OeWL7DQG=knoEKO5-G=fASc@mail.gmail.com>
	<AANLkTinkdDt811vVb+FCQzSX4J4GXfDozxnawBmffYSF@mail.gmail.com>
	<201012100932.51784.envite@rolamasao.org>
Message-ID: <20101210100312.GO2326@K9>


Hi Noel, Jason

@Jason: If you wouldn't mind, could you scroll down to the place where
	I say "I'm copying to Jason" and confirm the validity of my
	claims?

> So, please correct me, the legal state (to Tycho2) is:
> 
> Files: deepstars.dat
> Copyright: 2008 Akarsh Simha <kstars-devel at kde.org>, Jason Harris <kstars-
> devel at kde.org>
> License: GPL
> X-Original-Data-Copyright: 2000 E. H?g, C. Fabricius, V.V. Makarov, S. Urban, 
> T. Corbin, G. Wycoff, U. Bastian, P. Schwekendiek, and A. Wicenec
>                            1997 ESA
> X-Reference: Astron. Astrophys. 355.2, P L19-L22 (2000) :
>              The Tycho-2 Catalogue of the 2.5 Million Brightest Stars.
> 
> or must I delete X-Original-Data-Copyright and X-Reference and add something 
> like
> 
> X-Original-Data-License: Public Domain by USNO

Could you possibly keep both?  

Also, isn't it public domain by NASA (and not ESA/H??g?)

AFAIK, we used data from the NASA ADC, whose policies are here:
http://web.archive.org/web/20070303235508/http://adc.astro.umd.edu/adc/questions_feedback.html#policies1
for Tycho-2 and that's what deepstars.dat was built out of.

The Tycho-2 catalog itself was available there, and since it was hosted by the ADC,
http://web.archive.org/web/20060908122029/adc.astro.umd.edu/cgi-bin/adc/cat.pl?/catalogs/1/1259/
the policy must be applicable to Tycho-2 as well.

So maybe we should say "(c) Erik H??g et al.", but then mention
"Public Domain according to <NASA ADC citation>"?

When USNO's data was obtained, Jason matched the Tycho-2 stars were
matched against the NASA ADC Tycho-2, and got rid of them from the
USNO, and sent me the rest of the USNO data for creating the binary
files. So for the USNO catalog (USNO-NOMAD-1e8.dat), the mail I just
forwarded applies.

> Moreover, the data you used to compile deepstars.dat does come from the 
> published Tycho2 catalogue (copyright Erik H?g et al) or directly from raw 
> USNO data?

I think it comes from the Tycho-2. As I said, Jason sent me Tycho-2
data first, before he got any data from USNO, and sieved out Tycho-2
stars from the NOMAD. I'm copying to Jason to see if he can correct
me.

> That is, should I cite H?g or ESA or just USNO? I must confess I'm a bit lost, 
> since the Tycho2 name suggests citing H?g and ESA.

I think we should cite H??g and ESA, but mention that it is public
domain by NASA ADC citation.

> > The NGC/IC data is partially from the SAC catalog, which I've again
> > used with permission. The license on the SAC catalog says "This is not
> > suitable for commercial use", but we are GPL-ed, so I wrote a mail
> > asking about this. The response was approximately that "This was
> > stated with the intention that it should not be sold separately. For
> > use with a program, it's fine.". Let me know if you need that. I think
> > you probably don't, because that's shipped with KStars by default
> > anyway!
> 
> That's work for another Debian maintainer ;) but as soon as this is settled 
> for Tycho2 I will contact him in order to be sure.

Oh! I don't think this is an issue. Don't bother. I specified this
detail in the data file itself (it's an ASCII file)

> > Thanks a ton! I'm sure this will be very useful to Debian + KStars
> > users (I'm one of them, although I use trunk! :D)
> > 
> > Regards
> > Akarsh
> 
> No no, thanks to you for your understanding abou how hard this can be

Well, it is important to keep these things absolutely clean. I'm very
sorry I haven't been concentrating on KStars in the past. Hopefully,
I'll be able to spend a lot of time on it in December!

Regards
Akarsh

From akarshsimha at gmail.com  Fri Dec 10 11:11:05 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 04:11:05 -0600
Subject: [Kstars-devel] Re: polar view
In-Reply-To: <AANLkTimj3W87FFOwUKj5fH1r1GCw9AQFD2hTaCHNk0wK@mail.gmail.com>
References: <AANLkTimj3W87FFOwUKj5fH1r1GCw9AQFD2hTaCHNk0wK@mail.gmail.com>
Message-ID: <20101210101105.GS2326@K9>

>    quick description
>    is it possible to add a* polar based view as well as the default alt/az
>    system
> 
>    longer discription
>    when using kstars the view is as it would be for a alt az mount** ie*
>    centered on the location with the views rotation
>    based on the point directly above
>    if using a polar mount on a telescope connected to it via inid then the
>    displayed data should* be rotated around the pole
> 
>    mainly if you set the fov symbol to a rectangle to display the fov of an
>    attached cam then it is at the wrong rotation for the actual
>    fov* amongst other things

Hi David

I don't understand your point completely. As far as I know, the
"Horizontal Coordinates" mode (I think it's now called "Switch to
Horizonal View") in one of the menus uses Alt-Az coordinates.

Firstly, the FOV symbols still don't rotate -- they are fixed
horizontally, which is unfortunate, and that's something we must
change very soon.

But what you are saying, I guess, is (once we get them to be
rotatable) that they should rotate as expected by slewing a telescope
on an alt/az mount. I think that should be doable to.

I'll try to do this after 15th December. This might be an interesting
GCI task as well.

Regards
Akarsh

From envite at rolamasao.org  Fri Dec 10 11:49:47 2010
From: envite at rolamasao.org (Noel David Torres =?iso-8859-1?q?Ta=F1o?=)
Date: Fri, 10 Dec 2010 10:49:47 +0000
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <20101210100312.GO2326@K9>
References: <20101210085759.GA10264@K9>
	<201012100932.51784.envite@rolamasao.org>
	<20101210100312.GO2326@K9>
Message-ID: <201012101049.50304.envite@rolamasao.org>

On Viernes 10 Diciembre 2010 10:03:12 usted escribi?:
> Hi Noel, Jason
> 
> @Jason: If you wouldn't mind, could you scroll down to the place where
> 	I say "I'm copying to Jason" and confirm the validity of my
> 	claims?
> 
> > So, please correct me, the legal state (to Tycho2) is:
> > 
> > Files: deepstars.dat
> > Copyright: 2008 Akarsh Simha <kstars-devel at kde.org>, Jason Harris
> > <kstars- devel at kde.org>
> > License: GPL
> > X-Original-Data-Copyright: 2000 E. H?g, C. Fabricius, V.V. Makarov, S.
> > Urban, T. Corbin, G. Wycoff, U. Bastian, P. Schwekendiek, and A. Wicenec
> > 
> >                            1997 ESA
> > 
> > X-Reference: Astron. Astrophys. 355.2, P L19-L22 (2000) :
> >              The Tycho-2 Catalogue of the 2.5 Million Brightest Stars.
> > 
> > or must I delete X-Original-Data-Copyright and X-Reference and add
> > something like
> > 
> > X-Original-Data-License: Public Domain by USNO
> 
> Could you possibly keep both?

Yes, I can have as many X- lines as needed
> 
> Also, isn't it public domain by NASA (and not ESA/H??g?)

Tycho2 catalogue data is based on observations by the ESA Hipparcos satellite 
from 1989 to 1993 (Erik H?g article) and proper motions included in the 
catalogue are derived from these observations and other 143 catalogues. So, 
the original data are copyright of the ESA Hipparcos mission, not USNO nor 
NASA, and the 'cooked' data are copyright H?g et al (or their institutions, 
namely CUO, USNO, ARI and ESO).
> 
> AFAIK, we used data from the NASA ADC, whose policies are here:
> http://web.archive.org/web/20070303235508/http://adc.astro.umd.edu/adc/ques
> tions_feedback.html#policies1 for Tycho-2 and that's what deepstars.dat was
> built out of.

I can not access ADC, but I suposse CDS's Readme is the same since 
http://cdsweb.u-strasbg.fr/hipparcos.html says ADC is a mirror of CDS. Since 
there is no relevant info in the Readme, this should imply one of
a) ADC has no permission to publish Tycho2 as PD
b) ADC has permission (either explicit or implicit) to publish Tycho2 as PD

Assuming the second means that at some point, ESA and H?g give their 
copyrights out.
> 
> The Tycho-2 catalog itself was available there, and since it was hosted by
> the ADC,
> http://web.archive.org/web/20060908122029/adc.astro.umd.edu/cgi-bin/adc/ca
> t.pl?/catalogs/1/1259/ the policy must be applicable to Tycho-2 as well.

True, but read my last sentences
> 
> So maybe we should say "(c) Erik H??g et al.", but then mention
> "Public Domain according to <NASA ADC citation>"?

I think that would be the way, but mentioning ESA too
> 
> When USNO's data was obtained, Jason matched the Tycho-2 stars were
> matched against the NASA ADC Tycho-2, and got rid of them from the
> USNO, and sent me the rest of the USNO data for creating the binary
> files. So for the USNO catalog (USNO-NOMAD-1e8.dat), the mail I just
> forwarded applies.

Good news :) but that menas (being scary) that Tycho2 data was used in the 
compilation of KStars' USNO... better don't think on that
> 
> > Moreover, the data you used to compile deepstars.dat does come from the
> > published Tycho2 catalogue (copyright Erik H?g et al) or directly from
> > raw USNO data?
> 
> I think it comes from the Tycho-2. As I said, Jason sent me Tycho-2
> data first, before he got any data from USNO, and sieved out Tycho-2
> stars from the NOMAD. I'm copying to Jason to see if he can correct
> me.
> 
> > That is, should I cite H?g or ESA or just USNO? I must confess I'm a bit
> > lost, since the Tycho2 name suggests citing H?g and ESA.
> 
> I think we should cite H??g and ESA, but mention that it is public
> domain by NASA ADC citation.

Agree
> 
> > > The NGC/IC data is partially from the SAC catalog, which I've again
> > > used with permission. The license on the SAC catalog says "This is not
> > > suitable for commercial use", but we are GPL-ed, so I wrote a mail
> > > asking about this. The response was approximately that "This was
> > > stated with the intention that it should not be sold separately. For
> > > use with a program, it's fine.". Let me know if you need that. I think
> > > you probably don't, because that's shipped with KStars by default
> > > anyway!
> > 
> > That's work for another Debian maintainer ;) but as soon as this is
> > settled for Tycho2 I will contact him in order to be sure.
> 
> Oh! I don't think this is an issue. Don't bother. I specified this
> detail in the data file itself (it's an ASCII file)
> 
> > > Thanks a ton! I'm sure this will be very useful to Debian + KStars
> > > users (I'm one of them, although I use trunk! :D)
> > > 
> > > Regards
> > > Akarsh
> > 
> > No no, thanks to you for your understanding abou how hard this can be
> 
> Well, it is important to keep these things absolutely clean. I'm very
> sorry I haven't been concentrating on KStars in the past. Hopefully,
> I'll be able to spend a lot of time on it in December!
> 
> Regards
> Akarsh

So let's do this this way:

Files: deepstars.dat
Copyright: 2008 Akarsh Simha <kstars-devel at kde.org>, Jason Harris <kstars-
devel at kde.org>
X-Original-Data-Copyright: 2000 E. H?g, C. Fabricius, V.V. Makarov, S. Urban, 
T. Corbin, G. Wycoff, U. Bastian, P. Schwekendiek, and A. Wicenec
                           1997 ESA (Hipparcos mission)
X-Reference: Astron. Astrophys. 355.2, P L19-L22 (2000) :
             The Tycho-2 Catalogue of the 2.5 Million Brightest Stars.
X-Original-Data-License: Public Domain (as data has been retrieved by Authors 
from NASA ADC whose policy is PD, as stated in 
http://web.archive.org/web/20060908122029/adc.astro.umd.edu/cgi-
bin/adc/cat.pl?/catalogs/1/1259/)
License: GPL

Hope it is true and ok for everybody this way

Noel
er Envite
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kstars-devel/attachments/20101210/18e15c1f/attachment.sig 

From akarshsimha at gmail.com  Fri Dec 10 12:14:35 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 10 Dec 2010 05:14:35 -0600
Subject: [Kstars-devel] Re: Fwd: Fwd: star catalog
In-Reply-To: <201012101049.50304.envite@rolamasao.org>
References: <20101210085759.GA10264@K9>
	<201012100932.51784.envite@rolamasao.org>
	<20101210100312.GO2326@K9>
	<201012101049.50304.envite@rolamasao.org>
Message-ID: <20101210111435.GX2326@K9>

Hi Noel

> Tycho2 catalogue data is based on observations by the ESA Hipparcos satellite 
> from 1989 to 1993 (Erik H?g article) and proper motions included in the 
> catalogue are derived from these observations and other 143 catalogues. So, 
> the original data are copyright of the ESA Hipparcos mission, not USNO nor 
> NASA, and the 'cooked' data are copyright H?g et al (or their institutions, 
> namely CUO, USNO, ARI and ESO).
> > 
> > AFAIK, we used data from the NASA ADC, whose policies are here:
> > http://web.archive.org/web/20070303235508/http://adc.astro.umd.edu/adc/ques
> > tions_feedback.html#policies1 for Tycho-2 and that's what deepstars.dat was
> > built out of.
> 
> I can not access ADC, but I suposse CDS's Readme is the same since 
> http://cdsweb.u-strasbg.fr/hipparcos.html says ADC is a mirror of CDS. Since 
> there is no relevant info in the Readme, this should imply one of
> a) ADC has no permission to publish Tycho2 as PD
> b) ADC has permission (either explicit or implicit) to publish Tycho2 as PD
> 
> Assuming the second means that at some point, ESA and H?g give their 
> copyrights out.
> > 
> > The Tycho-2 catalog itself was available there, and since it was hosted by
> > the ADC,
> > http://web.archive.org/web/20060908122029/adc.astro.umd.edu/cgi-bin/adc/ca
> > t.pl?/catalogs/1/1259/ the policy must be applicable to Tycho-2 as well.
> 
> True, but read my last sentences

Yes, the terms look flaky. I wonder if they really keep in mind that
astronomy programs might want to use it, and they should have clear
terms and conditions.

Yes, the ADC is now down. But that was, according to Jason, the source
from where he downloaded the files.

If we need further proof, we could write to Cartes du Ciel and
Stellarium. I think both of them use that. And here's Cartes
distributing Tycho-2 data in a downloadable package:
http://www.stargazing.net/astropc/oldversion/download.html

While of course, these are not legal support, if anything, it gives me
more confidence in believing that ADC was not shut down because of
copyright violation or something.


> > So maybe we should say "(c) Erik H??g et al.", but then mention
> > "Public Domain according to <NASA ADC citation>"?
> 
> I think that would be the way, but mentioning ESA too

Yes!

> > When USNO's data was obtained, Jason matched the Tycho-2 stars were
> > matched against the NASA ADC Tycho-2, and got rid of them from the
> > USNO, and sent me the rest of the USNO data for creating the binary
> > files. So for the USNO catalog (USNO-NOMAD-1e8.dat), the mail I just
> > forwarded applies.
> 
> Good news :) but that menas (being scary) that Tycho2 data was used in the 
> compilation of KStars' USNO... better don't think on that

I don't understand the implications. You mean that, in the event that
Tycho-2 is not really public domain, then USNO can't be public domain
either because we used that data to build USNO? But considering that
the data is not included, is that a problem? It's just selective
removal, but none of the Tycho-2 data is in USNO.

> > > That is, should I cite H?g or ESA or just USNO? I must confess I'm a bit
> > > lost, since the Tycho2 name suggests citing H?g and ESA.
> > 
> > I think we should cite H??g and ESA, but mention that it is public
> > domain by NASA ADC citation.
> 
> Agree

Okay!

> So let's do this this way:
> 
> Files: deepstars.dat
> Copyright: 2008 Akarsh Simha <kstars-devel at kde.org>, Jason Harris <kstars-
> devel at kde.org>
> X-Original-Data-Copyright: 2000 E. H?g, C. Fabricius, V.V. Makarov, S. Urban, 
> T. Corbin, G. Wycoff, U. Bastian, P. Schwekendiek, and A. Wicenec
>                            1997 ESA (Hipparcos mission)
> X-Reference: Astron. Astrophys. 355.2, P L19-L22 (2000) :
>              The Tycho-2 Catalogue of the 2.5 Million Brightest Stars.
> X-Original-Data-License: Public Domain (as data has been retrieved by Authors 
> from NASA ADC whose policy is PD, as stated in 
> http://web.archive.org/web/20060908122029/adc.astro.umd.edu/cgi-
> bin/adc/cat.pl?/catalogs/1/1259/)
> License: GPL
> 
> Hope it is true and ok for everybody this way

This looks perfect to me!

Is there someone you know, whom we can consult on this matter, to see
if this is absolutely clear? I could write to developers of Stellarium
and the author of Cartes if required, and see what they have to say
about Tycho-2.

Regards
Akarsh

From achiestdragon at gmail.com  Fri Dec 10 13:30:35 2010
From: achiestdragon at gmail.com (David Powell)
Date: Fri, 10 Dec 2010 12:30:35 +0000
Subject: [Kstars-devel] Re: polar view
In-Reply-To: <20101210101105.GS2326@K9>
References: <AANLkTimj3W87FFOwUKj5fH1r1GCw9AQFD2hTaCHNk0wK@mail.gmail.com>
	<20101210101105.GS2326@K9>
Message-ID: <AANLkTi=KSsyA__16wRGFRc9ZBOyPSLu+BwxtSz_g6t63@mail.gmail.com>

hi Akarsh
guess i need to clarify the problem a bit more
probably best way would be to explain the problem i guess

best observation angle is vertical (shortest path though the atmosphear)
if using a polor mount on the scope then you avoid the need for the scope to
have to reach its rotation point like on the "horizontal"/alt az system
if you are using kstars to look at the point directly above  then as you may

know  panning around there the view rotates around that point
making it hard to both get your bearings properly
if using kstars with a connected polar mount scope then that view rotation
axis should
be alligned to the celestial pole where it has the same problem
one of the advantages of using a polar mount is it that the aria directly
above can be photographed
without having actual fov rotation during a exposure

this way  other than rotation of the fov to compencate is perferabe and a
lot more pratical to follow whats happening
as the sky rotation point  matches the equipment setup
then the fov rotation correction is only needed to correct the rotation of
the cam angle on the tube of the scope itself as just a user setable offset
value

from the programming side i guess its as easy eather way to manage this but
from a usage point of view
if fov only rotation is used then it would be fair to say ..
that trying to interprate the fact that your view is using one rotation axis
and the scope fov using another at
although the scope and fov view are correctly displayed trying to
intrerprate the view angle and navigate it as displayed is tricky to say the
least

Regards
David


On Fri, Dec 10, 2010 at 10:11 AM,  Simha <akarshsimha at gmail.com> wrote:

> >    quick description
> >    is it possible to add a* polar based view as well as the default
> alt/az
> >    system
> >
> >    longer discription
> >    when using kstars the view is as it would be for a alt az mount** ie*
> >    centered on the location with the views rotation
> >    based on the point directly above
> >    if using a polar mount on a telescope connected to it via inid then
> the
> >    displayed data should* be rotated around the pole
> >
> >    mainly if you set the fov symbol to a rectangle to display the fov of
> an
> >    attached cam then it is at the wrong rotation for the actual
> >    fov* amongst other things
>
> Hi David
>
> I don't understand your point completely. As far as I know, the
> "Horizontal Coordinates" mode (I think it's now called "Switch to
> Horizonal View") in one of the menus uses Alt-Az coordinates.
>
> Firstly, the FOV symbols still don't rotate -- they are fixed
> horizontally, which is unfortunate, and that's something we must
> change very soon.
>
> But what you are saying, I guess, is (once we get them to be
> rotatable) that they should rotate as expected by slewing a telescope
> on an alt/az mount. I think that should be doable to.
>
> I'll try to do this after 15th December. This might be an interesting
> GCI task as well.
>
> Regards
> Akarsh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kstars-devel/attachments/20101210/51951aeb/attachment.htm 

From lists at faintfuzzies.ca  Fri Dec 10 17:22:44 2010
From: lists at faintfuzzies.ca (DancesWithWords)
Date: Fri, 10 Dec 2010 11:22:44 -0500
Subject: [Kstars-devel] Re: Printing Observing Plan
In-Reply-To: <20101210081024.GB2326@K9>
References: <201012061341.14595.lists@faintfuzzies.ca>
	<20101210081024.GB2326@K9>
Message-ID: <201012101122.44631.lists@faintfuzzies.ca>

On December 10, 2010 03:10:24 am Akarsh Simha wrote:
> On Mon, Dec 06, 2010 at 01:41:14PM -0500, DancesWithWords wrote:
> > Has anyone yet requested have the possibility of print the observing
> > plan?  In a format suitable for use in the field?  Like what Skytools
> > does?
> 
> Well, I don't think anyone has requested that yet. Please feel free to
> add a wishlist bug on https://bugs.kde.org
> 
> Hopefully, I'll be able to spend some time this winter trying to
> attend to KStars, but please feel free to nag me till I get this done
> 
> :D.
> 
> Also, some description on how Skytools does this would help.
> 
> Regards
> Akarsh

I don't have any of the programs (as I'm a Linux only guy and don't have 
access to commercial Windows based programs)  that create object per page 
observing sheets, so I've put out a call to a couple of  astronomy clubs that 
I belong to to send me PDF or screen captures from the most popular programs 
that do this.  I'll forward them to you as they come in.

Interestingly, Kstars does much of what I would want in a field sheet printout.  
telescope used, eye pieces being used, a place to note sky and weather 
conditions.  Your field sheet would be one object per sheet with 1 to 3 star 
field images included.  i.e. the first image field would be a wide stars field 
view of the objects location.  The second is usual the size of your specified 
finders field view and the third image is base on the size of field view of the 
proposed eye piece you plan to view the object with.

Why would some need such a sheet:  Well there are a lots of visual observers 
who don't have or choice not use goto scopes and don't take laptops or 
computers into the field.  For those individuals an observing plan that can be 
printed out makes great sense.  This especially true if it is based on the 
program you actually use on a regular basis.

Normally I've written my notes on whatever is handy,  After more than 6 years 
of this I've decided it is a very bad idea.  Since you have including the 
planning part in Ktars I've been try to find all those note and input them into 
Kstars.  Not fun.


-- 
DancesWithWords

From smfiso2006 at libero.it  Wed Dec 15 16:45:11 2010
From: smfiso2006 at libero.it (smfiso2006 at libero.it)
Date: Wed, 15 Dec 2010 16:45:11 +0100 (CET)
Subject: [Kstars-devel]  I: Re: Kstars & SkyWatcher EQ3 SynScan
Message-ID: <4338776.2927451292427911956.JavaMail.defaultUser@defaultHost>



>----Messaggio originale----
>Da: jharris at 30doradus.org
>Data: 09/12/2010 17.39
>A: "smfiso2006 at libero.it"<smfiso2006 at libero.it>
>Ogg: Re: Kstars &amp; SkyWatcher EQ3 SynScan
>
>Please email your question to the kstars mailing list:
>kstars-devel at kde.org.  I am no longer involved with KStars
>development.
>
>regards,
>Jason
>
>On Thu, Dec 9, 2010 at 5:02 AM, smfiso2006 at libero.it
><smfiso2006 at libero.it> wrote:
>> Maybe I'm going to buy a SkyWatcher EQ3 SynScan , would it work with Kstars
>> ?
>>
>



From mutlaqja at ikarustech.com  Thu Dec 16 00:42:19 2010
From: mutlaqja at ikarustech.com (Jasem Mutlaq)
Date: Thu, 16 Dec 2010 02:42:19 +0300
Subject: [Kstars-devel] Re: I: Re: Kstars & SkyWatcher EQ3 SynScan
In-Reply-To: <4338776.2927451292427911956.JavaMail.defaultUser@defaultHost>
References: <4338776.2927451292427911956.JavaMail.defaultUser@defaultHost>
Message-ID: <AANLkTi=EMyMqA4FiHo6PSpzm0tAYvo1A_0dqkFUJqBjM@mail.gmail.com>

Hello,

KStars supports whatever telescopes INDI is supporting. Support for EQ3
SynScan will be available in libindi v0.8 which shall be released in about
3-4 weeks. If you use xUbuntu 10.04 or higher, you can get binaries from the
driver once it's released. Check www.indilib.org for more details.

Regards,
Jasem


On Wed, Dec 15, 2010 at 6:45 PM, smfiso2006 at libero.it
<smfiso2006 at libero.it>wrote:

>
>
> >----Messaggio originale----
> >Da: jharris at 30doradus.org
> >Data: 09/12/2010 17.39
> >A: "smfiso2006 at libero.it"<smfiso2006 at libero.it>
> >Ogg: Re: Kstars &amp; SkyWatcher EQ3 SynScan
> >
> >Please email your question to the kstars mailing list:
> >kstars-devel at kde.org.  I am no longer involved with KStars
> >development.
> >
> >regards,
> >Jason
> >
> >On Thu, Dec 9, 2010 at 5:02 AM, smfiso2006 at libero.it
> ><smfiso2006 at libero.it> wrote:
> >> Maybe I'm going to buy a SkyWatcher EQ3 SynScan , would it work with
> Kstars
> >> ?
> >>
> >
>
>
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel
>



-- 
--
Best Regards,
Jasem Mutlaq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kstars-devel/attachments/20101216/8fc37839/attachment.html 

From abhijit.apte at gmail.com  Fri Dec 17 10:29:45 2010
From: abhijit.apte at gmail.com (Abhijit Apte)
Date: Fri, 17 Dec 2010 14:59:45 +0530
Subject: [Kstars-devel]  Using QML in KStars
Message-ID: <AANLkTi=XOYtRz8qr+qStPMX1GBuYiCV88omfJrPzVWfd@mail.gmail.com>

Hi All,

Is there anything happening on this subject?
Atleast I googled for "QML KDE" and I didn't seem to find any technical
documentation on efforts in this front.
Is someone aware?

Rgds
-Abhi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kstars-devel/attachments/20101217/0d215db0/attachment.htm 

From akarshsimha at gmail.com  Fri Dec 17 11:06:27 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Fri, 17 Dec 2010 04:06:27 -0600
Subject: [Kstars-devel] Re: Using QML in KStars
In-Reply-To: <AANLkTi=XOYtRz8qr+qStPMX1GBuYiCV88omfJrPzVWfd@mail.gmail.com>
References: <AANLkTi=XOYtRz8qr+qStPMX1GBuYiCV88omfJrPzVWfd@mail.gmail.com>
Message-ID: <20101217100627.GA2131@K9>

On Fri, Dec 17, 2010 at 02:59:45PM +0530, Abhijit Apte wrote:
>    Hi All,
> 
>    Is there anything happening on this subject?
>    Atleast I googled for "QML KDE" and I didn't seem to find any technical
>    documentation on efforts in this front.
>    Is someone aware?

Well, I don't know much about QML, but it might be a nice thing to
experiment. In fact, I have some interesting ideas which might be
implementable using QML, if whatever bit I know about QML is right.

John Tapsell who is an astronomer and a KDE developer, suggested that
we have something helpful for beginners, to tell them how to use
KStars and tell them what's interesting in the sky.

I've been imagining this as a widget that's semitransparent -- quite
like the infoboxes -- that overlays on the skymap and is a dockable
widget that can be pulled out from the sides of the screen (much like
everything in Stellarium). This widget should be able to contain links
that implement specific actions. I was thinking of something that'd
look like this:

---------------------------------------------------------------------
What's Interesting to see?

+ Naked eye

  * Venus is visible in the evening
  Venus is shining at mag -4 and is at 45% phase. Elongation in 11
  days. <link>Click here to slew to Venus</link>

  * Jupiter is visible in the morning
  Just before daybreak, Jupiter is at an altitude of 30??. Rises at
  2:30 AM. Magnitude -2. <link>Click here to slew to Jupiter</link>

+ Telescope

  * Io transits Jupiter tonight at 3:23 AM.
  <link>Click here to open Jupiter's Moons tool</link>

  * Random Springtime galaxy showcase?
  Have you seen NGC 4565?
  <link>NGC 4565</link> is a bright edge-on spiral galaxy in
  <link>Coma Berenices</link>. At magnitude so-and-so, it is an
  interesting target for small telescopes... blah blah blah
---------------------------------------------------------------------

Now, here's the problem -- all these links are internal action links
-- they are to be bound to slots. And there should be an easy way of
writing all this, instead of coding each snippet! I'm wondering if QML
will help here. Maybe I'm completely mistaken and am looking for
something totally orthogonal.

Regards
Akarsh

From akarshsimha at gmail.com  Wed Dec 29 08:20:33 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Wed, 29 Dec 2010 08:20:33 +0100 (CET)
Subject: [Kstars-devel]  branches/KDE/4.6/kdeedu
Message-ID: <20101229072033.E08D23E1F1@svn.kde.org>

SVN commit 1210036 by asimha:

Temporary fix of KStars, just in case I don't fix everything before
the 4.6 release.

If this is done, the only significant changes, if I remember, in 4.6
are fixing a lot of projection-related bugs, refraction code, moon
phase almanac and some cities.dat fixes. Maybe there are a couple
more, but I'm disabling OpenGL support.

Hopefully, before the final release, I should have an option to switch
to the "Beta" OpenGL rendering mode which will be a regression from a
feature POV, but will run much much faster, so that many users will
still be interested in that.

CCMAIL: kstars-devel at kde.org, hdevalence at gmail.com



 M  +6 -4      CMakeLists.txt  
 M  +2 -1      kstars/kstars/skymap.h  


--- branches/KDE/4.6/kdeedu/CMakeLists.txt #1210035:1210036
@@ -92,12 +92,14 @@
 
 macro_optional_find_package(Eigen2 2.0.3)
 macro_log_feature(EIGEN2_FOUND "Eigen2" "A generic C++ template library for dense and sparse matrices" "http://eigen.tuxfamily.org" FALSE "2.0.3" "Required to build Step and KStars.")
-macro_optional_find_package(OpenGL)
+
+## For the 4.6 release, keeping OGL disabled by default.
+#macro_optional_find_package(OpenGL)
 # Really, OpenGL should be optional to build KStars, but as it stands now, it is a requisite.
-macro_log_feature(OPENGL_FOUND "OpenGL" "3D Graphics Library" "http://www.opengl.org/" FALSE "" "Required to build KStars.")
-if( EIGEN2_FOUND AND OPENGL_FOUND )
+#macro_log_feature(OPENGL_FOUND "OpenGL" "3D Graphics Library" "http://www.opengl.org/" FALSE "" "Required to build KStars.")
+if( EIGEN2_FOUND )
    macro_optional_add_subdirectory(kstars)
-endif( EIGEN2_FOUND AND OPENGL_FOUND )
+endif( EIGEN2_FOUND )
 
 macro_optional_add_subdirectory(kalzium)
 if (EIGEN2_FOUND AND NOT WIN32)
--- branches/KDE/4.6/kdeedu/kstars/kstars/skymap.h #1210035:1210036
@@ -18,7 +18,8 @@
 #ifndef SKYMAP_H_
 #define SKYMAP_H_
 
-#define USEGL
+// Disable GL for KDE 4.6 release at the moment.
+// #define USEGL
 
 #include <QTimer>
 #ifdef USEGL

From akarshsimha at gmail.com  Wed Dec 29 10:18:38 2010
From: akarshsimha at gmail.com (Akarsh Simha)
Date: Wed, 29 Dec 2010 10:18:38 +0100 (CET)
Subject: [Kstars-devel]  KDE/kdeedu/kstars/kstars
Message-ID: <20101229091838.A54EF3E1F3@svn.kde.org>

SVN commit 1210044 by asimha:

Backends separated. Working, unclean, hackish version.

+ SkyMap is now a QGraphicsView

+ The widget on which all drawing is done is called SkyMapQDraw for
  the Qt version (and will be called SkyMapGLDraw for the GL version).

+ SkyMapQDraw and the future SkyMapGLDraw inherit from an abstract
  SkyMapDrawAbstract class which contains common methods that draw
  using QPainter, and allows the reimplementation of paintEvent() or
  paintGL() as is appropriate in the children.

+ The SkyMapQDraw is set as the child widget of the
  QGraphicsView::viewport(). This seems to be the typical workaround
  for getting an QGLWidget to work as a non-background widget in a
  QGV. I don't know if there is a more elegant way _that works_. This
  is one of those hackish things.

+ SkyMap::forceUpdate() calls a repaint() (for the time being, not
  update()) on the SkyMapQDraw instead of the SkyMap itself. I don't
  know why this is necessary as yet. This is one more of the hackish
  things.

TODO:

1. See if there are less hackish ways of doing things. (But this is
   not on priority for the 4.6 release. If it works, and is reasonably
   neat, I think we should let it in.) If these are actually Qt bugs,
   file them and triage them.

2. Implement the GL backend.

Please let me know what you think. If it's okay, I'll transfer this to
4.6 after I'm done with the GL stuff. I solicit everyone's response on
this as soon as possible, since the release is in a very very short
time from now.

CCMAIL: kstars-devel at kde.org, hdevalence at gmail.com

 M  +1 -1      CMakeLists.txt  
 M  +5 -0      kstarsdata.h  
 M  +36 -16    skymap.cpp  
 M  +39 -61    skymap.h  
 D             skymapdraw.cpp  
 D             skymapdraw.h  
 A             skymapdrawabstract.cpp   skymapdraw.cpp#1210043 [License: GPL (v2+)]
 A             skymapdrawabstract.h   [License: GPL (v2+)]
 M  +8 -54     skymapevents.cpp  
 A             skymapqdraw.cpp   [License: GPL (v2+)]
 A             skymapqdraw.h   skymapdraw.h#1210043 [License: GPL (v2+)]


--- trunk/KDE/kdeedu/kstars/kstars/CMakeLists.txt #1210043:1210044
@@ -310,7 +310,7 @@
 	kspopupmenu.cpp obslistpopupmenu.cpp kstars.cpp ksalmanac.cpp 
 	kstarsactions.cpp kstarsdata.cpp kstarsdatetime.cpp kstarsdcop.cpp kstarsinit.cpp 
 	kstarssplash.cpp ksutils.cpp kswizard.cpp main.cpp 
-	simclock.cpp skymap.cpp skymapdraw.cpp skymapevents.cpp
+	simclock.cpp skymap.cpp skymapdrawabstract.cpp skymapqdraw.cpp skymapevents.cpp
 	skypainter.cpp skyqpainter.cpp skyglpainter.cpp
 	texture.cpp texturemanager.cpp
 	timezonerule.cpp 
--- trunk/KDE/kdeedu/kstars/kstars/kstarsdata.h #1210043:1210044
@@ -203,6 +203,11 @@
     /** Synchronize list of visible FOVs and list of selected FOVs in Options */
     void syncFOV();
 
+    /**
+     *@return the list of visible FOVs
+     */
+    inline const QList<FOV*> getVisibleFOVs() const { return visibleFOVs; }
+
     /** Return log object */
     OAL::Log *logObject() { return m_logObject; }
 
--- trunk/KDE/kdeedu/kstars/kstars/skymap.cpp #1210043:1210044
@@ -25,6 +25,7 @@
 #include <QFile>
 #include <QPointF>
 #include <QApplication>
+#include <QGraphicsScene>
 
 #include <kactioncollection.h>
 #include <kconfig.h>
@@ -58,6 +59,8 @@
 #include "projections/azimuthalequidistantprojector.h"
 #include "projections/equirectangularprojector.h"
 
+#include "skymapqdraw.h"
+
 #ifdef HAVE_XPLANET
 #include <KProcess>
 #include <kfiledialog.h>
@@ -139,14 +142,17 @@
 }
 
 SkyMap::SkyMap() :
+    QGraphicsView( KStars::Instance() ),
+    /*
 #ifdef USEGL
     QGLWidget( QGLFormat(QGL::SampleBuffers), KStars::Instance() ),
 #else 
     QWidget( KStars::Instance() ),
 #endif
+    */
     computeSkymap(true), angularDistanceMode(false), scrollCount(0),
-    data( KStarsData::Instance() ), pmenu(0), sky(0), sky2(0),
-    ClickedObject(0), FocusObject(0), TransientObject(0), m_proj(0)
+    data( KStarsData::Instance() ), pmenu(0),
+    ClickedObject(0), FocusObject(0), TransientObject(0), m_proj(0), m_SkyMapDraw(NULL)
 {
     m_Scale = 1.0;
 
@@ -171,8 +177,6 @@
     ClickedObject = NULL;
     FocusObject = NULL;
 
-    sky   = new QPixmap( width(),  height() );
-    sky2  = new QPixmap( width(),  height() );
     pmenu = new KSPopupMenu();
 
     setupProjector();
@@ -223,22 +227,39 @@
     m_iboxes->addInfoBox(m_geoBox);
     m_iboxes->addInfoBox(m_objBox);
 
-    m_fpstime.start();
-    m_framecount = 0;
+    // TODO: Pick the render enging from Options. For now, we will
+    // hardcode it here, for testing purposes only!
+    SkyMapQDraw *smqd = new SkyMapQDraw( this ); 
+    m_SkyMapDraw = smqd;
+    m_SkyMapDrawWidget = smqd;
 
+    // DEBUG: Okay. None of this seems to work. So I'm going to do it
+    // the stupid way -- where I just add the SkyMapQDraw (QWidget) as
+    // a child of this QGV.
+    /*
+    m_SkyScene = new QGraphicsScene( this );
+    m_SkyScene->addWidget( smqd );
+    setCacheMode( QGraphicsView::CacheNone );
+    smqd->show();
+    setScene( m_SkyScene );
+    */
+    smqd->setParent( this->viewport() );
+    smqd->show();
+
     //The update timer will be destructed when SkyMap is..
     QTimer *update = new QTimer(this);
     update->setInterval(30);
     connect(update, SIGNAL(timeout()), this, SLOT(update()) );
     update->start();
 
+    /*
     #ifdef USEGL
     if( !format().testOption( QGL::SampleBuffers ) )
         qWarning() << "No sample buffer; can't use multisampling (antialiasing)";
     if( !format().testOption( QGL::StencilBuffer ) )
         qWarning() << "No stencil buffer; can't draw concave polygons";
-
     #endif
+    */
 }
 
 void SkyMap::slotToggleGeoBox(bool flag) {
@@ -286,23 +307,17 @@
         Options::setFocusDec( focus()->dec().Degrees() );
     }
 
-    delete sky;
-    delete sky2;
     delete pmenu;
 
     delete m_proj;
 }
 
 void SkyMap::setGeometry( int x, int y, int w, int h ) {
-    QWidget::setGeometry( x, y, w, h );
-    *sky = sky->scaled( w, h );
-    *sky2 = sky2->scaled( w, h );
+    QGraphicsView::setGeometry( x, y, w, h );
 }
 
 void SkyMap::setGeometry( const QRect &r ) {
-    QWidget::setGeometry( r );
-    *sky = sky->scaled( r.width(), r.height() );
-    *sky2 = sky2->scaled( r.width(), r.height() );
+    QGraphicsView::setGeometry( r );
 }
 
 
@@ -894,6 +909,7 @@
 void SkyMap::setZoomFactor(double factor) {
     Options::setZoomFactor(  KSUtils::clamp(factor, MINZOOM, MAXZOOM)  );
     forceUpdate();
+    kDebug() << "Z00m CHANGED! CALLING forceUpdate()";
     emit zoomChanged();
 }
 
@@ -915,13 +931,17 @@
 
     computeSkymap = true;
     
+    kDebug() << "FORCING UPDATE!";
+
     // Ensure that stars are recomputed
     data->incUpdateID();
-
+    /*
     if( now )
         repaint();
     else
         update();
+    */
+    m_SkyMapDrawWidget->repaint(); // DEBUG: Testing.
 }
 
 float SkyMap::fov() {
--- trunk/KDE/kdeedu/kstars/kstars/skymap.h #1210043:1210044
@@ -18,20 +18,20 @@
 #ifndef SKYMAP_H_
 #define SKYMAP_H_
 
-#define USEGL
+// #define USEGL
 
 #include <QTimer>
-#ifdef USEGL
-    #include <QGLWidget>
-#else
-    #include <QWidget>
-#endif
+#include <QGraphicsView>
 #include <QPixmap>
 #include <QTime>
 
+
 #include "skyobjects/skypoint.h"
 #include "skyobjects/skyline.h"
 
+#include "skymapdrawabstract.h"
+#include "skymapqdraw.h"
+
 #include <config-kstars.h>
 
 #define HOVER_INTERVAL 500
@@ -51,6 +51,8 @@
 class InfoBoxes;
 class Projector;
 
+class QGraphicsScene;
+
 /**@class SkyMap
 	*
 	*This is the canvas on which the sky is painted.  It's the main widget for KStars.
@@ -66,10 +68,13 @@
 	*@version 1.0
 	*/
 
-class SkyMap::QGraphicsView {
+class SkyMap : public QGraphicsView {
 
-    Q_OBJECT
+    Q_OBJECT;
 
+    friend class SkyMapDrawAbstract;
+    friend class SkyMapQDraw; // FIXME: This is the ugliest thing I've done in my life. Please, please, do something else.
+
 protected:
     /**
     *Constructor.  Read stored settings from KConfig object (focus position,
@@ -269,6 +274,7 @@
 
     bool isPointNull( const QPointF &p );
 
+    // NOTE: This method is draw-backend independent.
     /**@short update the geometry of the angle ruler. */
     void updateAngleRuler();
 
@@ -280,35 +286,26 @@
     	*/
     bool isObjectLabeled( SkyObject *o );
 
-    /**@short Convenience function for shutting off tracking mode.  Just calls KStars::slotTrack().
+    /*@*@short Convenience function for shutting off tracking mode.  Just calls KStars::slotTrack().
     	*/
     void stopTracking();
 
-    // TODO: Decide the fate of this method. This method should
-    // probably be implemented only in the SkyMapQDraw class, and should be
-    // called out of that class, since it uses QPainter.
-
-    /**@short Draw the current Sky map to a pixmap which is to be printed or exported to a file.
-    	*
-    	*@param pd pointer to the QPaintDevice on which to draw.  
-    	*@see KStars::slotExportImage()
-    	*@see KStars::slotPrint()
-    	*/
-    void exportSkyImage( QPaintDevice *pd );
-
     /** Get the current projector.
         @return a pointer to the current projector. */
     const Projector * projector() const;
 
-    /**@short Draw "user labels".  User labels are name labels attached to objects manually with
-     * the right-click popup menu.  Also adds a label to the FocusObject if the Option UseAutoLabel
-     * is true.
-     * @param labelObjects QList of pointers to the objects which need labels (excluding the centered object)
-     * @param psky painter for the sky
-     * @note the labelObjects list is managed by the SkyMapComponents class
+    /**
+     *@short Proxy method for SkyMapDrawAbstract::exportSkyImage()
      */
-    void drawObjectLabels( QList< SkyObject* >& labelObjects );
+    void exportSkyImage( QPaintDevice *pd ) { m_SkyMapDraw->exportSkyImage( pd ); }
 
+    /**
+     *@short Proxy method for SkyMapDrawAbstract::drawObjectLabels()
+     */
+    void drawObjectLabels( QList< SkyObject* >& labelObjects ) { m_SkyMapDraw->drawObjectLabels( labelObjects ); }
+
+
+
 public slots:
     //DEBUG_KIO_JOB
     void slotJobResult( KJob *j );
@@ -421,11 +418,13 @@
      */
     void slotClockSlewing();
 
+    // NOTE: This method is draw-backend independent.
     /**Enables the angular distance measuring mode. It saves the first
      * position of the ruler in a SkyPoint. It makes difference between
      * having clicked on the skymap and not having done so */
     void slotBeginAngularDistance();
 
+    // NOTE: This method is draw-backend independent.
     /**Computes the angular distance, prints the result in the status
      * bar and disables the angular distance measuring mode
      * If the user has clicked on the map the status bar shows the 
@@ -482,14 +481,6 @@
     void mousePointChanged(SkyPoint*);
 
 protected:
-    #ifdef USEGL
-    virtual void resizeGL(int width, int height);
-    virtual void initializeGL();
-    //virtual void paintGL();
-    #endif
-    /**Draw the Sky, and all objects in it. */
-    virtual void paintEvent( QPaintEvent *e );
-
     /**Process keystrokes:
      * @li arrow keys  Slew the map
      * @li +/- keys  Zoom in and out
@@ -541,6 +532,11 @@
      */
     virtual void resizeEvent( QResizeEvent * );
 
+    /**
+     *@short Asks the SkyMapDrawWidget to repaint itself
+     */
+    virtual void paintEvent( QPaintEvent *e );
+
 private slots:
     /**Gradually fade the Transient Hover Label into the background sky color, and
     	*redraw the screen after each color change.  Once it has faded fully, set the 
@@ -548,6 +544,7 @@
     	*/
     void slotTransientTimeout();
 
+    // NOTE: Akarsh believes that this method is backend-independent, and is pretty confident about that, but he thinks that it really requires a second inspection.
     /**@short attach transient label to object nearest the mouse cursor.
     	*This slot is connected to the timeout() signal of the HoverTimer, which is restarted
     	*in every mouseMoveEvent().  So this slot is executed only if the mouse does not move for 
@@ -563,29 +560,7 @@
     void setMouseMoveCursor();
 
 private:
-    /**Draw the overlays on top of the sky map.  These include the infoboxes,
-    	*field-of-view indicator, telescope symbols, zoom box and any other
-    	*user-interaction graphics.
-    	*
-    	*The overlays can be updated rapidly, without having to recompute the entire SkyMap.
-    	*The stored Sky image is simply blitted onto the SkyMap widget, and then we call
-    	*drawOverlays() to refresh the overlays.
-    	*@param pm pointer to the Sky pixmap
-    	*/
-    void drawOverlays( QPainter& p );
 
-    /**Draw symbols at the position of each Telescope currently being controlled by KStars.
-    	*@note The shape of the Telescope symbol is currently a hard-coded bullseye.
-    	*@param psky reference to the QPainter on which to draw (this should be the Sky pixmap). 
-    	*/
-    void drawTelescopeSymbols(QPainter &psky);
-
-    /**
-    	*@short Draw a dotted-line rectangle which traces the potential new field-of-view in ZoomBox mode.
-    	*@param psky reference to the QPainter on which to draw (this should be the Sky pixmap). 
-    	*/
-    void drawZoomBox( QPainter &psky );
-
     /**@short Begin fading out the name label attached to TransientObject.
     	*
     	*mouseMoveEvent() will call fadeTransientLabel() when TransientObject is not a 
@@ -664,7 +639,6 @@
 
     KStarsData *data;
     KSPopupMenu *pmenu;
-    QPixmap *sky, *sky2;
     SkyPoint  Focus, ClickedPoint, FocusPoint, MousePoint, Destination;
     SkyObject *ClickedObject, *FocusObject, *TransientObject;
 
@@ -684,10 +658,14 @@
     InfoBoxWidget* m_objBox;
     InfoBoxes*     m_iboxes;
 
+    // Note: These two point to the same stuff
+    SkyMapDrawAbstract *m_SkyMapDraw;
+    QWidget *m_SkyMapDrawWidget;
+
+    QGraphicsScene *m_SkyScene;
+
     static SkyMap* pinstance;
 
-    QTime m_fpstime;
-    int m_framecount;
 };
 
 #endif
--- trunk/KDE/kdeedu/kstars/kstars/skymapevents.cpp #1210043:1210044
@@ -57,8 +57,9 @@
     //FIXME: No equivalent for this line in Qt4 ??
     //	if ( testWState( Qt::WState_AutoMask ) ) updateMask();
 
-    *sky  = sky->scaled( width(), height() );
-    *sky2 = sky2->scaled( width(), height() );
+    // TODO: Hopefully the child QWidget / QGLWidget will scale automatically...
+    // No, it doesn't seem to:
+    m_SkyMapDrawWidget->resize( size() );
 
     // Resize infoboxes container.
     // FIXME: this is not really pretty. Maybe there are some better way to this???
@@ -641,7 +642,7 @@
     }
 }
 
-#ifdef USEGL
+/*
 void SkyMap::initializeGL()
 {
 }
@@ -682,60 +683,13 @@
 
     ++m_framecount;
 }
-#else
-void SkyMap::paintEvent( QPaintEvent *event )
-{
-    //If computeSkymap is false, then we just refresh the window using the stored sky pixmap
-    //and draw the "overlays" on top.  This lets us update the overlay information rapidly
-    //without needing to recompute the entire skymap.
-    //use update() to trigger this "short" paint event; to force a full "recompute"
-    //of the skymap, use forceUpdate().
+*/
 
-    if(m_framecount == 25) {
-        float sec = m_fpstime.elapsed()/1000.;
-        printf("FPS: %.2f\n", m_framecount/sec);
-        m_framecount = 0;
-        m_fpstime.restart();
+void SkyMap::paintEvent( QPaintEvent *e ) {
+    // Do nothing for now.
+    kDebug() << "Was here";
     }
 
-    ++m_framecount;
-    if (!computeSkymap)
-    {
-        QPainter p;
-        p.begin( this );
-        p.drawLine(0,0,1,1); // Dummy operation to circumvent bug
-        p.drawPixmap( 0, 0, *sky );
-        drawOverlays(p);
-        p.end();
-        return ; // exit because the pixmap is repainted and that's all what we want
-    }
-
-    // FIXME: used to to notify infobox about possible change of object coordinates
-    // Not elegant at all. Should find better option
-    showFocusCoords();
-    setupProjector();
-    
-    SkyQPainter psky(this, sky);
-    //FIXME: we may want to move this into the components.
-    psky.begin();
-    
-    //Draw all sky elements
-    psky.drawSkyBackground();
-    data->skyComposite()->draw( &psky );
-    //Finish up
-    psky.end();
-
-    QPainter psky2;
-    psky2.begin( this );
-    psky2.drawLine(0,0,1,1); // Dummy op.
-    psky2.drawPixmap( 0, 0, *sky );
-    drawOverlays(psky2);
-    psky2.end();
-
-    computeSkymap = false;	// use forceUpdate() to compute new skymap else old pixmap will be shown
-}
-#endif
-
 double SkyMap::zoomFactor( const int modifier ) {
     double factor = ( modifier & Qt::ControlModifier) ? DZOOM : 2.0; 
     if ( modifier & Qt::ShiftModifier )