On Fri, Oct 3, 2008 at 7:00 AM,
<kstars-devel-request@kde.org> wrote:
Send Kstars-devel mailing list submissions to
kstars-devel@kde.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/kstars-devel
or, via email, send a message with subject or body 'help' to
kstars-devel-request@kde.org
You can reach the person managing the list at
kstars-devel-owner@kde.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kstars-devel digest..."
Today's Topics:
1. Re: INDI as a separate package (Brian)
2. KDE/kdeedu/kstars/kstars (Akarsh Simha)
3. KDE/kdeedu/kstars/kstars/tools (Akarsh Simha)
4. Re: INDI as a separate package (Jasem Mutlaq)
5. (no subject)
6. KDE/kdeedu/kstars/kstars/skycomponents (Akarsh Simha)
7. KDE/kdeedu/kstars/kstars/skycomponents (Akarsh Simha)
8. KDE/kdeedu/kstars/kstars/tools (Akarsh Simha)
----------------------------------------------------------------------
Message: 1
Date: Thu, 02 Oct 2008 21:29:10 +1000
From: Brian <bnc@astronomicalresearchaustralia.org>
Subject: Re: [Kstars-devel] INDI as a separate package
To: KStars Development Mailing List <kstars-devel@kde.org>
Message-ID: <48E4B086.6070001@astronomicalresearchaustralia.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Jasem,
As you know I use INDI extensively every clear night.
As long as the separate install works ok and we do not lose any
functionality, should be fine by me.
However, would it still integrate with kstars, i.e. will I still be able
to right click on a star and tell the scope to slew to it?
I was bit concerned when I found out that all the hardware drivers were
being removed. Has the doco been changed to describe how to install
required drivers?
I am currently running my observatory on suse 10.3 on a 64bit machine.
I have also installed a SUSE 11.0, which uses kde4 in part.
What level of kde4 will I need to test the new indi?
Can I download it vis svn?
Thanks,
Brian
Jasem Mutlaq wrote:
> Hi,
>
> After much consideration, I think it is better to remove INDI from KStars
> repo and make it as an optional add on. This is due to many factors
> including maintenance of two INDIs (KStars and the primary) and packaging
> consideration (some distros ship the two INDIs!). Furthermore, INDI is only
> available for Linux and KStars can be now run on multiple OSes. All in all,
> there will be less headache and only one INDI package will be available.
> Please let me know if there are any objections to this idea.
>
> Regards,
> Jasem
>
>
>
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel
>
------------------------------
Message: 2
Date: Thu, 02 Oct 2008 20:46:55 +0000
From: Akarsh Simha <akarshsimha@gmail.com>
Subject: [Kstars-devel] KDE/kdeedu/kstars/kstars
To: kde-commits@kde.org
Cc: kstars-devel@kde.org
Message-ID: <1222980415.831939.17881.nullmailer@svn.kde.org>
Content-Type: text/plain; charset=UTF-8
SVN commit 867116 by asimha:
Fixes incorrect message in What's Up Tonight Dialog. Should not
translate an empty string.
Many thanks to Avinash Krishnakumar and Suvinay S for helping me out.
CCMAIL: kstars-devel@kde.org
M +4 -4 geolocation.h
--- trunk/KDE/kdeedu/kstars/kstars/geolocation.h #867115:867116
@@ -124,19 +124,19 @@
QString name() const { return Name; }
/**@return translated City name
*/
- QString translatedName() const { return i18nc("City name (optional, probably does not need a translation)", Name.toUtf8().data()); }
- /**@return untranslated Province name
+ QString translatedName() const { return Name.isEmpty() ? QString() : i18nc("City name (optional, probably does not need a translation)", Name.toUtf8().data()); }
+ /**@return untranslated Province name
*/
QString province() const { return Province; }
/**@return translated Province name
*/
- QString translatedProvince() const { return i18nc("Region/state name (optional, rarely needs a translation)", Province.toUtf8().data()); }
+ QString translatedProvince() const { return Province.isEmpty() ? QString() : i18nc("Region/state name (optional, rarely needs a translation)", Province.toUtf8().data()); }
/**@return untranslated Country name
*/
QString country() const { return Country; }
/**@return translated Country name
*/
- QString translatedCountry() const { return i18nc("Country name (optional, but should be translated)", Country.toUtf8().data()); }
+ QString translatedCountry() const { return Country.isEmpty() ? QString() : i18nc("Country name (optional, but should be translated)", Country.toUtf8().data()); }
/**@return comma-separated city, province, country names (each localized)
*/
------------------------------
Message: 3
Date: Thu, 02 Oct 2008 21:22:05 +0000
From: Akarsh Simha <akarshsimha@gmail.com>
Subject: [Kstars-devel] KDE/kdeedu/kstars/kstars/tools
To: kde-commits@kde.org
Cc: kstars-devel@kde.org
Message-ID: <1222982525.625949.19301.nullmailer@svn.kde.org>
Content-Type: text/plain; charset=UTF-8
SVN commit 867132 by asimha:
Fixing incorrect label in the Conjunctions Dialog. The conjunction
tool, since quite some time, allows one of the objects to be a generic
sky object.
CCMAIL: kstars-devel@kde.org
M +1 -1 conjunctions.ui
--- trunk/KDE/kdeedu/kstars/kstars/tools/conjunctions.ui #867131:867132
@@ -86,7 +86,7 @@
</sizepolicy>
</property>
<property name="text" >
- <string>Between solar system bodies:</string>
+ <string>Between objects:</string>
</property>
</widget>
</item>
------------------------------
Message: 4
Date: Fri, 3 Oct 2008 01:31:10 +0300
From: "Jasem Mutlaq" <mutlaqja@ikarustech.com>
Subject: Re: [Kstars-devel] INDI as a separate package
To: <bnc@astronomicalresearchaustralia.org>, "'KStars Development
Mailing List'" <kstars-devel@kde.org>
Message-ID: <001101c924de$941b3340$bc5199c0$@com>
Content-Type: text/plain; charset="us-ascii"
Hi Brian,
------------------------------
Message: 5
Message-ID: <mailman.8.1223028009.12356.kstars-devel@kde.org>
packagers ship KStars, they compile it with the INDI package, and I'll try
to make sure this happens on Linux. Regarding drivers which depend on
external libraries like apogee, sbig, ..etc, they will not be part of the
primary INDI package, but they'll be offered as separate packages.
Installation-wise, I'm using SUSE BuildService to make all these packages
available to all major distributions, and will try to include them in the
official repo for each major distribution.
Regards,
Jasem
> -----Original Message-----
> From: Brian [mailto:bnc@astronomicalresearchaustralia.org]
> Sent: Thursday, October 02, 2008 2:29 PM
> To: KStars Development Mailing List
> Subject: Re: [Kstars-devel] INDI as a separate package
>
> Hi Jasem,
> As you know I use INDI extensively every clear night.
> As long as the separate install works ok and we do not lose any
> functionality, should be fine by me.
> However, would it still integrate with kstars, i.e. will I still be
> able
> to right click on a star and tell the scope to slew to it?
>
> I was bit concerned when I found out that all the hardware drivers were
> being removed. Has the doco been changed to describe how to install
> required drivers?
>
> I am currently running my observatory on suse 10.3 on a 64bit machine.
> I have also installed a SUSE 11.0, which uses kde4 in part.
> What level of kde4 will I need to test the new indi?
> Can I download it vis svn?
>
> Thanks,
> Brian
>
> Jasem Mutlaq wrote:
> > Hi,
> >
> > After much consideration, I think it is better to remove INDI from
> KStars
> > repo and make it as an optional add on. This is due to many factors
> > including maintenance of two INDIs (KStars and the primary) and
> packaging
> > consideration (some distros ship the two INDIs!). Furthermore, INDI
> is only
> > available for Linux and KStars can be now run on multiple OSes. All
> in all,
> > there will be less headache and only one INDI package will be
> available.
> > Please let me know if there are any objections to this idea.
> >
> > Regards,
> > Jasem
> >
> >
> >
> > _______________________________________________
> > Kstars-devel mailing list
> > Kstars-devel@kde.org
> > https://mail.kde.org/mailman/listinfo/kstars-devel
> >
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel@kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel
------------------------------
Message: 6
Date: Fri, 03 Oct 2008 00:51:22 +0000
From: Akarsh Simha <akarshsimha@gmail.com>
Subject: [Kstars-devel] KDE/kdeedu/kstars/kstars/skycomponents
To: kde-commits@kde.org
Cc: kstars-devel@kde.org
Message-ID: <1222995082.417519.25899.nullmailer@svn.kde.org>
Content-Type: text/plain; charset=UTF-8
SVN commit 867186 by asimha:
Remove the warning about magnitude jump. While this is great help for
debugging and exposes hidden problems, it is a nuisance with the NOMAD
catalog and since the catalogs and code are pretty much fine, it might
be safe to remove it now.
CCMAIL: kstars-devel@kde.org
M +2 -0 starblocklist.cpp
--- trunk/KDE/kdeedu/kstars/kstars/skycomponents/starblocklist.cpp #867185:867186
@@ -135,10 +135,12 @@
}
blocks[nBlocks - 1]->addStar( &star );
+ /*
if( faintMag > -5.0 && fabs(faintMag - blocks[nBlocks - 1]->getFaintMag()) > 0.2 ) {
kDebug() << "Encountered a jump from mag" << faintMag << "to mag"
<< blocks[nBlocks - 1]->getFaintMag() << "in trixel" << trixel;
}
+ */
faintMag = blocks[nBlocks - 1]->getFaintMag();
nStars++;
}
------------------------------
Message: 7
Date: Fri, 03 Oct 2008 01:23:57 +0000
From: Akarsh Simha <akarshsimha@gmail.com>
Subject: [Kstars-devel] KDE/kdeedu/kstars/kstars/skycomponents
To: kde-commits@kde.org
Cc: kstars-devel@kde.org
Message-ID: <1222997037.226692.26190.nullmailer@svn.kde.org>
Content-Type: text/plain; charset=UTF-8
SVN commit 867187 by asimha:
Manage the setting of the inDraw flag correctly.
Thanks to Madhusudhan, Santhosh and Krishna for working on it.
CCMAIL: kstars-devel@kde.org
M +2 -2 deepstarcomponent.cpp
--- trunk/KDE/kdeedu/kstars/kstars/skycomponents/deepstarcomponent.cpp #867186:867187
@@ -178,8 +178,8 @@
float radius = map->fov();
if ( radius > 90.0 ) radius = 90.0;
- if ( m_skyMesh->inDraw() ) {
- printf("Warning: aborting concurrent DeepStarComponent::draw()\n");
+ if ( m_skyMesh != SkyMesh::Instance() && m_skyMesh->inDraw() ) {
+ printf("Warning: aborting concurrent DeepStarComponent::draw()");
}
bool checkSlewing = ( map->isSlewing() && Options::hideOnSlew() );
------------------------------
Message: 8
Date: Fri, 03 Oct 2008 01:32:28 +0000
From: Akarsh Simha <akarshsimha@gmail.com>
Subject: [Kstars-devel] KDE/kdeedu/kstars/kstars/tools
To: kde-commits@kde.org
Cc: kstars-devel@kde.org
Message-ID: <1222997548.890329.26290.nullmailer@svn.kde.org>
Content-Type: text/plain; charset=UTF-8
SVN commit 867188 by asimha:
The conjunctions tool must object if both objects selected are the
same.
Thanks for the patch, Prakash.
CCMAIL: kstars-devel@kde.org
M +6 -3 conjunctions.cpp
--- trunk/KDE/kdeedu/kstars/kstars/tools/conjunctions.cpp #867187:867188
@@ -138,11 +138,11 @@
break;
}
case 9: {
- Object1 = (KSComet *) new KSComet( (KSComet &) *fd.selectedObject() );
+ Object1 = new KSComet( (KSComet &) *fd.selectedObject() );
break;
}
case 10: {
- Object1 = (KSAsteroid *) new KSAsteroid( (KSAsteroid &) *fd.selectedObject() );
+ Object1 = new KSAsteroid( (KSAsteroid &) *fd.selectedObject() );
break;
}
}
@@ -179,7 +179,10 @@
return;
}
Object2 = KSPlanetBase::createPlanet( Obj2ComboBox->currentIndex() );
-
+ if( Object1->name() == Object2->name() ) {
+ KMessageBox::sorry( 0 , i18n("Please select two different objects to check conjunctions with.") );
+ return;
+ }
QApplication::setOverrideCursor( QCursor(Qt::WaitCursor) );
KSConjunct ksc;
ComputeStack->setCurrentIndex( 1 );
------------------------------
_______________________________________________
Kstars-devel mailing list
Kstars-devel@kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel
End of Kstars-devel Digest, Vol 63, Issue 2
*******************************************