[Kstars-devel] Kstars optimization

[Prasanna Krishnamoorthy]

On 11/28/06, Jason Harris <jharris at 30doradus.org> wrote:
> It depends mostly on the zoom level, I think.  If we have just a single static
> lookup table, then there will be a single threshhold zoom level above which
> we will want to switch from the LUT to real trig values, because at higher
> zoom levels errors in position will be more noticeable.  I think we should
> decide on this zoom level empirically.  We can draw some set of objects
> twice, once with LUT coordinates, and one with real trig coordinates.  Then
> zoom in until the pairs of objects deviate from each other.
Ok. I'll write the code, then we'll see.

> You are developing against 3.5, I presume?  We're technically not developing
> that branch anymore; no new features are allowed to be committed in it.  I am
> willing to port your changes to the development branch (which will eventually
> become KDE4).
Thanks, I'm a bit wary about picking up the development because of
your previous comments on 3.5 being faster than the development
branch. I hope the changes will be easy for you to port over.

Best Regards,
Prasanna.