performance tip which might be of use for kstars?

http://www.kotek.net/blog/rangeset_and_huge_datasets

Re: performance tip which might be of use for kstars?

В сообщении от 01 декабря 2009 12:50:05 Mike Rosseel написал:
> http://www.kotek.net/blog/rangeset_and_huge_datasets

As far as I can understand from blog post approach described there is 
advantageous for very specific data sets. They should be isomorphic to integer 
numbers and dense enough. I.e. it should consist of small number of contiguous 
ranges. It seems that there isn't any application for such data structure in 
kstars.

Thank you for the link though 
_______________________________________________
Kstars-devel mailing list
Kstars-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

Cursor bug

Hello

Could anyone confirm bug with cursor in he latest kstars. Cursor above the map 
appears on the white square.

This is very obvious and annoying bug and it should be fixed before beta2 
tagging I believe.
--
  Khudyakov Alexey

Re: Cursor bug

Hello,

yes I can confirm this bug. I am using latest (from sunday) svn
version of kstars.

Best regards,
Martin

2009/12/1 Khudyakov Alexey <alexey.skladnoy <at> gmail.com>:
> Hello
>
> Could anyone confirm bug with cursor in he latest kstars. Cursor above the map
> appears on the white square.
>
> This is very obvious and annoying bug and it should be fixed before beta2
> tagging I believe.
> --
>  Khudyakov Alexey
> _______________________________________________
> Kstars-devel mailing list
> Kstars-devel <at> kde.org
> https://mail.kde.org/mailman/listinfo/kstars-devel
>

Re: performance tip which might be of use for kstars?

В сообщении от Вторник 01 декабря 2009 16:38:58 вы написали:
> Hi,
> 
> > As far as I can understand from blog post approach described there is
> > advantageous for very specific data sets. They should be isomorphic to
> > integer
> 
> in the end he talks about healpix, which I thought kstars uses, but I
> might be wrong of course :)
> 
No. Kstars uses another approach to spatial indexing on a sphere. Namely 
hierarchical triangular mesh.
_______________________________________________
Kstars-devel mailing list
Kstars-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

Fwd: [kde-promo] Update The Feature Plan! NOW!

Valid also for KDE-Edu developers, especially KStars and Marble!

----------  Forwarded Message  ----------

Subject: [kde-promo] Update The Feature Plan! NOW!
Date: Tuesday 01 December 2009
From: Sebastian Kügler <sebas <at> kde.org>
To: plasma-devel <at> kde.org

Dear Plasma Developers,

Please edit the feature plan:

http://techbase.kde.org/Schedules/KDE4/4.4_Feature_Plan

I'm looking over it, and it all does not make sense. There are many items 
which 
should be green, but are yellow. That means that you, my fellow developers did 
not 
update it. I'm not going to run through them all, everything yellow might 
simply not 
be in the list of new and improved things in for KDE SC 4.4 as I cannot confirm 
for 
every single item in there if it's in and if it's supposed to work.

So, please edit the feature plan. If you've done so, reply to this email (keep 
kde-
promo in CC:) with your change, so I can update the list we're using as source 
for 
the 4.4 release notes.

Re: Cursor bug

В сообщении от 01 декабря 2009 16:38:23 Martin Mancuska написал:
> Hello,
> 
> yes I can confirm this bug. I am using latest (from sunday) svn
> version of kstars.
> 
Thank you for your input. I fixed bug in my local branch. I will commit in 
central repository in a week or so. Beta1 isn't out yet and I won't be able 
to anything for this week.
_______________________________________________
Kstars-devel mailing list
Kstars-devel <at> kde.org
https://mail.kde.org/mailman/listinfo/kstars-devel

KStars workout at FOSS.IN

Hi folks

Prakash and I are at this conference called FOSS.IN (http://foss.in)
in Bangalore, India and the KDE India team is making it pretty big
this time as well, as usual.

Starting sometime after about 24 hours, we are holding a "workout",
which is FOSS.IN terminology for a contributing session. We'd like
some ideas on how to make KStars better - both easy-to-implement ones
and complicated ones. Please do put in your ideas on this wiki:
http://techbase.kde.org/Projects/Edu/KStars/KStars_Workout_at_FOSS.IN_2009

Even categorizing existing buglists / wishlists and highlighting
"important" ones would be of help.

Thanks in advance.

Regards
Akarsh

branches/kstars/unfrozen/kstars [POSSIBLY UNSAFE]

SVN commit 1058621 by asimha:

Syncing KStars directory of trunk with the unfrozen branch. Useful to
catch the small amount of love KStars gets from me during December
vacation.

CCMAIL: kstars-devel <at> kde.org

 M  +0 -1      CMakeLists.txt  
 M  +34 -21    kstars/CMakeLists.txt  
 M  +12 -8     kstars/Messages.sh  
 M  +13 -8     kstars/binfilehelper.cpp  
 M  +1 -1      kstars/binfilehelper.h  
 M  +0 -30     kstars/byteswap.h  
 M  +61 -124   kstars/colorscheme.cpp  
 M  +65 -108   kstars/colorscheme.h  
 M  +75 -0     kstars/data/CMakeLists.txt  
 M  +3409 -24  kstars/data/Cities.dat  
 M  +122 -4    kstars/data/README.binfileformat  
 M  +21 -1     kstars/data/README.indexfileformat  
 M  +99 -0     kstars/data/TZrules.dat  
 M  +2000 -0   kstars/data/asteroids.dat  
 M  +1390 -0   kstars/data/cbounds-3.idx  
 M  +11803 -0  kstars/data/cbounds-5.idx  
 M  +13124 -0  kstars/data/cbounds.dat  
 M  +29 -0     kstars/data/chart.colors  
 M  +1 -0      kstars/data/classic.colors  
 M  +4759 -0   kstars/data/clines.dat  
 M  +548 -0    kstars/data/cnames.dat  
 M  +1279 -0   kstars/data/comets.dat  

info boxes

Hi,

I have messed around with the info boxes a bit and would like to have some 
feedback.

I implemented some code to use the "sticky" integers from options to prevent 
the info boxes from floating in the center of the skymap or outside of visible 
range after window resize. I have attached my result, the debug-patch shows 
the stickyness of the info boxes through their background colors. I guess 
there is something terribly wrong with my approach, please tell me what it is.

In SkyMap::~SkyMap() the state of the info boxes is stored to the Options. It 
seems as if "m_iboxes->isVisible()" allways returns false at this point and 
therefore the boxes are always hidden on program start. If I use the state of 
the checkbox instead, it seems to work. What is the problem here?

I'm wondering where the info boxes are deleted on program termination. Does it 
happen at all?

Regards,
Lukas

Index: kstars.cpp
===================================================================
--- kstars.cpp	(revision 1058994)
+++ kstars.cpp	(working copy)
@@ -156,6 +156,7 @@
     actionCollection()->action("coordsys")->setText(
         Options::useAltAz() ? i18n("Horizontal &Coordinates") : i18n("Equatorial &Coordinates") );